How to fix npm ERR! code ERESOLVE npm ERR! Found: package@version npm ERR! Could not resolve dependency: npm ERR! package@version from the root project in npm | DevErrors

How to fix "npm ERR! code ERESOLVE npm ERR! Found: package@version npm ERR! Could not resolve dependency: npm ERR! package@version from the root project"

1Use --legacy-peer-deps flag (quick fix)

Revert to npm 6 peer dependency behavior:

bash

# For single install
npm install --legacy-peer-deps

# For specific package
npm install package-name --legacy-peer-deps

This ignores peer dependency conflicts and proceeds with installation.

2Make legacy-peer-deps permanent

Add to .npmrc for project-wide setting:

bash

# Create or edit .npmrc in project root
echo "legacy-peer-deps=true" >> .npmrc

Now all npm install commands will use legacy resolution.

3Use --force for aggressive resolution

Bypass all safety checks (use with caution):

bash

npm install --force

Warning: This may install incompatible versions that cause runtime errors.

4Clean reinstall to reset state

Sometimes conflicts arise from corrupted lockfile state:

bash

# Remove cached dependency state
rm -rf node_modules package-lock.json

# Reinstall fresh
npm install

# Or with legacy peer deps
npm install --legacy-peer-deps

5Identify and resolve specific conflicts

For a proper fix, identify the conflicting packages:

bash

# See outdated packages
npm outdated

# Check what versions are available
npm view package-name versions

# Update the conflicting package
npm install package-name@latest

Update packages to versions compatible with your framework version.

6Use overrides to force versions (npm 8.3+)

Force specific versions using package.json overrides:

json

{
  "overrides": {
    "react": "^18.2.0"
  }
}

This tells npm to use React 18 everywhere, regardless of peer dependency declarations.

7Consider switching to Yarn

Yarn often handles peer dependencies more gracefully:

bash

# Install Yarn
npm install -g yarn

# Remove npm artifacts
rm -rf node_modules package-lock.json

# Install with Yarn
yarn install

Yarn uses a different resolution algorithm that may avoid the conflict.

Advanced notes

Using --legacy-peer-deps or --force masks underlying compatibility issues. Packages installed may conflict at runtime, causing duplicate package instances, incorrect behavior, or hard-to-debug errors. For production applications, investigate and resolve the root cause.

Common scenarios requiring this fix:
- Upgrading React 17 → 18 with packages not yet supporting React 18
- Angular major version upgrades
- Using beta/release candidate versions of frameworks
- Older packages no longer maintained

For CI/CD, add legacy-peer-deps=true to .npmrc in the repository, or modify install commands. GitHub Actions example:

yaml

- run: npm ci --legacy-peer-deps

How to fix npm ERR! code ERESOLVE npm ERR! Found: package@version npm ERR! Could not resolve dependency: npm ERR! package@version from the root project in npm

What this error means

Typical symptoms

Common causes

How to fix "npm ERR! code ERESOLVE npm ERR! Found: package@version npm ERR! Could not resolve dependency: npm ERR! package@version from the root project"

Advanced notes

Related errors

Official resources & further reading