Node.js MODULE_NOT_FOUND local versus production drift response

When this happens

Use this when it works locally but fails only on the deployed server. Do not stop at the screen message; validate runtime version, environment variables, file paths, locale, timezone, and permissions first.

Symptom checklist

• MODULE_NOT_FOUND appears repeatedly in the Node.js UI or logs.
• process env, npm tree, memory, port, module type differs between successful and failed requests.
• The issue appears only after separating Node runtime error from package dependency issue.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• MODULE_NOT_FOUND specifically changes the investigation surface for Node.js: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• The deployed runtime does not contain the package, class, image, or module that local development used.
• Lockfiles or dependency caches select a different version than expected.
• ESM/CJS, classpath, Composer autoload, or Python virtualenv boundaries are mixed.
• A registry or image pull permission fails before application code starts.
• Build and runtime environments use different package managers or versions.
• For the local versus production drift case, the first useful clue is runtime version, environment variables, file paths, locale, timezone, and permissions.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare process env, npm tree, memory, port, module type for success and failure in the same window.
3. Test the hypothesis: dependency or import failure caused by missing package, incompatible module system, stale lockfile, classpath, image registry, or isolated runtime.
4. Classify this as local versus production drift: runtime version, environment variables, file paths, locale, timezone, and permissions.
5. Capture current values before changing configuration.

First evidence

Treat MODULE_NOT_FOUND as a local versus production drift case. First collect evidence for runtime version, environment variables, file paths, locale, timezone, and permissions.

Output examples

Normal output

Runtime, env values, paths, and permissions match the documented production baseline.

Failing output

Production uses a different version, env var, path, locale, timezone, or user.

Output-to-action branches

• It works locally but fails only on the deployed server.
  Print effective runtime state from the failing process, not only from the login shell.
• The working and failing outputs differ.
  Act on the differing layer first: For MODULE_NOT_FOUND, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not trust CLI output if the web worker, service, or container runs as another user.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "MODULE_NOT_FOUND" ./logs

node --trace-warnings server.js

npm ls

lsof -i :3000

grep -R "MODULE_NOT_FOUND" src logs

npm ls || true

python -m pip freeze || true

composer diagnose || true

mvn -q dependency:tree || true

printenv | sort && pwd && id

Fix order

1. Record the full MODULE_NOT_FOUND message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for dependency or import failure caused by missing package, incompatible module system, stale lockfile, classpath, image registry, or isolated runtime.
3. Compare the failing case with a successful case before editing settings.
4. If this is the local versus production drift branch, Print effective runtime state from the failing process, not only from the login shell.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For MODULE_NOT_FOUND, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Reproduce from a clean install rather than a warmed local cache.
• Pin dependency versions and regenerate the lockfile deliberately.
• Align module system, classpath, autoload, or virtualenv configuration.
• Authenticate registry/image pulls before restarting workloads.
• Add a build-time check for the missing module or class.
• For the local versus production drift branch, Print effective runtime state from the failing process, not only from the login shell.

Evidence links

• Node.js errors official
• Node.js diagnostics official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Node.js MODULE_NOT_FOUND.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change Node runtime error from package dependency issue results.
• Do not trust only the Node.js UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for process env, npm tree, memory, port, module type.
• Add npm dedupe, ESM/CJS alignment, heap tuning, port cleanup to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• Node.js ECONNRESET first triage response
• Node.js EADDRINUSE first triage response
• Node.js MODULE_NOT_FOUND first triage response
• Node.js ERR_REQUIRE_ESM first triage response
• Node.js heap out of memory first triage response
• Node.js npm peer dependency first triage response
• Node.js fetch failed first triage response
• Node.js timeout first triage response