1#@!#!123s

: / opt / cpanel / ea-nodejs10 / lib / node_modules / npm / man / man1 /

Filename : npm-update.1

back

.TH "NPM\-UPDATE" "1" "March 2021" "" ""
.SH "NAME"
\fBnpm-update\fR \- Update a package
.SS Synopsis
.P
.RS 2
.nf
npm update [\-g] [<pkg>\.\.\.]

aliases: up, upgrade
.fi
.RE
.SS Description
.P
This command will update all the packages listed to the latest version
(specified by the \fBtag\fP config), respecting semver\.
.P
It will also install missing packages\. As with all commands that install
packages, the \fB\-\-dev\fP flag will cause \fBdevDependencies\fP to be processed
as well\.
.P
If the \fB\-g\fP flag is specified, this command will update globally installed
packages\.
.P
If no package name is specified, all packages in the specified location (global
or local) will be updated\.
.P
As of \fBnpm@2\.6\.1\fP, the \fBnpm update\fP will only inspect top\-level packages\.
Prior versions of \fBnpm\fP would also recursively inspect all dependencies\.
To get the old behavior, use \fBnpm \-\-depth 9999 update\fP\|\.
.P
As of \fBnpm@5\.0\.0\fP, the \fBnpm update\fP will change \fBpackage\.json\fP to save the 
new version as the minimum required dependency\. To get the old behavior, 
use \fBnpm update \-\-no\-save\fP\|\.
.SS Example
.P
IMPORTANT VERSION NOTE: these examples assume \fBnpm@2\.6\.1\fP or later\.  For
older versions of \fBnpm\fP, you must specify \fB\-\-depth 0\fP to get the behavior
described below\.
.P
For the examples below, assume that the current package is \fBapp\fP and it depends
on dependencies, \fBdep1\fP (\fBdep2\fP, \.\. etc\.)\.  The published versions of \fBdep1\fP are:
.P
.RS 2
.nf
{
  "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"
  ]
}
.fi
.RE
.SS Caret Dependencies
.P
If \fBapp\fP\|'s \fBpackage\.json\fP contains:
.P
.RS 2
.nf
"dependencies": {
  "dep1": "^1\.1\.1"
}
.fi
.RE
.P
Then \fBnpm update\fP will install \fBdep1@1\.2\.2\fP, because \fB1\.2\.2\fP is \fBlatest\fP and
\fB1\.2\.2\fP satisfies \fB^1\.1\.1\fP\|\.
.SS Tilde Dependencies
.P
However, if \fBapp\fP\|'s \fBpackage\.json\fP contains:
.P
.RS 2
.nf
"dependencies": {
  "dep1": "~1\.1\.1"
}
.fi
.RE
.P
In this case, running \fBnpm update\fP will install \fBdep1@1\.1\.2\fP\|\.  Even though the \fBlatest\fP
tag points to \fB1\.2\.2\fP, this version does not satisfy \fB~1\.1\.1\fP, which is equivalent
to \fB>=1\.1\.1 <1\.2\.0\fP\|\.  So the highest\-sorting version that satisfies \fB~1\.1\.1\fP is used,
which is \fB1\.1\.2\fP\|\.
.SS Caret Dependencies below 1\.0\.0
.P
Suppose \fBapp\fP has a caret dependency on a version below \fB1\.0\.0\fP, for example:
.P
.RS 2
.nf
"dependencies": {
  "dep1": "^0\.2\.0"
}
.fi
.RE
.P
\fBnpm update\fP will install \fBdep1@0\.2\.0\fP, because there are no other
versions which satisfy \fB^0\.2\.0\fP\|\.
.P
If the dependence were on \fB^0\.4\.0\fP:
.P
.RS 2
.nf
"dependencies": {
  "dep1": "^0\.4\.0"
}
.fi
.RE
.P
Then \fBnpm update\fP will install \fBdep1@0\.4\.1\fP, because that is the highest\-sorting
version that satisfies \fB^0\.4\.0\fP (\fB>= 0\.4\.0 <0\.5\.0\fP)
.SS Updating Globally\-Installed Packages
.P
\fBnpm update \-g\fP will apply the \fBupdate\fP action to each globally installed
package that is \fBoutdated\fP \-\- that is, has a version that is different from
\fBwanted\fP\|\.
.P
Note: Globally installed packages are treated as if they are installed with a caret semver range specified\. So if you require to update to \fBlatest\fP you may need to run \fBnpm install \-g [<pkg>\.\.\.]\fP
.P
NOTE: If a package has been upgraded to a version newer than \fBlatest\fP, it will
be \fIdowngraded\fR\|\.
.SS See Also
.RS 0
.IP \(bu 2
npm help install
.IP \(bu 2
npm help outdated
.IP \(bu 2
npm help shrinkwrap
.IP \(bu 2
npm help registry
.IP \(bu 2
npm help folders
.IP \(bu 2
npm help ls

.RE

Name	Size	Last Modified	Owner	Permissions
npm-README.1	4.773 KB	September 13 2023 2:48:05	root	0644
npm-access.1	2.992 KB	September 13 2023 2:48:05	root	0644
npm-adduser.1	3.117 KB	September 13 2023 2:48:05	root	0644
npm-audit.1	4.394 KB	September 13 2023 2:48:05	root	0644
npm-bin.1	0.369 KB	September 13 2023 2:48:05	root	0644
npm-bugs.1	1.05 KB	September 13 2023 2:48:05	root	0644
npm-build.1	0.623 KB	September 13 2023 2:48:05	root	0644
npm-bundle.1	0.399 KB	September 13 2023 2:48:05	root	0644
npm-cache.1	2.761 KB	September 13 2023 2:48:05	root	0644
npm-ci.1	2.004 KB	September 13 2023 2:48:05	root	0644
npm-completion.1	0.937 KB	September 13 2023 2:48:05	root	0644
npm-config.1	1.615 KB	September 13 2023 2:48:05	root	0644
npm-dedupe.1	1.458 KB	September 13 2023 2:48:05	root	0644
npm-deprecate.1	0.929 KB	September 13 2023 2:48:05	root	0644
npm-dist-tag.1	3.18 KB	September 13 2023 2:48:05	root	0644
npm-docs.1	1.137 KB	September 13 2023 2:48:05	root	0644
npm-doctor.1	4.835 KB	September 13 2023 2:48:05	root	0644
npm-edit.1	1.067 KB	September 13 2023 2:48:05	root	0644
npm-explore.1	1.105 KB	September 13 2023 2:48:05	root	0644
npm-fund.1	1.683 KB	September 13 2023 2:48:05	root	0644
npm-help-search.1	0.903 KB	September 13 2023 2:48:05	root	0644
npm-help.1	0.941 KB	September 13 2023 2:48:05	root	0644
npm-hook.1	2.047 KB	September 13 2023 2:48:05	root	0644
npm-init.1	2.365 KB	September 13 2023 2:48:05	root	0644
npm-install-ci-test.1	0.289 KB	September 13 2023 2:48:05	root	0644
npm-install-test.1	0.736 KB	September 13 2023 2:48:05	root	0644
npm-install.1	19.63 KB	September 13 2023 2:48:05	root	0644
npm-link.1	2.795 KB	September 13 2023 2:48:05	root	0644
npm-logout.1	1.251 KB	September 13 2023 2:48:05	root	0644
npm-ls.1	2.791 KB	September 13 2023 2:48:05	root	0644
npm-org.1	1.093 KB	September 13 2023 2:48:05	root	0644
npm-outdated.1	4.278 KB	September 13 2023 2:48:05	root	0644
npm-owner.1	1.21 KB	September 13 2023 2:48:05	root	0644
npm-pack.1	0.962 KB	September 13 2023 2:48:05	root	0644
npm-ping.1	0.496 KB	September 13 2023 2:48:05	root	0644
npm-prefix.1	0.603 KB	September 13 2023 2:48:05	root	0644
npm-profile.1	3.49 KB	September 13 2023 2:48:05	root	0644
npm-prune.1	1.428 KB	September 13 2023 2:48:05	root	0644
npm-publish.1	3.144 KB	September 13 2023 2:48:05	root	0644
npm-rebuild.1	0.453 KB	September 13 2023 2:48:05	root	0644
npm-repo.1	0.754 KB	September 13 2023 2:48:05	root	0644
npm-restart.1	0.934 KB	September 13 2023 2:48:05	root	0644
npm-root.1	0.364 KB	September 13 2023 2:48:05	root	0644
npm-run-script.1	3.689 KB	September 13 2023 2:48:05	root	0644
npm-search.1	3.108 KB	September 13 2023 2:48:05	root	0644
npm-shrinkwrap.1	0.827 KB	September 13 2023 2:48:05	root	0644
npm-star.1	0.53 KB	September 13 2023 2:48:05	root	0644
npm-stars.1	0.525 KB	September 13 2023 2:48:05	root	0644
npm-start.1	0.729 KB	September 13 2023 2:48:05	root	0644
npm-stop.1	0.372 KB	September 13 2023 2:48:05	root	0644
npm-team.1	2.256 KB	September 13 2023 2:48:05	root	0644
npm-test.1	0.389 KB	September 13 2023 2:48:05	root	0644
npm-token.1	3.675 KB	September 13 2023 2:48:05	root	0644
npm-uninstall.1	1.63 KB	September 13 2023 2:48:05	root	0644
npm-unpublish.1	1.379 KB	September 13 2023 2:48:05	root	0644
npm-update.1	3.726 KB	September 13 2023 2:48:05	root	0644
npm-version.1	4.84 KB	September 13 2023 2:48:05	root	0644
npm-view.1	3.26 KB	September 13 2023 2:48:05	root	0644
npm-whoami.1	0.333 KB	September 13 2023 2:48:05	root	0644
npm.1	5.534 KB	September 13 2023 2:48:05	root	0644
npx.1	6.697 KB	September 13 2023 2:48:05	root	0644

2017 © D7net \| D704T team