-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
npm-link: clarify usage of global prefix #532
Closed
Closed
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
In wondered why npm link doesn't "install to" `npm prefix`. I looked up the documentation for `npm prefix` and found the important distinction between the local prefix, and the global prefix. This attempts to clarity that `npm link` always uses specifically the global prefix.
ruyadorno
added
Release 6.x
work is associated with a specific npm 6 release
semver:patch
semver patch level for changes
labels
Jan 9, 2020
ruyadorno
approved these changes
Jan 9, 2020
ruyadorno
pushed a commit
that referenced
this pull request
Jan 9, 2020
In wondered why npm link doesn't "install to" `npm prefix`. I looked up the documentation for `npm prefix` and found the important distinction between the local prefix, and the global prefix. This attempts to clarity that `npm link` always uses specifically the global prefix. PR-URL: #532 Credit: @jgehrcke Close: #532 Reviewed-by: @ruyadorno
This was referenced Jan 10, 2020
Merged
This was referenced Jan 18, 2020
Closed
This was referenced Feb 10, 2020
This was referenced Feb 25, 2020
This was referenced Mar 9, 2020
This was referenced Mar 17, 2020
This was referenced Mar 26, 2020
This was referenced Apr 11, 2020
This was referenced Jun 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Release 6.x
work is associated with a specific npm 6 release
semver:patch
semver patch level for changes
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.
In wondered why npm link doesn't "install to"
npm prefix
.I looked up the documentation for
npm prefix
and foundthe important distinction between the local prefix, and the
global prefix.
This attempts to clarity that
npm link
always uses specificallythe global prefix.