3 ms·
Chalk[0][1] maintainer here. We've gone over this, uh... call to arms? a number of times before. AMA. [0] https://github.com/chalk https://github.com/chalk [1
by junon 3y ago
Chalk[0][1] maintainer here. We've gone over this, uh... call to arms? a number of times before. AMA.
[0] https://github.com/chalk https://github.com/chalk
[1] https://npmjs.org/package/chalk https://npmjs.org/package/chalk
- kps 3y agoThe examples seem to encourage hard-coding specific colours, and includes examples that are unreadable on a light background. chalk.bgHex('#DEADED').underline('Hello, world!')
- junon 3y agoWe don't encourage it, we just supply the functionality. There's no fix here - terminal colors are inherently environment-unaware aside from the basic 16 (8 dark, 8 light).
- tgv 3y agoWhy not add env("NO_COLOR") to it as an equivalent of FORCE_COLOR=0?
- junon 3y agoBecause we've had 5nor 6 of these standards and it becomes unclear which one should take precedence. If FORCE_COLOR=1 and NO_COLOR is defined, which one wins? FORCE_COLOR was the first we had found that was also present in other Unix utilities and thus the one that won.
- tgv 3y agoI'm a bit late, but perhaps you could write the no-color website maintainer, and ask to link to similar projects? Then we could see all options to disable or forcibly enable color in one glance.