fix: respect NO_COLOR environment variable in dev format - #353
Open
luisangelrod wants to merge 2 commits into
Open
fix: respect NO_COLOR environment variable in dev format#353luisangelrod wants to merge 2 commits into
luisangelrod wants to merge 2 commits into
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The
devformat currently emits ANSI color escape codes unconditionally. This change follows theNO_COLORconvention: color is disabled whenNO_COLORis present and non-empty, while an empty value preserves the existing behavior.Changes
index.jsNO_COLORhas a non-empty value before compiling the dev format.NO_COLORis absent or empty.test/morgan.jsNO_COLOR=1.NO_COLORshell value and restore the original environment after each test.Testing
npm test— 91 passingnpm run lintgit diff --checkCloses #302