mirror of
https://github.com/nodejs/node.git
synced 2025-05-16 15:50:47 +00:00
d3906ae294
PR-URL: https://github.com/nodejs/node/pull/37117 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
128 lines
2.8 KiB
Markdown
128 lines
2.8 KiB
Markdown
---
|
|
title: npm-update
|
|
section: 1
|
|
description: Update packages
|
|
---
|
|
|
|
### Synopsis
|
|
|
|
```bash
|
|
npm update [-g] [<pkg>...]
|
|
|
|
aliases: up, upgrade
|
|
```
|
|
|
|
### Description
|
|
|
|
This command will update all the packages listed to the latest version
|
|
(specified by the `tag` config), respecting semver.
|
|
|
|
It will also install missing packages. As with all commands that install
|
|
packages, the `--dev` flag will cause `devDependencies` to be processed
|
|
as well.
|
|
|
|
If the `-g` flag is specified, this command will update globally installed
|
|
packages.
|
|
|
|
If no package name is specified, all packages in the specified location (global
|
|
or local) will be updated.
|
|
|
|
### Example
|
|
|
|
For the examples below, assume that the current package is `app` and it depends
|
|
on dependencies, `dep1` (`dep2`, .. etc.). The published versions of `dep1`
|
|
are:
|
|
|
|
```json
|
|
{
|
|
"dist-tags": { "latest": "1.2.2" },
|
|
"versions": [
|
|
"1.2.2",
|
|
"1.2.1",
|
|
"1.2.0",
|
|
"1.1.2",
|
|
"1.1.1",
|
|
"1.0.0",
|
|
"0.4.1",
|
|
"0.4.0",
|
|
"0.2.0"
|
|
]
|
|
}
|
|
```
|
|
|
|
#### Caret Dependencies
|
|
|
|
If `app`'s `package.json` contains:
|
|
|
|
```json
|
|
"dependencies": {
|
|
"dep1": "^1.1.1"
|
|
}
|
|
```
|
|
|
|
Then `npm update` will install `dep1@1.2.2`, because `1.2.2` is `latest` and
|
|
`1.2.2` satisfies `^1.1.1`.
|
|
|
|
#### Tilde Dependencies
|
|
|
|
However, if `app`'s `package.json` contains:
|
|
|
|
```json
|
|
"dependencies": {
|
|
"dep1": "~1.1.1"
|
|
}
|
|
```
|
|
|
|
In this case, running `npm update` will install `dep1@1.1.2`. Even though the
|
|
`latest` tag points to `1.2.2`, this version do not satisfy `~1.1.1`, which is
|
|
equivalent to `>=1.1.1 <1.2.0`. So the highest-sorting version that satisfies
|
|
`~1.1.1` is used, which is `1.1.2`.
|
|
|
|
#### Caret Dependencies below 1.0.0
|
|
|
|
Suppose `app` has a caret dependency on a version below `1.0.0`, for example:
|
|
|
|
```json
|
|
"dependencies": {
|
|
"dep1": "^0.2.0"
|
|
}
|
|
```
|
|
|
|
`npm update` will install `dep1@0.2.0`, because there are no other
|
|
versions which satisfy `^0.2.0`.
|
|
|
|
If the dependence were on `^0.4.0`:
|
|
|
|
```json
|
|
"dependencies": {
|
|
"dep1": "^0.4.0"
|
|
}
|
|
```
|
|
|
|
Then `npm update` will install `dep1@0.4.1`, because that is the highest-sorting
|
|
version that satisfies `^0.4.0` (`>= 0.4.0 <0.5.0`)
|
|
|
|
|
|
#### Updating Globally-Installed Packages
|
|
|
|
`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`.
|
|
|
|
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_.
|
|
|
|
|
|
### See Also
|
|
|
|
* [npm install](/commands/npm-install)
|
|
* [npm outdated](/commands/npm-outdated)
|
|
* [npm shrinkwrap](/commands/npm-shrinkwrap)
|
|
* [npm registry](/using-npm/registry)
|
|
* [npm folders](/configuring-npm/folders)
|
|
* [npm ls](/commands/npm-ls)
|