Closed bcomnes closed 2 months ago
a potential related approach to possibly consider: https://github.com/mysticatea/npm-run-all/issues/131
Oh good technique. Will add it to the docs and see if I can patch it into the labels. I noticed that there is already a known issues section.
If it's eg chalk that deactivate the color then we should maybe check if we could upstream it to not just check TTY but also that env variable?
The force color env var works pretty well. Been playing with that.
Using env vars and whatnot, I think thats probably the best solution with this flag for now.
When using the
--print-label
option, colors are stripped from the log output. It would be preferable if that wasn't the case.