Remove custom NPM package prefix #505
Merged
Conversation
This file contains 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
fideloper
added a commit
that referenced
this pull request
Sep 28, 2015
Remove custom NPM package prefix
|
The simpler the better :D thanks! |
|
Awesome, thanks for the swift merge! Can you reply here when you include this in a release? 😁 |
|
well, I'll try, but I doubt I'll remember >.>. Should be some way to get reminded on that.... On Mon, Sep 28, 2015 at 7:42 AM Franz Liedke [email protected]
|
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.
NVM hasn't worked well with the NPM "prefix" option. They added a warning about this in a release seven days ago.
Since global packages are already in the PATH (NVM probably takes care of that), just removing the custom prefix did the job for me. Are there any problems this could cause?
See nvm-sh/nvm#606 and nvm-sh/nvm@a1def71