Fix React 19 slot registration - #6
Merged
Merged
Conversation
kolengri
marked this pull request as ready for review
July 30, 2026 19:17
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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.
What changed\n\n- Replaced the -backed slot registry with a closure-backed registry.\n- Bumped the package version to 2.0.4.\n- Added a regression test that prevents reintroducing the unsupported approach.\n\n## Why\n\nReact 19 no longer applies to function components, so the previous implementation passed an empty slot list and produced empty .\n\n## Validation\n\n- Built successfully with the repository's frozen Yarn dependencies.\n- Verified the slot-prop flow directly against React 19.2.7.\n