table of contents
- bullseye 7.5.2+ds-2
- bullseye-backports 8.5.5~ds1-1~bpo11+1
- testing 9.1.3~ds1-1
- unstable 9.2.0~ds1-1
npm-ci - Install a project with a clean slate
This command is similar to npm install /cli-commands/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:
- There is a package-lock.json or npm-shrinkwrap.json file.
- The node_modules folder is missing or empty.
In short, the main differences between using npm install and npm ci are:
- The project must have an existing package-lock.json or npm-shrinkwrap.json.
- If dependencies in the package lock do not match those in 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.
- If a node_modules is already present, it will be automatically removed before npm ci begins its install.
- It will never write to 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-lock
Run npm ci in that project
$ npm ci added 154 packages in 5s
Configure 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:
- npm help install
- npm help package-lock.json