Skip to content

Handle props on Fragment error due to Symbol(react.lazy)#3873

Merged
RobinMalfait merged 6 commits into
mainfrom
fix/handle-react-lazy
Apr 7, 2026
Merged

Handle props on Fragment error due to Symbol(react.lazy)#3873
RobinMalfait merged 6 commits into
mainfrom
fix/handle-react-lazy

Conversation

@RobinMalfait
Copy link
Copy Markdown
Member

@RobinMalfait RobinMalfait commented Apr 7, 2026

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.lazy elements.

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

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
headlessui-react Ready Ready Preview, Comment Apr 7, 2026 4:58pm
headlessui-vue Ready Ready Preview, Comment Apr 7, 2026 4:58pm

Request Review

@RobinMalfait RobinMalfait enabled auto-merge (squash) April 7, 2026 16:58
@RobinMalfait RobinMalfait merged commit b0dcd8f into main Apr 7, 2026
8 checks passed
@RobinMalfait RobinMalfait deleted the fix/handle-react-lazy branch April 7, 2026 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Next.js Link Documentation Example

1 participant