docs:correction to npm update -g behaviour#755
Closed
johnkennedy9147 wants to merge 1 commit into
Closed
Conversation
This was referenced Apr 11, 2020
This was referenced Apr 22, 2020
Amorymeltzer
added a commit
to Amorymeltzer/dotfiles
that referenced
this pull request
Jun 3, 2020
There's a long trail here (from npm/npm#11534 to npm/cli#755) but basically, npm installs globals as if there were a caret given in the version, so that `npm upgrade -g` won't ever do anything beyond that semver. Thus, we need to actually pass each individual package name to `npm install` (note: install, not upgrade) in order to actually update packages.
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
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.
What / Why
The docs state that running
npm update -gwill update globally installed packages to latestThe actual behaviour is to upgrading with an implicit caret range specified to the globally installed packages, this means that it will not always update to latest.
This PR updates the docs to make this clear.
References