Handle props on Fragment error due to Symbol(react.lazy)#3873
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
0846d5b to
b0af729
Compare
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
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.
This PR fixes an error where you get an error that props were forwarded to a Fragment. This is because we forward props to the children in case of a Fragment. We only do this to valid elements, but in some scenarios, it could be that we receive a
Symbol(react.lazy).Sometimes we also get a
Symbol(react.transitional.element)but that doesn't seem like an issue.With this PR, we resolve the payload of fulfilled
react.lazyelements.Fixes: tailwindlabs/tailwind-plus-issues#1814
Test plan
Tested this behavior in Catalyst.
Before:
Screen.Recording.2026-04-07.at.18.25.01.mov
After:
Screen.Recording.2026-04-07.at.18.26.18.mov