Skip to content

Commit 7d8e5b9

Browse files
johnkennedy9147darcyclarke
authored andcommitted
docs:correction to npm update -g behaviour
PR-URL: #755 Credit: @ Close: #755 Reviewed-by: @darcyclarke
1 parent 0eac801 commit 7d8e5b9

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/content/cli-commands/npm-update.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,9 @@ version that satisfies `^0.4.0` (`>= 0.4.0 <0.5.0`)
122122

123123
`npm update -g` will apply the `update` action to each globally installed
124124
package that is `outdated` -- that is, has a version that is different from
125-
`latest`.
125+
`wanted`.
126+
127+
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>...]`
126128

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

0 commit comments

Comments
 (0)