fix: isolate module federation shared scope per app#2770
Merged
Conversation
Load each external app through its own ModuleFederation instance instead of a single shared host instance. All remotes loaded through one instance share the same shareScopeMap by reference, so a faulty app that corrupts that scope during init breaks every other app too. Per-instance isolation contains such failures to the offending app while preserving parallel loading and singleton identity of shared modules. (cherry picked from commit 3926dbb)
(cherry picked from commit 89aebc8)
AlexAndBear
approved these changes
Jun 30, 2026
kulmann
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
maintostable-7.1:Questions ?
Please refer to the Backport tool documentation