Skip to content
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

docs:correction to npm update -g behaviour #755

Conversation

johnkennedy9147
Copy link
Contributor

What / Why

The docs state that running npm update -g will update globally installed packages to latest

image

The 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

@johnkennedy9147 johnkennedy9147 requested a review from a team as a code owner February 1, 2020 15:45
@mikemimik mikemimik added Priority Backlog a "backlogged" item that will be tracked in a Project Board Community Enhancement new feature or improvement semver:patch semver patch level for changes labels Feb 12, 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement new feature or improvement Priority Backlog a "backlogged" item that will be tracked in a Project Board semver:patch semver patch level for changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] npm update global not updating packages to latest
2 participants