CLI sometimes emits errors in a hard-to-read foreground color

[fr0]

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

The error log output (for compiler errors, etc.) sometimes shows up as dark red, which is very difficult to read on a black background. (Sometimes, it shows up as the normal red color. I am not sure what causes the switch.)

See attached screenshots.

Readable (normal color):

Not readable:

Command (mark with an x)

- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Angular CLI: 7.0.2
Node: 8.11.2
OS: win32 x64
Angular: 7.0.0
... animations, common, compiler, compiler-cli, core, elements
... forms, http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.10.2
@angular-devkit/build-angular     0.10.2
@angular-devkit/build-optimizer   0.10.2
@angular-devkit/build-webpack     0.10.2
@angular-devkit/core              7.0.2
@angular-devkit/schematics        7.0.2
@angular/cli                      7.0.2
@ngtools/webpack                  7.0.2
@schematics/angular               7.0.2
@schematics/update                0.10.2
rxjs                              6.3.3
typescript                        3.1.3
webpack                           4.19.1

This is using Windows 10. I have tried with standard windows command prompt consoles and cygwin consoles, and the issue occurs in both cases.

Repro steps

ng serve on Windows 10

Add an error to the typescript code. Keep doing this until it shows up as dark-red.

Desired functionality

Light red error text.

Mention any other details that might be useful

I don't remember this happening prior to upgrading to Angular 7, etc, so this may be a regression.

[angular-automatic-lock-bot]

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.}