ng serve --watch is not watching for code changes

[davidrdz93]

Bug Report or Feature Request (mark with an x)

- [ x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.4.9
node: 8.9.0
os: linux x64
@angular/animations: 4.3.6
@angular/common: 4.3.6
@angular/compiler: 4.3.6
@angular/core: 4.3.6
@angular/forms: 4.3.6
@angular/http: 4.3.6
@angular/platform-browser: 4.3.6
@angular/platform-browser-dynamic: 4.3.6
@angular/router: 4.3.6
@angular/cli: 1.4.9
@angular/compiler-cli: 4.3.6
@angular/language-service: 4.3.6
typescript: 2.3.4

Repro steps.

ng serve --port 8080 --watch

The log given by the failure.

The development server is not reloading when changes are made on the code..
It only compiles and serves the project.

I don't know what other information can I supply in order to explain better myself!

[deebloo]

@davidrdz93 can you provide a sample project with this issue? also ng serve should do livereload without the --watch flag. can you try with that flag?

[davidrdz93]

I am trying without the --watch flag but it is not working.. Last night I tried reinstalling webpack and It worked for a while! I don't know how to provide a sample project, however let me know if there are another ways to give you more info! Thanks!

[davidrdz93]

I don't know if there is something in my environment because in my other PC it is livereloading nice!

[davidrdz93]

I am just realizing that using ng serve with sudo is making it work properly

[scottasmith]

Hi all,
This may help if it is the same problem I had.
Trying to use ng serve and ng build --watch sometimes worked but mostly they were not watching for code changes and I thought it was something to do with ng.

Then I remembered a problem I had a while back with
inotify watches

I ran this on my Ubuntu machine and it seems to have kicked in and watching code changes:

echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system

Hope it helps

[ilovett]

Thanks @scottasmith increasing max watches on ubuntu worked for me

[Paulskit]

@davidrdz93 try this: #9275 (comment)
Helped my solve the same issue.

[tommueller]

For me this also changed from one day to the other, also running the the ng serve as root fixes the problem for me ... I ran an apt upgrade on my Debian 9 maschine today, that updated this packages:

Start-Date: 2018-02-27  09:03:50
Upgrade: libsystemd0:amd64 (236-3~bpo9+1, 237-3~bpo9+1), geoip-database:amd64 (20171107-1~bpo9+1, 20180215-1~bpo9+1), google-chrome-stable:amd64 (64.0.3282.140-1, 64.0.3282.186-1), udev:amd64 (236-3~bpo9+1, 237$
End-Date: 2018-02-27  09:04:10

Maybe that is of any help?!

Angular CLI: 1.6.2
Node: 8.9.4
OS: linux x64

[quirogamauricio]

@scottasmith 's solution worked for me as well. Thank you.

[udbhav1995]

@scottasmith 's solution worked for me as well for angular version 1.6.3

[mmohammad-pk]

@scottasmith Thanks. It worked for me as well.

[vikasinfobeans]

Below cmd is working for me

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

[nikhilbhalwankar]

Hi all,
This may help if it is the same problem I had.
Trying to use ng serve and ng build --watch sometimes worked but mostly they were not watching for code changes and I thought it was something to do with ng.

Then I remembered a problem I had a while back with
inotify watches

I ran this on my Ubuntu machine and it seems to have kicked in and watching code changes:

echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system

Hope it helps

Thanks a ton. This worked for me like a charm on Ubuntu 18.04 LTS !

[oranjos9]

watch is not watching for code changes i am using windows

[mgechev]

@oranjos9 what's your Angular CLI version?

[vijayksingh]

@mgechev It's not working for me, I haven't installed it globally but only at Project Level

Angular CLI Version: 8.1.1
OS: Windows
I also tried adding a poll option to angular.json configuration and it also doesn't seem to work.

[mgechev]

Not sure if that's a problem in the CLI. Happy to see that there's a workaround for linux, but this also makes me thing that the issue is related to permissions or other OS-level configuration.

With the limited information we have here, I don't think there's anything more we can do. I'm closing for now, please comment or open a new issue if you have more insights or you're able to consistently reproduce the problem.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}