This 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:
node_modulesfolder is missing or empty.
In short, the main differences between using
npm install and
npm ci are:
npm ciwill exit with an error, instead of updating the package lock.
npm cican only install entire projects at a time: individual dependencies cannot be added with this command.
node_modulesis already present, it will be automatically removed before
npm cibegins its install.
package.jsonor 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
npm ci in that project
$ npm ci added 154 packages in 5s
Configure Travis to build using
npm ci instead of
# .travis.yml install: - npm ci # keep the npm cache around to speed up installs cache: directories: - "$HOME/.npm"
When "true" submit audit reports alongside the current npm command to the default registry and all registries configured for scopes. See the documentation for
npm audit for details on what is submitted.
If true, npm does not run scripts specified in package.json files.
Note that commands explicitly intended to run a particular script, such as
npm test, and
npm run-script will still run their intended script if
ignore-scripts is set, but they will not run any pre- or post-scripts.
The shell to use for scripts run with the
npm run and
init <pkg> commands.
© npm, Inc. and Contributors
Licensed under the npm License.
npm is a trademark of npm, Inc.