Does not work when piped into bunyan about chalk HOT 4 CLOSED

Whew, after banging my head against the wall how the exact same string, produced by two different libraries, could possibly act different I finally realised it's because you ran chalk headless.

If you look here in chalk you see that it get's disabled if it's not running in a TTY.

This is an optimisation to prevent to colorisation of strings that aren't being printed to stdout anyway. It is imho questionable if this is valid, as it means that a user of chalk may unexpectedly not get styled strings even though he explicitly applied styles to them. Perhaps something to reconsider, @sindresorhus ?

Wrapping up, this is expected behaviour, @apriendeau, and you can get your desired results by explicitly setting chalk.enabled = true.

var colors   = require('colors')
var chalk    = require('chalk')
chalk.enabled = true

console.log(chalk.blue('test'))
console.log('test'.blue)

Will now work when piped through through bunyan

from chalk.

nice @jbnicolai thanks so much!

from chalk.

You can also force color by using the --color flag in the CLI. The most common case is not wanting colors when piped and chalk optimizes for that usecase.

from chalk.

A terminal without color is a terminal that I do not want to live in. Thanks for the help!

from chalk.