This repository has been archived by the owner on Nov 3, 2022. It is now read-only.
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.
Add a new method
isDefault(key)
that enables a way to know if thevalue to be returned by a
config.get(key)
call is coming from thedefault definitions or any other different source. In case it's coming
from the default values this method returns
true
, it returnsfalse
otherwise.
This addition is going to allow for effectively managing different
default values in the npm cli on a command-basis, e.g:
The
save
config default value in the npm cli istrue
, so that innpm install
and other commands that value is always going to defaultto true if no user config is provided. Now let's say we want to use a
different value in
npm update
, for examplesave=false
. This changeenables us to have a conditional check to see if the
save
config valueis coming from the default source, thus providing a way to use a
different value instead of the default:
Relates to: npm/cli#4223
Relates to: npm/statusboard#324
References