You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/lib/content/commands/npm-update.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,8 +128,7 @@ In this case if you really did need your package to use a newer version you woul
128
128
129
129
`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`.
130
130
131
-
Note: Globally installed packages are treated as if they are installed with a caret semver range specified.
132
-
So if you require to update to `latest` you may need to run `npm install -g [<pkg>...]`
131
+
Note: Globally installed packages do not have a `package.json` semver range available, so their `wanted` version is `latest`.
133
132
134
133
NOTE: If a package has been upgraded to a version newer than `latest`, it will be _downgraded_.
0 commit comments