Module federation in nextjs with App directory

[PowellT]

It is clear that @module-federation/nextjs-mf wont support App directory in nextjs.
How have others gotten around this? Where you able to do this with webpack directly?
I am gonna can nextjs if I cant get this to work.

[ScriptedAlchemy]

Cheapest solution is use something else other than next.
You could try using the runtime package directly, forgoing the build plugin and put init() in the rsc as well as in the use client.

ModernJS will release RSC + Federation support in 2025.

Warning: Support for next is ending

#3153

[YanPes]

I can recommend using Modern.js as a replacement for Next.js.
It is a very capable framework with the unique benefit of being a first class citizen of Module Federation (MF). If you build your architecture around MF I would suggest using the ecosystem to it's fullest by leveraging supported tech where possible.

[fcano-ut]

I used to have a Next.js host app which shared all dependencies as "eager". It also exclusively loaded micro-frontends in the client (no SSR).

I could replace it with this setup:

• From pages to app router
• Stop using next-mf plugin
• Start using Module Federation runtime to register app + remotes + share deps

Functionally it's similar to what I had before. I just had minor issues where dependency sharing was not quite working for some specific dependencies if the micro-frontend was not using the enhanced plugin, but it's something that got fixed by updating the micro-frontends. (Also it was not a blocker because functionally it was still working, even if not that optimal)

[zackarychapple]

This should get easier with the updates and PRs going into webpack and Rspack and the increased help and guidance from Vercel and the NextJS team to support Module Federation. Apologies for this taking so long, but looks like we have a path forward now.