A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.npmjs.com/cli/v7/commands/npm-ci below:

npm-ci | npm Docs

npm-ci

Install a project with a clean slate

Synopsis Description

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:

In short, the main differences between using npm install and npm ci are:

Example

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:

install:

- npm ci

cache:

directories:

- "$HOME/.npm"

Configuration audit

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.

ignore-scripts

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 start, npm stop, npm restart, 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.

script-shell

The shell to use for scripts run with the npm exec, npm run and npm init <pkg> commands.

See Also

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4