f118062594
* Fix workflow * Trigger * [auto] Update compiled version * [auto] Commit modules * Push Windows changes * Fix * [auto] Update compiled version * Try removing cwd * [auto] Update compiled version * Try with path module * [auto] Update compiled version * Fix path * [auto] Update compiled version * Use raw path * [auto] Update compiled version * Other path * [auto] Update compiled version * Avoid @action/exec * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * Try with shelljs * [auto] Update compiled version * Fix my stupidity * Copy scripts to local dir * [auto] Update compiled version * Still use path * [auto] Update compiled version * Delete entrypoint.sh * [auto] Update compiled version * Make file executable * [auto] Update compiled version * Try using bash * [auto] Update compiled version
supports-color 
Detect whether a terminal supports color
Install
$ npm install --save supports-color
Usage
var supportsColor = require('supports-color');
if (supportsColor) {
console.log('Terminal supports color');
}
It obeys the --color and --no-color CLI flags.
For situations where using --color is not possible, add an environment variable FORCE_COLOR with any value to force color. Trumps --no-color.
Related
- supports-color-cli - CLI for this module
- chalk - Terminal string styling done right
License
MIT © Sindre Sorhus