Restore previous FORCE_COLOR=0 behavior#16362
Conversation
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/56549 |
|
https://github.com/chalk/supports-color/ |
|
Most of that complexity of that package comes from supporting multiple CLI flags (that we do not support) and detecting the level of color support. I would just do the minimal changes done by this PR, and if we want to move to something more reliable we can switch to |
|
Actually, it seems like the only difference is |
|
https://github.com/chalk/supports-color/blob/c214314a14bcb174b12b3014b2b0a8de375029ae/index.js#L126-L136 |
|
Releasing |
Fixes #1, Fixes #2See alexeyraspopov/picocolors#62 and jestjs/jest#14976 (comment). Until the last released we interpreted
FORCE_COLOR=0as disabling color. There is no consensus among tools about whatFORCE_COLOR=0does, but we should not change this behavior in a patch release.