ꦫꦣꦺꦤ꧀ꦄꦤ꧀ꦠꦱꦺꦤ

PATH: usr / local / lib / node_modules / npm / docs / content / cli-commands

---
section: cli-commands 
title: npm-ci
description: Install a project with a clean slate
---

# npm-ci(1)

## Install a project with a clean slate

### Synopsis
```bash
npm ci
```

### Example

Make sure you have a package-lock and an up-to-date install:

```bash
$ cd ./my/npm/project
$ npm install
added 154 packages in 10s
$ ls | grep package-lock
```

Run `npm ci` in that project

```bash
$ npm ci
added 154 packages in 5s
```

Configure Travis to build using `npm ci` instead of `npm install`:

```bash
# .travis.yml
install:
- npm ci
# keep the npm cache around to speed up installs
cache:
  directories:
  - "$HOME/.npm"
```

### Description

This command is similar to [`npm install`](/cli-commands/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. It can be significantly faster than a regular npm
install by skipping certain user-oriented features. It is also more strict than
a regular install, which can help catch errors or inconsistencies caused by the
incrementally-installed local environments of most npm users.

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.

### See Also

* [npm install](/cli-commands/npm-install)
* [package-locks](/configuring-npm/package-locks)

[-] npm-build.md [edit]
[-] npm-bundle.md [edit]
[-] npm-prune.md [edit]
[-] npm-repo.md [edit]
[-] npm-owner.md [edit]
[-] npm-edit.md [edit]
[-] npm-audit.md [edit]
[-] npm-unpublish.md [edit]
[-] npm-bin.md [edit]
[-] npm-test.md [edit]
[-] npm-run-script.md [edit]
[-] npm-completion.md [edit]
[-] npm-adduser.md [edit]
[+] ..
[-] npm-deprecate.md [edit]
[-] npm-link.md [edit]
[-] npm-root.md [edit]
[-] npm-dist-tag.md [edit]
[-] npm-update.md [edit]
[-] npm-start.md [edit]
[-] npm-config.md [edit]
[-] npm-hook.md [edit]
[-] npm-token.md [edit]
[-] npm-pack.md [edit]
[-] npm-stars.md [edit]
[-] npm-publish.md [edit]
[-] npm-whoami.md [edit]
[-] npm-install-ci-test.md [edit]
[-] npm-prefix.md [edit]
[-] npm-shrinkwrap.md [edit]
[-] npm.md [edit]
[-] npm-install-test.md [edit]
[-] npm-version.md [edit]
[-] npm-team.md [edit]
[-] npm-fund.md [edit]
[-] npm-restart.md [edit]
[-] npm-star.md [edit]
[-] npm-ci.md [edit]
[-] npm-ls.md [edit]
[-] npm-explore.md [edit]
[-] npm-view.md [edit]
[-] npm-dedupe.md [edit]
[-] npm-cache.md [edit]
[-] npm-uninstall.md [edit]
[-] npm-ping.md [edit]
[-] npm-install.md [edit]
[-] npm-access.md [edit]
[-] npm-help-search.md [edit]
[-] npm-help.md [edit]
[-] npm-org.md [edit]
[-] npm-init.md [edit]
[-] npm-logout.md [edit]
[-] npm-doctor.md [edit]
[-] npm-stop.md [edit]
[-] npm-bugs.md [edit]
[-] npm-rebuild.md [edit]
[-] npm-docs.md [edit]
[-] npm-profile.md [edit]
[-] npm-outdated.md [edit]
[-] npm-search.md [edit]