Flag to disable build/serve colors for text viewers that don't support them

Bug Report or Feature Request (mark with an x)

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

Versions.

@angular/cli: 1.0.0

Repro steps.

ng build >> log.txt

The log given by the failure.

chunk {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]

Desired functionality.

There’s no way to disable colors in output. Leading to lines and lines of: chunk {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered] in log files. This makes log lines absurdly long and generally reader unfriendly. Plus, the color option being only available for testing makes it even more confusing, as one would expect such an option to be global.

Mention any other details that might be useful.

This is an issue with any non-console or otherwise color unsupporting viewer. For both builds and live reload, in high reliance systems it doesn’t seem viable to constantly designate a terminal window for the output of one component of the product, since 95+% of the time you won’t need it.

[v-karbovnichy]

@sumitarora consider changing the label to type: bug as per previous comment, and also maybe change the priority 🙏

[ivanseidel]

This should be a bare basic option for Angular cli, as it is intended to be used within a CI, and it might not have color support out of the box (With Jenkins + Blue Ocean for instance, it cannot be achieved. And the logs are just crazy and hard to look at)

I think it should be a high priority, as the main reason for a CLI is to be a interface from the User to the Code, and we cannot understand the interface if information is not clear.