Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ng build --prod is not creating unique hashes
See original GitHub issueVersions
`Angular CLI: 6.0.0 Node: 8.10.0 OS: win32 x64 Angular: 6.0.0 … animations, cli, common, compiler, compiler-cli, core, forms … http, language-service, platform-browser … platform-browser-dynamic, router
Package Version
@angular-devkit/architect 0.6.0 @angular-devkit/build-angular 0.6.0 @angular-devkit/build-optimizer 0.6.0 @angular-devkit/core 0.6.0 @angular-devkit/schematics 0.6.0 @ngtools/webpack 6.0.0 @schematics/angular 0.6.0 @schematics/update 0.6.0 rxjs 6.1.0 typescript 2.7.2 webpack 4.6.0`
Repro steps
- Create a site with ng new
- Add a lazy path with loadChildren
- ng build --prod
Observed behavior
Every time production build happens the hashes in the chunks do not change.
Desired behavior
Every single --prod build should result in unique hashes for cache busting.
Mention any other details that might be useful (optional)
Not sure if this is an issue with Angular cli or with webpack but it’s definitely effecting Angular. I believe it’s also in 5.2.10.
Not sure if this is windows only, but it happens locally on Windows and in VSTS hosted build.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:19
- Comments:62 (20 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think you’re having some weird errors and can’t debug it, and so, understandably, you’re frustrated. But this is a tracker for bugs and feature requests. If we can we also try to help with support requests. We’re very lucky to have awesome community members that also spend time trying to help people here in the issue tracker.
But we can’t really help much at all if you don’t fill in the issue template. I read your issue and have no idea what’s going wrong and how to help you. And when other users search the issue tracker and see your issue, it also doesn’t help them.
So I think the best thing to do is to close this issue, and ask you to open a new one. In that new one please fill in the issue template and give us an idea of what’s happening and how to reproduce it. That way we’ll have a chance to help you.
Closing as it looks like the issue has been solved with the answers above.