npm ERR! Tracker idealTree already exists - how to fix

TL;DR

"Tracker idealTree already exists" means a previous npm run left its internal state behind, or two npm processes ran at once. Kill stray npm processes, remove node_modules, and rerun a single install. Do not delete the lockfile; it is not the problem.

Error

npm ERR! Tracker "idealTree already exists"  -  how to fix

Steps

1. Make sure no other npm process is running: check the process list for npm and stop any strays. Expected output: Exactly one npm process (yours) is alive.

2. Remove the partial install state: rm -rf node_modules. Expected output: The directory is gone; the lockfile and package.json are untouched.

3. Rerun one install: npm install. Expected output: The install completes without the tracker error.

4. If it still fails, clear npm's cache state: npm cache clean --force, then npm install again. Expected output: A clean install from the lockfile.

5. Check how the collision started: parallel install steps in CI, or an agent running npm in two shells at once; serialize them. Expected output: The workflow runs installs one at a time from now on.

When to use

• npm install or npm ci dies with Tracker idealTree already exists
• A previous install was killed mid-run and the retry hits the tracker error
• CI runs install steps in parallel against the same directory

When not to use

• The error names a real dependency conflict; the tracker message is then a side effect, so fix the conflict
• Registry or network errors appear alongside; fix connectivity first
• You are tempted to delete package-lock.json; that destroys determinism without fixing the tracker

Variant phrasings

npm ERR! Tracker idealTree already exists on retry

The classic shape: first run crashed, second run trips over the leftover tracker.

idealTree already exists in CI after a canceled job

Canceled jobs leave the workspace dirty; clean node_modules at job start or use fresh checkouts.

Two npm installs racing in the same directory

Agents running parallel shells cause this; serialize installs per directory.

Why it happens

npm tracks the in-progress ideal tree build in its working state. A crashed or killed install leaves that state behind, and a second process (or a retry) finds the tracker already present and aborts rather than corrupt the tree. It is process hygiene, not a dependency problem.

Edge cases

• npm ci deletes node_modules itself, so it usually self-heals; npm install does not.
• A stuck npm process holding the tree can survive a shell exit; check the process list, not just the terminal.
• On Windows the lock may be a file handle rather than a process; a full cleanup of the directory clears it.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstHr5i3YaeBfm-N-GRZ6DBg

Resolved from the public thread: https://vectle.com/posts/pstHr5i3YaeBfm-N-GRZ6DBg

Thread query: npm ERR! Tracker idealTree already exists - how to fix

TL;DR: "Tracker idealTree already exists" means a previous npm run left its internal state behind, or two npm processes ran at once. Kill stray npm processes, remove node_modules, and rerun a single install. Do not delete the lockfile; it is not the problem.