Paste your npm error. Get the actual fix.

Stop manually tracing an ERESOLVE unable to resolve dependency tree error through a wall of red text. Paste the full error and get the two conflicting packages, the versions they each want, and a copy-paste fix.

Zeeshan Tofiq

Full Stack Developer

Share

How ERESOLVE Explainer works

1. 1

   Paste the full npm ERESOLVE error

   Copy everything npm printed, starting from ERESOLVE unable to resolve dependency tree through the final Fix the upstream dependency conflict line. The more complete the paste, the more the parser can extract.

2. 2

   The error is parsed entirely in your browser

   Nothing is sent to a server. The parser strips the npm error / npm ERR! line prefixes, then looks for the While resolving, Found, and Could not resolve dependency sections that npm always prints in this order.

3. 3

   The two conflicting packages are identified

   The parser extracts the package already resolved in your tree (and where it came from) and the peer dependency requirement that conflicts with it (and which package declared that requirement).

4. 4

   A plain-English summary is generated

   Instead of raw npm output, you get a sentence explaining which package wants which version, and whether it's a direct dependency in your package.json or pulled in transitively by something else.

5. 5

   Copy-paste overrides and resolutions blocks appear

   Both an npm overrides block and a Yarn resolutions block are generated from the actual package names and versions in your error, ready to drop into package.json.

6. 6

   Fix the conflict without --force or --legacy-peer-deps

   Apply the generated block, delete node_modules and your lockfile if needed, and reinstall. The conflict is resolved instead of silently suppressed.

What each part of the result means

Every ERESOLVE conflict comes down to two packages disagreeing about a third package's version.

Found: typescript@7.0.0-rc
node_modules/typescript
  typescript@"^7.0.0-rc" from the root project

peer typescript@"<6.1.0" from typescript-eslint@8.15.0

{
  "overrides": {
    "typescript-eslint": {
      "typescript": "$typescript"
    }
  }
}

# Make sure your paste includes both:
Found: <package>@<version>
peer <package>@"<range>" from <parent>@<version>

npm ERESOLVE error format reference

Every npm 7+ ERESOLVE error follows the same structure, just with different package names.

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: my-app@1.0.0        // your project
npm error Found: typescript@7.0.0-rc           // what's already resolved
npm error node_modules/typescript
npm error   typescript@"^7.0.0-rc" from the root project   // declared directly
npm error
npm error Could not resolve dependency:
npm error peer typescript@"<6.1.0" from typescript-eslint@8.15.0  // the conflict
npm error node_modules/typescript-eslint
npm error   typescript-eslint@"^8.15.0" from the root project    // also direct
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

Older npm versions (3 through 6) print a shorter npm WARN message instead of failing outright, since peer dependency conflicts were warnings, not hard errors, before npm 7.

When to use ERESOLVE Explainer