2.1.0 release Breaking/Broken

Platform: Windows Server 2012 R2 Console: Cmder Node Version: v8.1.4

Example code that worked before 2.1.0 release:

const chalk = require('chalk');
const clk = new chalk.constructor({ enabled: true });

console.log(`${clk.bgBlue("Text with blue background")}${clk.bgMagenta("Text with magenta background")} ect`);

2.0.1:

2.1.0:

[kyranet]

Evaluating process.stdout.isTTY returned undefined in PM2 and the value for process.stdout._type is pipe, however, in a normal Node.js process, the first returned true and _type is tty:

The returned value of console.log(process.stdout); with PM2:

Socket {
  connecting: false,
  _hadError: false,
  _handle: [Object],
  _parent: null,
  _host: null,
  _readableState: [Object],
  readable: false,
  domain: null,
  _events: [Object],
  _eventsCount: 3,
  _maxListeners: undefined,
  _writableState: [Object],
  writable: true,
  allowHalfOpen: false,
  _bytesDispatched: 528,
  _sockname: null,
  _pendingData: null,
  _pendingEncoding: '',
  server: null,
  _server: null,
  _type: 'pipe',
  fd: 1,
  _isStdio: true,
  destroySoon: [Object],
  _destroy: [Object],
  [Symbol(asyncId)]: 10,
  [Symbol(bytesRead)]: 0 }

The returned value of console.log(process.stdout); without PM2:

WriteStream {
  connecting: false,
  _hadError: false,
  _handle: [Object],
  _parent: null,
  _host: null,
  _readableState: [Object],
  readable: false,
  domain: null,
  _events: [Object],
  _eventsCount: 4,
  _maxListeners: undefined,
  _writableState: [Object],
  writable: true,
  allowHalfOpen: false,
  _bytesDispatched: 100,
  _sockname: null,
  _writev: null,
  _pendingData: null,
  _pendingEncoding: '',
  server: null,
  _server: null,
  columns: 238, 
  rows: 61,
  _type: 'tty',
  fd: 1,
  _isStdio: true,
  destroySoon: [Function: destroy],
  _destroy: [Function],
  [Symbol(asyncId)]: 2,
  [Symbol(bytesRead)]: 0 }

[Qix-]

Thanks for the confirm @CyberiumShadow.

Yeah, to be honest it sounds like supports-color was broken before v2 - this is actually intended behavior.

Please use FORCE_COLOR=1 if you need it. Remember that any time you run your script inside of a wrapper (e.g. PM2) where it spawns a new node process, it’s most likely going to cause isatty() to return 0 under the hood, causing process.stdout.isTTY to be false-ey.

You’re more than welcome to file a ticket over at PM2 to use pseudo-terminals upon spawning, but IIRC that’s a ton of work from the Node.js end and not cross-platform compatible.

Closing unless someone has reason to believe this is unintended functionality.

Thanks for the report and all of the correspondence.