Skip to content
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

Unexpected color changes in Angular commands' output #238

Closed
peruukki opened this issue Aug 7, 2020 · 4 comments
Closed

Unexpected color changes in Angular commands' output #238

peruukki opened this issue Aug 7, 2020 · 4 comments

Comments

@peruukki
Copy link
Contributor

peruukki commented Aug 7, 2020

We use Concurrently to run various commands in an Angular project. After upgrading to Angular 10, we are seeing unexpected color changes in various Angular commands' output, even in the middle of output lines.

Here is the output of an ng serve command when run directly on the command line:
ng-serve-directly

Here is the same when run (prefixed "admin") via Concurrently:
ng-serve-via-concurrently

Should the output colors be the same? In any case, any ideas what might cause this behavior? The colors have never been the same for us, but these kinds of color changes (white to green) only started after we upgraded Angular.

We are using Concurrently programmatically if that makes a difference, and our Node version is 12.16.1.

@danielweck
Copy link

danielweck commented Oct 29, 2020

I tried various combinations of COLORS=1 and FORCE_COLOR=1 and --color and NPM_CONFIG_COLOR=always on the CLI, but --raw is what helped in the end.

@GerkinDev
Copy link

Seems related to the observable approach of concurrently's output, as mentioned the related issue in angular repo. Wouldn't it be possible to use a stream instead of an observable?

@GerkinDev
Copy link

This issue has been solved on the angular side just now and should be shipped in next version of angular CLI!
You'll be able to pass FORCE_COLOR=1 in order to bypass angular CLI color support

@paescuj
Copy link
Collaborator

paescuj commented May 20, 2022

Closing as it seems like this has been resolved on angulars side.

@paescuj paescuj closed this as completed May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants