Replies: 4 comments 3 replies
-
Same issue, did you find a fix for your problem? |
Beta Was this translation helpful? Give feedback.
-
@sahul-e hey, good news i have solved the issue try downgrading to this next version
and also in your build script and start-dev or dev you need to add this key to let know next js to use the local webpack instead of the its own webpack version
|
Beta Was this translation helpful? Give feedback.
-
@GeorgeVictor8 |
Beta Was this translation helpful? Give feedback.
-
@sahul-e have you tried using Next15 + Rspack to see if the error is the same? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team 👋,
I'm trying to use @module-federation/nextjs-mf with Next.js v15.3.2, and I'm running into an issue when starting the dev server:
It looks like the plugin is relying on a private/internal Next.js file that may have been removed or moved in Next 15.
❓ Request for Help
I’m not in a position to downgrade Next.js, so I'm hoping to continue using nextjs-mf with the latest Next version.
Could someone from the team guide me on:
I’d be happy to test or contribute a fix if there’s a direction to go in. 🙏
📦 Versions
✅ Repro Steps
@module-federation/nextjs-mf
NextFederationPlugin
tonext.config.js
(const NextFederationPlugin = require('@module-federation/nextjs-mf') )
npm run dev
🔎 Root Cause
The plugin relies on the internal file
next/dist/compiled/lib/ModuleNotFoundError
which was removed in Next.js 15.Beta Was this translation helpful? Give feedback.
All reactions