npm ci vs npm install in CI: Which to Use
In CI you almost always want npm ci, not npm install - here is why.
They look similar but behave differently around the lockfile and reproducibility.
| npm install | npm ci | |
|---|---|---|
| Uses lockfile | May update it | Installs exactly from it |
| node_modules | Reuses/patches | Deletes and reinstalls clean |
| Reproducible | No | Yes |
| Fails on lockfile drift | No | Yes (by design) |
Use npm ci in CI
npm ci gives clean, reproducible installs and fails loudly if package.json and the lockfile disagree - which is exactly what you want in a pipeline. npm install is for local development where you intend to change dependencies.
The verdict
CI: always npm ci (with the lockfile committed). Local dependency changes: npm install.
Related guides
npm ci "can only install with an existing package-lock.json in sync"Fix "npm ci can only install with an existing package-lock.json … in sync with package.json" in CI - caused b…
npm vs Yarn vs pnpm in CI: Speed, Disk & Reliabilitynpm vs Yarn vs pnpm for CI: install speed, disk usage, lockfile behavior, and caching. Which package manager…
Nginx vs Caddy: Manual TLS or Automatic?Nginx vs Caddy: a high-performance server with manual config vs a modern server with automatic HTTPS. Config,…