ng serve not creating new hash on code updates

[rohitsodhia]

Please provide us with the following information:

OS?

Win 8

Versions.

1.0.0-beta.30

Repro steps.

Originally created in 1.0.0-beta.26, I followed the update steps on the main GIT page to update to 30.

The log given by the failure.

Not a failure, persay. When I run ng serve, the initial compilation works out. When I change code, it triggers the compiler to rebuild the files, but the same hash is served, and the files don't seem to update. I have to stop ng serve and restart it each time I make a code change to see my changes reflected.

[nerumo]

Same on Win 10, the hash stays the same. If I change the html it works, but not for TS.

[hansl]

Seems like this is a problem mostly with Windows. We'll investigate. Thanks!

[Ionaru]

Can confirm issue on Windows 10, changing something in the stylesheets will also trigger a refresh correctly.

[Jonatthu]

Same here with ngtools 1.2.7 is happening, I've installed 1.2.4 for keep working

[mattdistefano]

Dup of #4338?

[ulymor]

I faced with the same problem on Ubuntu 16.04 and angular CLI 1.0.0-beta.30

The problem was related with Inotify Watches Limit on Linux.
To solve to issue I increased the watches limit to 512K

sudo sysctl fs.inotify.max_user_watches=524288
sudo sysctl -p --system

After that I restarted my IDE (WebStorm in my case) and after that the change detection started to work.

[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.}