Issue while trying to make module fedration work with next js about module-federation-examples HOT 8 CLOSED

I need to write a plugin for next js. Next uses a single runtime chunk which moves all the Federation code into the main runtime. In reality I need a special runtime created that’s not bound to the normal webpack runtime

from module-federation-examples.

Thanks.. May be I will wait for the plugin then.

from module-federation-examples.

You can make a shim for next.js. It’s what I use in production

from module-federation-examples.

@ScriptedAlchemy Do you have any documentation / resources on how to do this?

from module-federation-examples.

https://gist.github.com/ScriptedAlchemy/d386a094832dbd9a04324862d26570e9

window.abtests needs to be replaced with window.[remote]

from module-federation-examples.

@ScriptedAlchemy Would you happen to have an example of federating pages between two separate next applications? I could see this being very useful where you would have a main shell application with some kind of discovery service that is able to locate different remotes and include their pages. Similar to the way zones work with next js, but truly a single-page experience.

I have a discovery service working for components / routes outside of the next js framework.

from module-federation-examples.

all examples are proprietary and in-house to solve legacy WP4 and next js. Nothing demoed in repos mostly because I don’t use WP4 anymore lol. you pretty much paste the gist into a js file and add it as a new entrypoint then change the importAll context around based on what you want to expose to other remotes. You will need to load more than one file tho. 1 the runtime chunk next makes, 2 the remote entry containing the shim along with it dynamic importing all the pages via require.context, ugly but works

from module-federation-examples.

Closing these as its a separate series of problems that will arise. There is a next.js example available now

from module-federation-examples.