fix(sharing): copy buildMeta and buildInfo to ConsumeSharedModule #20054
+103
−0
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.
What kind of change does this PR introduce?
Bug fix
Did you add tests for your changes?
Yes
Summary
This PR fixes issue #16125 where
ConsumeSharedModuledoesn't properly inheritbuildMetaandbuildInfofrom its fallback module, causing incorrect ESM/CJS detection for.mjsfiles in Module Federation.Changes
finishModuleshook inConsumeSharedPluginto copybuildMetaandbuildInfofrom fallback modules toConsumeSharedModuleinstancesFlagDependencyExportsPlugin)DelegatedModulepattern for metadata inheritanceTest Coverage
test/configCases/sharing/consume-mjs-module/to verify ESM module consumption works correctlyImpact
This fix ensures Module Federation correctly handles ESM modules (particularly
.mjsfiles) by preserving theexportsTypeand other critical metadata through the consumption chain. This resolves issues with packages likeswr/infiniteand any other shared packages that use.mjsextensions.Related
buildMetaandbuildInfoonConsumeSharedPluginusing fallbacks module-federation/core#4063Does this PR introduce a breaking change?
No