package.json中规定的npm install和npm update包装版本处理之间的差异:
{
"name": "my-project",
"version": "1.0", // install update
"dependencies": { // ------------------
"already-installed-versionless-module": "*", // ignores "1.0" -> "1.1"
"already-installed-semver-module": "^1.4.3" // ignores "1.4.3" -> "1.5.2"
"already-installed-versioned-module": "3.4.1" // ignores ignores
"not-yet-installed-versionless-module": "*", // installs installs
"not-yet-installed-semver-module": "^4.2.1" // installs installs
"not-yet-installed-versioned-module": "2.7.8" // installs installs
}
}
Summary:唯一的区别是an already installed module with fuzzy versioning...
npm install
忽略npm update
次Additionally:install
和update
默认情况下处理devdependency的方式不同
--production
标志,否则npm install
将显示install/update个DevDependence--dev
标志,否则npm update
将显示ignore个DevDependenceWhy use 100 at all?
因为npm install
除了处理package.json
中的依赖项外,还可以做更多的事情.
npm install -g <name>
将它们设置为global(这将它们放入shell的PATH
中)--force
强制重新安装