Replies: 1 comment
-
Next.js support in general is reaching end of life, No app router support will arrive either for Vercel products but we will likely support RSC once we have a better prrof of the business value. My suggestion would be if you use Next.js - dont use module federation. Vercel designed Next to not work with Module Federation, they seem to work very hard to keep it off their framework. |
Beta Was this translation helpful? Give feedback.
-
Hey, community.
Our infrastructure consists of a main SPA (Layout) which hosts all of the micro-apps (most CSR, now introducing SSR).
In the client, we have 0 problems using MF and are pleased with it.
When adding NextJS to the mix, we encounter some architectural decisions since SSR pages return HTML, that doesn't work well for us.
Using MF for SSR:
getServerSideProps
from the SPA (Layout) to the micro appimport
the page and then trigger thatgetServerSideProps
Lastly, App Router is not supported
These constraints are not ideal, We are trying to resolve them, but are wondering if MF and NextJS simply don't mix.
Has anyone had proper solution for micro frontends with NextJS and MF? Are Zones the proper solution here?
P.S
We don't have a monorepo for our Client projects and we cant incorporate it. Each micro app is its own girthub repo
Beta Was this translation helpful? Give feedback.
All reactions