Angular CLI: 6.0.0-rc.9
Node: 10.0.0
OS: win32 x64
Angular: 6.0.0-rc.6
... common, compiler, compiler-cli, core, forms, http
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.5.12
@angular-devkit/build-angular 0.5.12
@angular-devkit/build-optimizer 0.5.12
@angular-devkit/core 0.5.12
@angular-devkit/schematics 0.5.12
@angular/cli 6.0.0-rc.9
@ngtools/webpack 6.0.0-rc.10
@schematics/angular 0.5.12
@schematics/update 0.5.12
rxjs 6.0.0
typescript 2.7.2
webpack 4.6.0
Build with this configuration :
"optimization": true,
"outputHashing": "none",
"sourceMap": true,
"extractCss": true,
"namedChunks": false,
"aot": true,
"extractLicenses": true,
"vendorChunk": true,
"buildOptimizer": true,
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
Finish generation build with sourcemap when optimisation and buildOptimizer are enabled in configuration
update: same behavior in v6 release of angular&cli
Have same issue just with Angular 6 and Angular-Cli 6
+1
+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
+1
If you set --optimization=false build can succeed with --source-map enabled
+1
+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.
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._
Most helpful comment
Have same issue just with Angular 6 and Angular-Cli 6