mirror of
https://github.com/cloudflare/vinext.git
synced 2026-05-09 08:25:34 +02:00
[GH-ISSUE #135] Track jsx-runtime compatibility for remaining shim .tsx modules #29
Labels
No labels
enhancement
enhancement
good first issue
help wanted
nextjs-tracking
nextjs-tracking
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vinext#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @liuxiaopai-ai on GitHub (Feb 26, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/135
Following review feedback on #45: while
error-boundary.tsxis fixed, several other shim modules still rely on JSX transform assumptions and may hit the samereact/jsx-runtimenamed-export mismatch in specific packaging setups.Candidate files called out in review:
packages/vinext/src/shims/link.tsxpackages/vinext/src/shims/metadata.tsxpackages/vinext/src/shims/legacy-image.tsxpackages/vinext/src/shims/form.tsxpackages/vinext/src/shims/document.tsxpackages/vinext/src/shims/image.tsxProposed follow-up:
React.createElementstyle, or@vitejs/plugin-rsc) so JSX transform remains robust regardless of user tsconfig/package interop.I can follow up with a focused PR once direction is confirmed.
@liuxiaopai-ai commented on GitHub (Feb 26, 2026):
Opened follow-up implementation PR: #136