Skip to content

Commit

Permalink
Merge pull request #65 from joscha/patch-1
Browse files Browse the repository at this point in the history
docs: add hint about forcing chalk coloring
  • Loading branch information
mysticatea committed Oct 6, 2016
2 parents 51eaa25 + e6c12c9 commit 0d3671a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/npm-run-all.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ Those are similar to [Shell Parameters](http://www.gnu.org/software/bash/manual/
- If `--print-label` option is given, some tools in scripts might stop coloring their output.
Because some coloring library (e.g. [chalk]) will stop coloring if `process.stdout` is not a TTY.
`npm-run-all` changes the `process.stdout` of child processes to a pipe in order to add labels to the head of each line if `--print-label` option is given.<br>
For example, [eslint] stops coloring under `npm-run-all --print-label`. But [eslint] has `--color` option to force coloring, we can use it.
For example, [eslint] stops coloring under `npm-run-all --print-label`. But [eslint] has `--color` option to force coloring, we can use it. For anything [chalk] based you can set the environment variable `FORCE_COLOR=1` to produce colored output anyway.

[glob]: https://www.npmjs.com/package/glob#glob-primer
[chalk]: https://www.npmjs.com/package/chalk
Expand Down

0 comments on commit 0d3671a

Please sign in to comment.