Node.js ERR_MODULE_NOT_FOUND

What this error means

Error [ERR_MODULE_NOT_FOUND] means npm or Node.js cannot resolve the project files, package metadata, dependency graph, or module path required by the command. Check the project root, lockfile, and Node version first.

Why this happens

Node projects depend on a consistent relationship between package.json, lockfiles, installed modules, and runtime version.

For Node.js ERR_MODULE_NOT_FOUND, local success can be misleading if node_modules is stale or the lockfile was not regenerated.

Common causes

• Relative import is missing a file extension
• Package is not installed
• Path points to a CommonJS-only entry incorrectly
• Case-sensitive filesystem reveals a path mismatch

Quick fixes

1. Run the command from the folder containing package.json.
2. Check the exact import specifier, include required file extensions for relative ESM imports, and reinstall dependencies.
3. Check node --version and npm --version.
4. Use npm ci for a clean lockfile-based install when a lockfile exists.

Copy-paste commands

Check runtime versions

node --version
npm --version

Install dependencies

npm install

Clean CI-style install

npm ci

Clear npm cache

npm cache clean --force

Reset local install state

rm -rf node_modules package-lock.json
npm install

Platform-specific fixes

CI/CD

• Prefer npm ci in CI so the build fails when package.json and package-lock.json drift apart.

Real-world fixes

• If the error names a peer dependency, update the plugin and framework versions together.
• If the error names a missing file, check filename casing; CI often runs on a case-sensitive filesystem.
• Check the exact import specifier, include required file extensions for relative ESM imports, and reinstall dependencies.

Step-by-step troubleshooting

1. Find the first Error [ERR_MODULE_NOT_FOUND] occurrence in the npm output; later stack lines are often symptoms.
2. Confirm the command is running in the intended package directory.
3. Compare package.json and package-lock.json after dependency changes.
4. Remove stale node_modules only after checking whether the lockfile is committed.
5. Rerun the failing command with the same Node version used in CI or production.

How to prevent it

• Commit lockfile changes with dependency changes.
• Pin the project Node version in .nvmrc, .node-version, or CI configuration.
• Use CI to catch dependency drift before deploy.

Related errors

• Node.js cannot find module
• Cannot use import statement outside a module
• npm ERR! code ERESOLVE

FAQ

What should I check first?

Start with the exact Error [ERR_MODULE_NOT_FOUND] line and the command, request, or workflow step that produced it. In npm or Node.js, the first useful clue is usually near the first failure line, not the final stack trace.

Can I ignore this error?

No. Treat it as a failed npm or Node.js step. A temporary bypass may help diagnosis, but the underlying cause should be fixed before shipping or publishing changes.

Why does this work locally but fail elsewhere?

Local machines often have cached credentials, old dependencies, different runtime versions, or network settings that CI and production do not share. Reproduce from a clean shell or clean install when possible.

How do I know the fix worked?

Rerun the smallest command, request, or deployment step that produced Error [ERR_MODULE_NOT_FOUND]. The fix is working when that step completes without the same signature and produces the expected output.