Replies: 2 comments
|
As long as you only use the build time version of module federation it should work. 1.0 does not work with the runtime capabilities of new mf versions. In addition I would suggest disabling the manifest.json usage of 2.0 to be better aligned with the outdated workflow of 1.0. https://module-federation.io/configure/manifest.html#manifest Let me know if it worked! |
0 replies
|
It should still work, as long as you dont try to use new features. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello, I have a question regarding module federation compatibility. If provider A uses moduleFederation 2.0 to build modules, and consumer B is still using module federation 1.0, can B seamlessly use A's modules? Thank you for your assistance!
All reactions