Error Codes Wiki

npm Install Errors — Dependency Resolution, Peer Dependencies, and Lock File Conflicts

Warningweb development

Overview

Fix npm install errors including ERESOLVE peer dependency conflicts, corrupted node_modules, lock file mismatches, and permission errors.

Key Details

  • npm install downloads packages from the npm registry and resolves dependency trees
  • ERESOLVE errors occur when two packages require incompatible versions of the same dependency
  • package-lock.json ensures reproducible installs — mismatches cause unexpected behavior
  • node_modules can become corrupted from interrupted installs, disk full, or npm cache issues
  • npm 7+ is stricter about peer dependencies than npm 6 — many existing projects get new errors

Common Causes

  • Peer dependency conflict: package A needs react@17, package B needs react@18
  • Corrupted node_modules from a previous interrupted or failed install
  • package-lock.json out of sync with package.json — manual edits or merge conflicts
  • npm cache corrupted containing damaged package tarballs

Steps

  1. 1For peer dependency errors: 'npm install --legacy-peer-deps' to skip strict peer dep checking
  2. 2Clean install: delete node_modules and package-lock.json, then 'npm install'
  3. 3Clear npm cache: 'npm cache clean --force' then 'npm install'
  4. 4Check for lock file conflicts: 'npm ci' uses package-lock.json exactly — fails if it does not match package.json
  5. 5Audit for vulnerabilities: 'npm audit' to see security issues, 'npm audit fix' for automatic patches

Tags

npminstallpeer-dependencynode-modulespackage-manager

Related Items

More in Web Development

Frequently Asked Questions

npm install reads package.json and may update package-lock.json. npm ci reads only package-lock.json exactly — faster and reproducible for CI environments. npm ci fails if the lock file is out of sync.