Following review feedback on #45: while error-boundary.tsx is fixed, several other shim modules still rely on JSX transform assumptions and may hit the same react/jsx-runtime named-export mismatch in specific packaging setups.
Candidate files called out in review:
packages/vinext/src/shims/link.tsx
packages/vinext/src/shims/metadata.tsx
packages/vinext/src/shims/legacy-image.tsx
packages/vinext/src/shims/form.tsx
packages/vinext/src/shims/document.tsx
packages/vinext/src/shims/image.tsx
Proposed follow-up:
- Decide whether to normalize these shims to
React.createElement style, or
- Fix at plugin level (
@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.
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.