Skip to content

docs: use the latest version for global update and outdated's wanted #9401

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.

Sign up for GitHub

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

Open
liangmiQwQ wants to merge 2 commits into
base: latest
Choose a base branch
from
+2 −3
Open

docs: use the latest version for global update and outdated's wanted #9401

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fba909a
docs(outdated): make `wanted` be latest version
liangmiQwQ May 24, 2026
e31d9fc
docs
liangmiQwQ Jun 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/lib/content/commands/npm-outdated.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Use `--all` to find all outdated meta-dependencies as well.
In the output:

* `wanted` is the maximum version of the package that satisfies the semver range specified in `package.json`.
If there's no available semver range (i.e. you're running `npm outdated --global`, or the package isn't included in `package.json`), then `wanted` shows the currently-installed version.
If there's no available semver range (i.e. you're running `npm outdated --global`, or the package isn't included in `package.json`), then `wanted` shows the latest version.
* `latest` is the version of the package tagged as latest in the registry.
Running `npm publish` with no special configuration will publish the package with a dist-tag of `latest`.
This may or may not be the maximum version of the package, or the most-recently published version of the package, depending on how the package's developer manages the latest [dist-tag](/commands/npm-dist-tag).
Expand Down
3 changes: 1 addition & 2 deletions docs/lib/content/commands/npm-update.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,8 +128,7 @@ In this case if you really did need your package to use a newer version you woul

`npm update -g` will apply the `update` action to each globally installed package that is `outdated` -- that is, has a version that is different from `wanted`.

Note: Globally installed packages are treated as if they are installed with a caret semver range specified.
So if you require to update to `latest` you may need to run `npm install -g [<pkg>...]`
Note: Globally installed packages do not have a `package.json` semver range available, so their `wanted` version is `latest`.

NOTE: If a package has been upgraded to a version newer than `latest`, it will be _downgraded_.

Expand Down