-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module federation remote loader #1041
Comments
@ScriptedAlchemy thanks for the heads-up! I've grepped the webpack and module-federation-examples repos for any examples but didn't find any occurrences or examples. Can you point me to something? |
The https://github.com/module-federation/module-federation-examples/tree/master/advanced-api/automatic-vendor-sharing are quite the use case which we're tackling here. |
This is on npm as module-federation/utilities Might need some adjustments to the file since it's got a loop for runtime remotes on there. (Send a pr if you want me to maintain script injection) https://github.com/module-federation/nextjs-mf/blob/main/packages/utilities/src/utils/common.ts |
Ive published it to npm, so you can use it via module-federation/utilities. |
Just a heads up - I still have this on my radar, but I'm short on time diving into that right now. Have to prepare next week's Plone conference training and my talk about module federation in Plone (resp. Patternslib) where I will revisit this proposal for sure :) |
Hi, I've recently developed a better solution to loading remote scripts.
Consider require.loadChunk or webpack_require.l(url,event,id)
This will leverage webpacks own chunk loader for loading remote containers the same way import(remote/module) does within webpack module factories.
It's by far the most reliable solution.
The text was updated successfully, but these errors were encountered: