Fixed ReactSharedInternals export in UMD bundle #22117
Merged
+2
−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.
Resolves #22113
Prior to this PR, the
react
UMD bundle contained twoReactSharedInternals
objects. The firstReactSharedInternals
object came from here:react/packages/react/src/ReactSharedInternals.js
Lines 15 to 26 in bd25570
The second
ReactSharedInternals
object (ReactSharedInternals$1
in the bundle) came from here:react/packages/react/src/forks/ReactSharedInternals.umd.js
Lines 15 to 28 in bd25570
The second one is the one that ended up being shared via
__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED
. It had aScheduler
key but not aReactCurrentActQueue
key. The fix was to make sure both keys got added to the UMD override.Testing
Re-built the bundle:
Then inspected the output at:
Also dropped both into a small repro app: