This is cool! Looking forward to pairing this with the "universal-module-federation-plugin" for loading the UMD Dependencies of my MF dependencies from CDNs too!
Great! You're mentioning hosting the package yourself. Do you mean relying on NPM and self-hosting something akin to unkpg or a completely self-hosted solution? Do you have any concrete examples? Thanks :)
When I say self hosting I mean for large companies that already have their own private package repositories (e.g. artifactory), they could then self host and unpkg server, proxy it through a CDN (Akamai, Cloudflare, etc.) and then use this mechanism themselves. They could then tweak the caching parameters on modules to whatever suited their SLAs.
Oooh. This is good stuff and solves a lot of issues. This feels like it introduces some local testing complexity, but is worth the trade-off. Really curious how you might refresh cache at edge here to capture federated component updates
@jherr this is excellent and better than hosting these MFEs yourself. In question though is what about dependent css files in these modules. Will those be handled seamlessly as well. I guess it will
Publishing to NPM can have dual factor auth. So even that is pretty good to start. But you can host a lot of this infrastructure yourself (as a business or a company) and then manage that auth yourself.
www.npmjs.com/package/live-plugin-manager .. will it be possible to directly use npm repos and dynamically load MFEs from npm and use it with module federation. The plugin manager to live download the npm modules and somehow make it work with module federation
@@jherr will give it a try soon. Also if this works it will be great if we can use something like bit.dev to publish and then consume as MFEs dynamically with module federation
The original code github.com/jacob-ebey/versioned-federated-module and github.com/jacob-ebey/consume-versioned-federated-module would be a decent starting point to build up an SSR version.
Publishing to npm is as easy as `npm login` and then `npm publish` in the directory with your package. Or `yarn login` and `yarn publish` if you prefer.
Seems like a good pattern! Good work Jacob, and thanks for making it digestible
This is awesome, Jack! Also, enjoyed the funny clips and that ice-covered tree in your outro! 😮
The ice looked a lot prettier than it turned out to be. It did a number on my neighborhood. Huge number of trees down. As well as some houses damaged.
@@jherr yikes! Stay safe out there.
This is super mind-blowing, Thank you Jack
This is cool! Looking forward to pairing this with the "universal-module-federation-plugin" for loading the UMD Dependencies of my MF dependencies from CDNs too!
another great video, jack!
You're doing a great job. Thanks for the video!
Jack, you made the best videos about microfronts, thank you a lot 😊
Which movie is it the funny clips? I want to watch 😂
Hi Jack. Great video. By the way, is there any alternative solution for self-hosting just like the feature unpkg offered?
Great! You're mentioning hosting the package yourself. Do you mean relying on NPM and self-hosting something akin to unkpg or a completely self-hosted solution? Do you have any concrete examples? Thanks :)
When I say self hosting I mean for large companies that already have their own private package repositories (e.g. artifactory), they could then self host and unpkg server, proxy it through a CDN (Akamai, Cloudflare, etc.) and then use this mechanism themselves. They could then tweak the caching parameters on modules to whatever suited their SLAs.
Oooh. This is good stuff and solves a lot of issues.
This feels like it introduces some local testing complexity, but is worth the trade-off.
Really curious how you might refresh cache at edge here to capture federated component updates
@jherr this is excellent and better than hosting these MFEs yourself. In question though is what about dependent css files in these modules. Will those be handled seamlessly as well. I guess it will
Also with unpkg will there be any additional security measures we need to take
Publishing to NPM can have dual factor auth. So even that is pretty good to start. But you can host a lot of this infrastructure yourself (as a business or a company) and then manage that auth yourself.
www.npmjs.com/package/live-plugin-manager .. will it be possible to directly use npm repos and dynamically load MFEs from npm and use it with module federation. The plugin manager to live download the npm modules and somehow make it work with module federation
@@tarunsukhu2614 Fascinating. I'd love to see someone try to do a fusion with this plugin-manager and federated modules!
@@jherr will give it a try soon. Also if this works it will be great if we can use something like bit.dev to publish and then consume as MFEs dynamically with module federation
It is support server side rendering? Thanks for sharing
The original code github.com/jacob-ebey/versioned-federated-module and github.com/jacob-ebey/consume-versioned-federated-module would be a decent starting point to build up an SSR version.
🎅 and 🤯, at the same time. Jack did you made a video on how to publish to npm? is it easy?
Publishing to npm is as easy as `npm login` and then `npm publish` in the directory with your package. Or `yarn login` and `yarn publish` if you prefer.
It is not working on app router. Do you have any fix for it?
Nope. And I probably won't. NextJS is working on their own version of RSC federation. It'll probably be Next only.
hi! tell me plz what about different versions react on host and remote apps? it is impossible ?
This is epic!