- npm 是什么?
- 如何安装 npm 并管理 npm 版本
- How to Prevent Permissions Errors
- 如何安装本地包
- Working with package.json
- 如何更新本地安装的包
- 如何卸载本地安装的包
- 如何安装全局包
- 如何更新全局安装的包
- 如何卸载全局安装的包
- 如何创建 Node.js 模块
- How to Publish & Update a Package
- 如何使用语义化版本
- How to Work with Scoped Packages
- How to Label Packages with Dist-tags
- How to Use Two-Factor Authentication
- How to Work with Security Tokens
- How to Change Profile Settings from the CLI
- Understanding Packages and Modules
- npm-access
- npm-adduser
- npm-audit
- npm-bin
- npm-bugs
- npm-build
- npm-bundle
- npm-cache
- npm-ci
- npm-completion
- npm-config
- npm-dedupe
- npm-deprecate
- npm-dist-tag
- npm-docs
- npm-doctor
- npm-edit
- npm-explore
- npm-help
- npm-help-search
- npm-hook
- npm-init
- npm-install
- npm install-ci-test -- Install a project with a clean slate and run tests
- npm install-test -- 安装依赖包并运行测试
- npm-link
- npm-logout
- npm-ls
- npm
- npm-org
- npm-outdated
- npm-owner
- npm-pack
- npm-ping
- npm-prefix
- npm-profile
- npm-prune
- npm-publish
- npm-rebuild
- npm-repo
- npm-restart
- npm-root
- npm-run-script
- npm-search
- npm-shrinkwrap
- npm-star
- npm-stars
- npm-start
- npm-stop
- npm-team
- npm-test
- npm-token
- npm-uninstall
- npm-unpublish
- npm-update
- npm-version
- npm-view
- npm-whoami
- npm-coding-style
- npm-config
- npm-developers
- npm-disputes
- npm-orgs
- npm-registry
- npm-removal
- npm-scope
- npm-scripts
- semver
- npm-folders
- npmrc
- package-lock.json
- npm-package-locks
- package.json
- npm-shrinkwrap.json
- 尝试 node 的最新稳定版本
- Try the latest stable version of npm
- 如果 npm 损坏了
- Try clearing the npm cache
- Common Errors
npm-update
Update a package
概要
npm update [-g] [<pkg>...]
aliases: up, upgrade
详情
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
.
实例
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:
{
"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:
"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:
"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:
"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
:
"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 latest
.
NOTE: If a package has been upgraded to a version newer than latest
, it will be downgraded.
请参阅
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论