[colors.js](https://github.com/Marak/colors.js) used to be the most popular string styling module, but it has serious deficiencies like extending `String.prototype` which causes all kinds of [problems](https://github.com/yeoman/yo/issues/68). Although there are other ones, they either do too much or not enough.
Chain[styles](#styles)andcallthelastoneasamethodwithastringargument.Orderdoesn'tmatter,andlaterstylestakeprecedentincaseofaconflict.Thissimplymeansthat`Chalk.red.yellow.green` is equivalent to `Chalk.green`.
Detectwhethertheterminal[supportscolor](https://github.com/chalk/supports-color). Used internally and handled for you, but exposed for convenience.
Canbeoverriddenbytheuserwiththeflags`--color` and `--no-color`. For situations where using `--color` is not possible, add an environment variable `FORCE_COLOR` with any value to force color. Trumps `--no-color`.
Chalkdoesnotsupportanythingotherthanthebaseeightcolors,whichguaranteesitwillworkonallterminalsandsystems.Someterminals,specifically`xterm`compliantones,willsupportthefullrangeof8-bitcolors.Forthisthelowerlevel[ansi-256-colors](https://github.com/jbnicolai/ansi-256-colors) package can be used.
##Windows
Ifyou'reonWindows,doyourselfafavoranduse[`cmder`](http://bliker.github.io/cmder/) instead of `cmd.exe`.
##Related
-[chalk-cli](https://github.com/chalk/chalk-cli) - CLI for this module
-[ansi-styles](https://github.com/chalk/ansi-styles/) - ANSI escape codes for styling strings in the terminal
-[supports-color](https://github.com/chalk/supports-color/) - Detect whether a terminal supports color