-
Notifications
You must be signed in to change notification settings - Fork 12k
6rc.X --stats-json or sourceMap blocking at 95% when optimisation&buildOptimizer are set to true #10591
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
Comments
Have same issue just with Angular 6 and Angular-Cli 6 |
+1 |
2 similar comments
+1 |
+1 |
Disabling sourceMaps seems to resolve the problem |
+1 |
I've got similar problem, but for me it freezes at 92%. I'm using Angular & cli v.6.0.1 |
+1. Works great on my mac but not on windows |
Does the same thing on my mac though |
Have same issue Angular-Cli 6.0.3 on win10 |
I also have the same problem, any work around for this? |
Currently still experiencing this issue in angular-cli 6.0.8 |
+1 |
1 similar comment
+1 |
+1 If you set --optimization=false build can succeed with --source-map enabled |
+1 |
2 similar comments
+1 |
+1 |
Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version. If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. |
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. |
Versions
Repro steps
Build with this configuration :
Observed behavior
Blocking at 95% but folder and map exist on filesystem, cli never finish 95% step. (it works if disabled optimisation option)
95% emitting index-html-webpack-plugin
Desired behavior
Finish generation build with sourcemap when optimisation and buildOptimizer are enabled in configuration
update: same behavior in v6 release of angular&cli
The text was updated successfully, but these errors were encountered: