fix(module-federation): use 'hoisted' runtime for node to prevent issues with eager sharing #29104
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.
Current Behavior
SSR with Module Federation frequently encounters issues related to the eager resolution of shared packages.
This has resulted in numerous erroneous behaviours including but not limited to:
Expected Behavior
Using the
'hoisted'
runtime provided by MF 2.0, we can ensure that SSR for Module Federation runs in an async environment, removing the issues surrounding eager consumption and resolution of shared modules.In testing, this has fixed the issues outlined above
Related Issue(s)
Fixes #27000
Fixes #27964