Skip to content

Commit

Permalink
docs:correction to npm update -g behaviour
Browse files Browse the repository at this point in the history
PR-URL: #755
Credit: @
Close: #755
Reviewed-by: @darcyclarke
  • Loading branch information
johnkennedy9147 authored and darcyclarke committed Mar 18, 2020
1 parent 0eac801 commit 7d8e5b9
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion docs/content/cli-commands/npm-update.md
Expand Up @@ -122,7 +122,9 @@ version that satisfies `^0.4.0` (`>= 0.4.0 <0.5.0`)

`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
`latest`.
`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: If a package has been upgraded to a version newer than `latest`, it will
be _downgraded_.
Expand Down

0 comments on commit 7d8e5b9

Please sign in to comment.