NO_COLOR=1 doesn't turn off intercepted console logging color

[hi-ogawa]

Describe the bug

Test file:

import { test } from 'vitest';

test('console color', () => {
  console.log(['string', /regexp/, 1234, true, null, undefined]);
});

Output:

$ NO_COLOR=1 npm run test
...
stdout | test/repro.test.ts > console color
[ 'string', /regexp/, 1234, true, null, undefined ]       /// <-- this always gets highlighted

Reveal screenshot

---

This is probably because of forced colorMode for the custom Console instance. Since this is node runtime only feature, I think it might be natural to do the same color detection as other places (like reporters) so that NO_COLOR would be also taken into account.

vitest/packages/vitest/src/runtime/console.ts

Lines 128 to 133 in b561c32

	return new Console({
	stdout,
	stderr,
	colorMode: true,
	groupIndentation: 2,
	})

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-gvgl5a?file=test%2Frepro.test.ts

System Info

(stackblitz)

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
    pnpm: 8.14.0 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: latest => 1.2.0 
    vite: latest => 5.0.11 
    vitest: latest => 1.2.0

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.