-
Notifications
You must be signed in to change notification settings - Fork 465
feat(cli): honor NO_COLOR #8331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
DavidWells
wants to merge
1
commit into
main
Choose a base branch
from
split/no-color
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| import { afterEach, describe, expect, test, vi } from 'vitest' | ||
|
|
||
| import { shouldDisableColors } from '../../../src/utils/command-helpers.js' | ||
|
|
||
| describe('NO_COLOR support', () => { | ||
| afterEach(() => { | ||
| vi.unstubAllEnvs() | ||
| vi.resetModules() | ||
| }) | ||
|
|
||
| test('shouldDisableColors is true for any non-empty NO_COLOR value', () => { | ||
| expect(shouldDisableColors({ NO_COLOR: '1' })).toBe(true) | ||
| expect(shouldDisableColors({ NO_COLOR: 'true' })).toBe(true) | ||
| expect(shouldDisableColors({ NO_COLOR: '0' })).toBe(true) | ||
| }) | ||
|
|
||
| test('shouldDisableColors is false when NO_COLOR is unset or empty', () => { | ||
| expect(shouldDisableColors({})).toBe(false) | ||
| expect(shouldDisableColors({ NO_COLOR: '' })).toBe(false) | ||
| }) | ||
|
|
||
| test('chalk is initialized colorless when NO_COLOR is set', async () => { | ||
| vi.stubEnv('NO_COLOR', '1') | ||
| const { chalk } = await import('../../../src/utils/command-helpers.js') | ||
| expect(chalk.level).toBe(0) | ||
| expect(chalk.red('plain')).toBe('plain') | ||
| }) | ||
| }) |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chalk already implements all the various colour detection stuff (much more than just NO_COLOR), the problem is that we're overriding that entirely by passing
argv.includes('--json'). chalk exportssupportsColorso we should be able to just import that and change to something likeargv.includes('--json') || supportsColor(that probably isn't right, but you get the idea).https://main.npmx.dev/package/chalk#user-content-supportscolor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good instinct, but I checked and chalk doesn't actually handle
NO_COLOR. It's a deliberate omission on their side.The
supports-colorlogic chalk 5.6.2 ships (vendored atnode_modules/chalk/source/vendor/supports-color/index.js) checks--no-color/--colorflags,FORCE_COLOR, TTY status, CI env vars, andTERM, but there is zero mention ofNO_COLORanywhere in the file. The chalk maintainers have declined to support it for years and point people toFORCE_COLOR=0instead (e.g. chalk/supports-color#105). Soargv.includes('--json') || !supportsColorwould silently drop theNO_COLORbehavior this PR exists to add.Also a small clarification on the "overriding entirely" part: we only override in the force-off case. When the arg is false,
safeChalkreturnsnew Chalk(), which still runs chalk's full auto-detection, so TTY/CI/FORCE_COLOR handling is already intact for chalk output today.That said, your suggestion does point at a real gap for prettyjson: it does its own coloring and knows nothing about chalk's detection, so piped
netlify statusoutput gets ANSI codes today even withoutNO_COLOR. Pulling insupportsColorthere in addition to (not instead of) theNO_COLORcheck would fix that:Happy to add that here if you're on board, or split it into a follow-up.