npm ciThis command is similar to npm install, except
it's meant to be used in automated environments such as test platforms,
continuous integration, and deployment -- or any situation where you want
to make sure you're doing a clean install of your dependencies.
npm ci will be significantly faster when:
package-lock.json or npm-shrinkwrap.json file.node_modules folder is missing or empty.In short, the main differences between using npm install and npm ci are:
package-lock.json or
npm-shrinkwrap.json.package.json,
npm ci will exit with an error, instead of updating the package lock.npm ci can only install entire projects at a time: individual
dependencies cannot be added with this command.node_modules is already present, it will be automatically removed
before npm ci begins its install.package.json or any of the package-locks:
installs are essentially frozen.Make sure you have a package-lock and an up-to-date install:
$ cd ./my/npm/project
$ npm install
added 154 packages in 10s
$ ls | grep package-lockRun npm ci in that project
$ npm ci
added 154 packages in 5sConfigure Travis to build using npm ci instead of npm install:
# .travis.yml
install:
- npm ci
# keep the npm cache around to speed up installs
cache:
directories:
- "$HOME/.npm"👀 Found a typo? Let us know!
The current stable version of npm is here. To upgrade, run: npm install npm@latest -g
To report bugs or submit feature requests for the docs, or for any issues regarding the npm command line tool, please post on the npm/cli GitHub project.