Still fails after clean install?

Upgrade npm/node to supported versions and delete package-lock.json only if you can regenerate it.

Check workspace tools (lerna/nx) for parallel installs conflicting with npm.

Ensure runners don’t overlap workspaces and cache keys aren’t corrupt.

Error fix

How to fix “npm ERR! tracker idealtree already exists”

npm’s internal dependency tree build hit a corrupted or locked state—often cache or concurrent installs.

Start here first. Step 1 fixes most cases—then work down the list.

Stop other npm/yarn/pnpm processes using the same project.
Remove node_modules and lockfile conflicts, then npm cache verify / npm cache clean --force if needed.
Reinstall with a single npm ci or npm install run.

Why this works

These steps work because it clears stale cached state that can cause the same request to fail repeatedly.

npm tracks an in-memory ideal tree while resolving dependencies; this error signals inconsistent internal state during that process.

Concurrent npm processes
Two installs writing node_modules or the npm cache at once.
Corrupted cache
Partial downloads or interrupted installs leaving bad metadata.

Reset local state
1. Stop other npm/yarn/pnpm processes using the same project.
2. Remove node_modules and lockfile conflicts, then npm cache verify / npm cache clean --force if needed.
3. Reinstall with a single npm ci or npm install run.

Still fails after clean install?: Upgrade npm/node to supported versions and delete package-lock.json only if you can regenerate it.
Monorepo only?: Check workspace tools (lerna/nx) for parallel installs conflicting with npm.
CI only?: Ensure runners don’t overlap workspaces and cache keys aren’t corrupt.

If reproducible on a minimal package.json, file an issue with npm with --verbose logs.

Still stuck? Try these related fixes next.

Tweak the message and run again—we'll match an existing fix or generate a new page.

Original error message

npm ERR! tracker idealtree already exists