(GH-121) Add support for reading npm configuration - #123
Draft
pascalberger wants to merge 1 commit into
Draft
Conversation
pascalberger
commented
Aug 29, 2020
pascalberger
left a comment
pascalberger
left a comment
Member
Author
There was a problem hiding this comment.
I would call this config not get since npm get is just a shorthand for npm config get. This would allow to add additional config functionality in the future. Aliases should follow the structure of other aliases (one with default settings, one with a configurator and one where a settings object can be past). Requires test cases, comments for public API and should follow code style of the project.
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
2 participants
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 support for npm get.
Splitted from #102 .
Fixes #121