I read it well, but the link between Next.js and Module Federation you're talking about has so much to lose compared to what you get. You need to import the components of the remoteApp as a dynamic import (ssr false). The reason is that if you do static or dynamic import (ssr true), you will get a hydration error. You will use the entry.js of the remoteApp that was built at the time of the build on the server, but what if the remoteApp screen was modified in the meantime? You will see a 100% hydration error. Dynamic import (ssr false) fails to render your components on the server, which eventually tarnishes one of Next.js' main objectives of optimizing SEO. It can also cause pages to appear slightly late, page layout to appear slightly broken, blinking, or shaking. Wouldn't it be better to split into monorepo and float servers in multiple locations and redirect different services?? Every time a remote app page is added, you have to keep adding and sync pages with shell, so what's the point of doing this hassle at the expense of the aforementioned?