docs: use the latest version for global update and outdated's wanted#9401
Open
liangmiQwQ wants to merge 2 commits into
Open
docs: use the latest version for global update and outdated's wanted#9401liangmiQwQ wants to merge 2 commits into
wanted#9401liangmiQwQ wants to merge 2 commits into
Conversation
owlstronaut
requested changes
Jun 2, 2026
Contributor
owlstronaut
left a comment
owlstronaut
left a comment
There was a problem hiding this comment.
Could you also update npm-update.md in this pr? The "treated as if installed with a caret semver range" not has the same mismatch with actual behavior and contradicts the fix you're making here
liangmiQwQ
changed the title
wanted be latest versionwanted
Author
I've updated in e31d9fc, and PR title is updated to fit the new scope as well. Thanks. |
liangmiQwQ
changed the title
wantedwanted
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
2 participants
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.
For now,
npm outdated's document showswantedfield for globalnpm outdatedis always the same ascurrentfield, but the runtime behavior showsnpm outdatedprintswantedas latest version. Consideringnpm update's behavior, it should be a document issue.This PR fixes it by saying
the latest versioninstead ofcurrently-installed version.References
Close #3612