-
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
[BUG] npm update global not updating packages to latest #746
Comments
They update to “wanted”, not “latest”. Global packages have an implicit ^ semver range, i believe. |
verbose logging revealed that it is indeed deliberate
and found the decision point in the code Lines 42 to 48 in f533d61
|
npm If your bug is preproducible on If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo Closing: This is an automated message. |
Attempting to update all globally installed packages docs state should go to latest but this does not happen. Possibly updating as if applying semver ^ range.
npm outdated
shows:ran npm update
npm outdated
now showsExpectation was that both would have been updated to latest.
eslint not updated.
lighthouse only updated to highest V4 version published (consistent with semver ^)
The text was updated successfully, but these errors were encountered: