(Windows) Consider using standard color scheme when term is xterm like

[weikinhuang]

perhaps check for:

process.platform === 'win32' && !process.env.TERM
or
process.platform === 'win32' && !(/xterm/).test(process.env.TERM || "")

I am suggesting this because I use node through a solarized color shell (admittedly through cygwin ssh).

Thanks.

[shinnn]

@weikinhuang Why current version doesn't meet your requirements? Current / expected screenshot is very welcome.

[weikinhuang]

Sure thing, here's the screenshot (using SecureCRT, with xterm-256 emulator mode):

"use strict";

const chalk = require("chalk");

[ "black", "red", "green", "yellow", "blue", "magenta", "cyan", "white", "gray" ].forEach(function(color) {
    process.stdout.write(chalk[color](color) + " ");
});
process.stdout.write("\n");

[ "bgBlack", "bgRed", "bgGreen", "bgYellow", "bgBlue", "bgMagenta", "bgCyan", "bgWhite" ].forEach(function(color) {
    process.stdout.write(chalk[color](color) + " ");
});
process.stdout.write("\n");

[shinnn]

I say again:

Why current version doesn't meet your requirements?

The screenshot looks good to me.

[weikinhuang]

Ah, sorry.
Since I'm on a xterm console (instead of cmd or something) I expect that blue would show up as blue and not a grey color even though I'm on windows.

The following would be the expected behavior:

I'm specifically referring to the blue foreground text color.

[shinnn]

Ah, OK. You meant that chalk should disable these lines on the terminals with solarized color theme?

[weikinhuang]

Ya, but not necessarily with a solarized theme, but terminals that supports proper colors.

[kevva]

Can you send a PR?

[weikinhuang]

PR sent, I couldn't decide if I should test against xterm or dumb terminal (that's what cmd.exe reports in process.env.TERM).