File Manager

X7ROOT File Manager

Current Path: /opt/alt/alt-nodejs12/root/usr/lib/node_modules/npm/docs/content/cli-commands

opt / alt / alt-nodejs12 / root / usr / lib / node_modules / npm / docs / content / cli-commands /

📁 ..
📄 npm-access.md(2.87 KB)
📄 npm-adduser.md(2.93 KB)
📄 npm-audit.md(4.08 KB)
📄 npm-bin.md(452 B)
📄 npm-bugs.md(1.08 KB)
📄 npm-build.md(645 B)
📄 npm-bundle.md(416 B)
📄 npm-cache.md(2.73 KB)
📄 npm-ci.md(1.92 KB)
📄 npm-completion.md(936 B)
📄 npm-config.md(1.62 KB)
📄 npm-dedupe.md(1.44 KB)
📄 npm-deprecate.md(953 B)
📄 npm-dist-tag.md(2.95 KB)
📄 npm-docs.md(1.14 KB)
📄 npm-doctor.md(4.65 KB)
📄 npm-edit.md(1.07 KB)
📄 npm-explore.md(1.04 KB)
📄 npm-fund.md(1.59 KB)
📄 npm-help-search.md(910 B)
📄 npm-help.md(989 B)
📄 npm-hook.md(1.88 KB)
📄 npm-init.md(2.17 KB)
📄 npm-install-ci-test.md(438 B)
📄 npm-install-test.md(832 B)
📄 npm-install.md(19.03 KB)
📄 npm-link.md(2.75 KB)
📄 npm-logout.md(1.28 KB)
📄 npm-ls.md(2.57 KB)
📄 npm-org.md(1.01 KB)
📄 npm-outdated.md(3.86 KB)
📄 npm-owner.md(1.22 KB)
📄 npm-pack.md(1.01 KB)
📄 npm-ping.md(519 B)
📄 npm-prefix.md(678 B)
📄 npm-profile.md(2.89 KB)
📄 npm-prune.md(1.38 KB)
📄 npm-publish.md(3.12 KB)
📄 npm-rebuild.md(495 B)
📄 npm-repo.md(774 B)
📄 npm-restart.md(962 B)
📄 npm-root.md(438 B)
📄 npm-run-script.md(3.49 KB)
📄 npm-search.md(2.85 KB)
📄 npm-shrinkwrap.md(1004 B)
📄 npm-star.md(591 B)
📄 npm-stars.md(614 B)
📄 npm-start.md(798 B)
📄 npm-stop.md(452 B)
📄 npm-team.md(2.2 KB)
📄 npm-test.md(469 B)
📄 npm-token.md(2.8 KB)
📄 npm-uninstall.md(1.53 KB)
📄 npm-unpublish.md(1.45 KB)
📄 npm-update.md(3.39 KB)
📄 npm-version.md(4.47 KB)
📄 npm-view.md(3.19 KB)
📄 npm-whoami.md(385 B)
📄 npm.md(5.31 KB)

Editing: npm-update.md

---
section: cli-commands 
title: npm-update
description: Update a package
---

# npm-update(1)

## Update a package

### 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.

As of `npm@2.6.1`, the `npm update` will only inspect top-level packages.
Prior versions of `npm` would also recursively inspect all dependencies.
To get the old behavior, use `npm --depth 9999 update`.

As of `npm@5.0.0`, the `npm update` will change `package.json` to save the 
new version as the minimum required dependency. To get the old behavior, 
use `npm update --no-save`.

### Example

IMPORTANT VERSION NOTE: these examples assume `npm@2.6.1` or later.  For
older versions of `npm`, you must specify `--depth 0` to get the behavior
described below.

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 does 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](/cli-commands/npm-install)
* [npm outdated](/cli-commands/npm-outdated)
* [npm shrinkwrap](/cli-commands/npm-shrinkwrap)
* [npm registry](/using-npm/registry)
* [npm folders](/configuring-npm/folders)
* [npm ls](/cli-commands/npm-ls)

X7ROOT File Manager

Editing: npm-update.md

Upload File

Create Folder