10.5.06.1.0Angular CLI: 6.0.8
Node: 10.5.0
OS: win32 x64
Angular: 6.0.7
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.6.8
@angular-devkit/build-angular 0.6.8
@angular-devkit/build-optimizer 0.6.8
@angular-devkit/core 0.6.8
@angular-devkit/schematics 0.6.8
@angular/cli 6.0.8
@ngtools/webpack 6.0.8
@schematics/angular 0.6.8
@schematics/update 0.6.8
rxjs 6.2.1
typescript 2.7.2
webpack 4.8.3
ng newI tried both
powershellandcmdon Windows
I'm not sure if this is a Windows issue and I also tried on the Windows Insiders as well
I think the issue Microsoft/vscode#19665 may helps probably


the build progress output should not be broken on Windows
BTW: the progress output works nicely as always in Bash on Ubuntu 16.04
SORRY for my poor English 馃槅
it's @angular/[email protected] with @angular-devkit/[email protected] and the issue is still there
any news ?
it's @angular/[email protected] with @angular-devkit/[email protected] and the issue is still there 馃槩
I'm not sure what's happening, but I am on Windows, using Git Bash, and don't see this behaviour.
hi @filipesilva
After doing some experiments, I think this issue is related to the font setting of the terminal (powershell, git bash , etc)
when I change the font setting of Git Bash like this the build output goes into a mess

but when I change the font setting of Git Bash like this the output goes well

just changed the font size from
8x16to8x12
SORRY for my poor English 馃槅
I redo the experiment above on an old angular project with [email protected] and @angular/[email protected]
the output goes very well no matter what the font setting of Git Bash is
Thanks for investigation 馃憤
It might be related with changes on Webpack's side as well, we'll have to investigate. Best I can say for now is to turn off progress reporting via --progress=false or in the angular.json file.
@filipesilva
this issue has been fixed with @angular/[email protected] and @angular-devkit/[email protected] in my scenario 馃帀
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
Thanks for investigation 馃憤
It might be related with changes on Webpack's side as well, we'll have to investigate. Best I can say for now is to turn off progress reporting via
--progress=falseor in theangular.jsonfile.