Browse by category

npm & Node errors

Install failures, lockfile issues, and common Node runtime messages.

• Cannot find module (Node / bundler)The runtime or bundler could not resolve an import—missing package, wrong path, or build config.
• Missing package.json fileNode/npm expected a package.json in this folder—the project root is wrong or the file was never created.
• npm ERR! tracker idealtree already existsnpm’s internal dependency tree build hit a corrupted or locked state—often cache or concurrent installs.
• npm peer dependency conflict (ERESOLVE)npm could not satisfy peer ranges—often a major version bump or duplicate packages.
• pnpm unexpected storeThe content-addressable store path does not match the project—often after switching machines.
• Yarn Berry / PnP resolutionPlug’n’Play could not resolve a package—cache, constraints, or missing deps.