npm-ciInstall a project with a clean slate
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:
- There is a
node_modulesfolder is missing or empty.
In short, the main differences between using
npm install and
npm ci are:
- The project must have an existing
- If dependencies in the package lock do not match those in
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.
- If a
node_modulesis already present, it will be automatically removed before
npm cibegins its install.
- It will never write to
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 installadded 154 packages in 10s$ ls | grep package-lock
npm ci in that project
$ npm ciadded 154 packages in 5s
Configure Travis to build using
npm ci instead of
# .travis.ymlinstall:- npm ci# keep the npm cache around to speed up installscache:directories:- "$HOME/.npm"
- Default: true
- Type: Boolean
When "true" submit audit reports alongside the current npm command to the
default registry and all registries configured for scopes. See the
npm audit for details on what is
- Default: false
- Type: Boolean
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
will still run their intended script if
ignore-scripts is set, but they
will not run any pre- or post-scripts.
- Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows
- Type: null or String
The shell to use for scripts run with the
npm run and
init <pkg> commands.