fix: fix up React federation order edge case#820
Merged
Merged
Conversation
4 tasks
gioboa
commented
Jun 15, 2026
gioboa
left a comment
Collaborator
Author
There was a problem hiding this comment.
Tests With Different Frameworks
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
1 participant
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.
Fixes a React federation plugin-order edge case where react could end up in both optimizeDeps.include and exclude, causing esbuild to externalize an entry point and crash. Federation now skips optimizer entry-point proxying, and normalizeOptimizeDeps removes include/exclude conflicts after all plugins mutate config.