Skip to content
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

fix(config): consolidate use of npm.color #3563

Merged
merged 1 commit into from Jul 22, 2021
Merged

Conversation

wraithgar
Copy link
Member

@wraithgar wraithgar commented Jul 20, 2021

The config value for color should never be directly read by npm, or
its submodules. The derived value npm.color or
npm.flatOptions.color is what we want to use.

This PR consolidates the use of these values, makes sure there is only
one place the value is actually calculated, and stops relying on
duplicated code in the setup-log.js file for setting one of them.

Closes npm/statusboard#372

The config value for `color` should never be directly read by npm, or
its submodules.  The derived value `npm.color` or
`npm.flatOptions.color` is what we want to use.

This PR consolidates the use of these values, makes sure there is only
one place the value is actually calculated, and stops relying on
duplicated code in the setup-log.js file for setting one of them.

PR-URL: #3563
Credit: @wraithgar
Close: #3563
Reviewed-by: @lukekarrys
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants