n8n - 💡(How to fix) Fix 2.15.1 → 2.16.1: Failed to load module "breaking-changes" [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28572Fetched 2026-04-17 08:54:56
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
1
Timeline (top)
commented ×2subscribed ×2labeled ×1mentioned ×1

Error Message

n8n@LeebN8N:~$ npx n8n Error: Failed to load module "breaking-changes": Cannot find module '/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/dist/modules/breaking-changes.ee/breaking-changes.module' Require stack:

  • /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/dist/modules/module-registry.js
  • /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/dist/index.js
  • /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/dist/config/index.js
  • /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/bin/n8n. Please review the module's entrypoint file name and the module's directory name. at ModuleRegistry.loadModules (/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/src/modules/module-registry.ts:100:12) at CommandRegistry.execute (/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/src/command-registry.ts:46:3) at /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/bin/n8n:63:2

Code Example

n8n@LeebN8N:~$ npx n8n
Error: Failed to load module "breaking-changes": Cannot find module '/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/dist/modules/breaking-changes.ee/breaking-changes.module'
Require stack:
- /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/dist/modules/module-registry.js
- /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/dist/index.js
- /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/dist/config/index.js
- /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/bin/n8n. Please review the module's entrypoint file name and the module's directory name.
    at ModuleRegistry.loadModules (/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/src/modules/module-registry.ts:100:12)
    at CommandRegistry.execute (/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/src/command-registry.ts:46:3)
    at /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/bin/n8n:63:2
RAW_BUFFERClick to expand / collapse

Bug Description

After running npx n8n and confirming to download version 2.16.1 this happens:

n8n@LeebN8N:~$ npx n8n
Error: Failed to load module "breaking-changes": Cannot find module '/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/dist/modules/breaking-changes.ee/breaking-changes.module'
Require stack:
- /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/dist/modules/module-registry.js
- /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/dist/index.js
- /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/dist/config/index.js
- /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/bin/n8n. Please review the module's entrypoint file name and the module's directory name.
    at ModuleRegistry.loadModules (/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/@n8n/backend-common/src/modules/module-registry.ts:100:12)
    at CommandRegistry.execute (/home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/src/command-registry.ts:46:3)
    at /home/n8n/.npm/_npx/a8a7eec953f1f314/node_modules/n8n/bin/n8n:63:2

To Reproduce

  1. npx [email protected]
  2. CRTL + C after n8n is ready
  3. npx n8n
  4. Proceed with update to version 2.16.1

Expected behavior

The upgrade should work the first time

Debug Info

n/a

Operating System

Debian 13 ”Trixie”

n8n Version

2.15.1

Node.js Version

24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

The issue can likely be resolved by clearing the npm cache and reinstalling the n8n package.

Guidance

  • Try clearing the npm cache using npm cache clean --force to remove any corrupted or outdated packages.
  • Reinstall the n8n package using npx [email protected] to ensure a clean installation.
  • Verify that the breaking-changes module is correctly loaded after reinstalling the package.
  • If the issue persists, try removing the entire .npm/_npx directory to start with a clean slate.

Example

No code snippet is necessary for this issue, as it appears to be related to package installation and caching.

Notes

The issue may be specific to the Debian 13 "Trixie" operating system or the Node.js version 24.14.1, but further investigation is needed to confirm this.

Recommendation

Apply workaround: Clear the npm cache and reinstall the n8n package, as this is a non-invasive and straightforward solution that may resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The upgrade should work the first time

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING