Replies: 1 comment
-
we support this with zephyr cloud already, it support tags, semver, pinning etc. https://zephyr-cloud.io/ To do this on your own, you cannot have two "scope" on the page at once. if its window.app1, you cant add another window.app1 without overwriting it. If you put it into esm mode, then it can use import() which does not rely on globals like script does - thus allowing you to avoid the collision in scope. Typically to support multiple version of the remote on the page - you would need to make the "name" unique, like app1_v123, app2_v123 - but then you need to know what its scope is to consume it. You may be able to use json remote entry with the new runtime, which the json remote will have the scope name inside it already and thus could overcome the issue in vanilla remotes. https://module-federation.io/guide/basic/runtime.html |
Beta Was this translation helpful? Give feedback.
-
We want to implement a feature on our platform that allows teams to "pin" specific remote versions while enabling other teams to continue using the latest version of the same remote. This means that a single "scope" could have multiple instances. Is this feasible?
Code example:
I really appreciate any help you can provide.
Beta Was this translation helpful? Give feedback.
All reactions