-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ng build --watch and ng serve don't always build updated files after new changes #4566
Comments
This is a known issue, going back to "@ngtools/webpack" : "1.2.4" fixes the issue but you will lose the new perfomance improvements in building time of version 1.2.6 and up. |
Thanks a bunch, efstathiosntonas. Just ran |
Having the same issue here actually, on Ubuntu. Will try to dig into it some more. So far I figured out that it is always the same files that it refuses to rebuild, so I think it is something related to the current dependency graph. |
Installing 1.2.4 of webpack doesn't fix it for me, is there any workaround to use in the meantime? Killing and then running |
Heya, let's talk about this in #5117 since it's still open and has a fair amount of replies there. I can't get a repro of this issue and would appreciate if someone has one. |
Have you tried removing --aot option? That works for me. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I usually need to save changes multiple times in order for angular-cli to actually build files with those changes.
OS?
Ubuntu 16.10 x64
Versions.
angular-cli: 1.0.0-beta.28.3
node: 7.1.0
os: linux x64
Repro steps.
This happens for any angular-cli app I make, even fresh ones.
In the log below you can see the initial build when running
ng build --watch
with Hash: 91bb893998276a59bbb3. Then I make a change toapp.component.ts
and save it. Angular-cli responds with those next builds with the same Hash: 91bb893998276a59bbb3 which results in dist files without the new change. I go back toapp.component.ts
and save again. Finally angular-cli responds with new Hash: 99e3be9aeef7c621e6f3 and the dist files include the new change.The log given by the failure.
Mention any other details that might be useful.
I thought this problem might be due to the Inotify Watches Limit on Linux that has been mentioned in some issues but setting it to 524288 does not fix the problem and it seems to me that angular-cli knows when the changes happen but doesn't include them in the build for some reason. Also none of the directories have spaces or special characters in their name and webpack runs fine in other projects.
The text was updated successfully, but these errors were encountered: