Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix!: don't force optimization of jsx-runtime #132

Merged
merged 1 commit into from Mar 30, 2023
Merged

Conversation

ArnaudBarre
Copy link
Member

@ArnaudBarre ArnaudBarre commented Mar 30, 2023

On my testing I found that this is correctly found by the optimiser.
No body also complain about the missing entry when not using the default one.

There is one edge case in the ssr test that fails on windows and ubuntu (node 14&16, not 18 🤦‍♂️). This is due to Vite returning an error for non variable/on going reprocessed of the pre-bundled deps. As this happens on a very particular setup, only in dev, and can be fixed by manually passing it in the config, I think the change should be part of the major.

With that we can make it clear that this is not expected to be set for TS projects, which was asked by some, and allow the niche case asked once of different runtime inside the same app (works great if not set thanks to tsconfck)

This other option is to invite people to pass is and have something like this: https://github.com/vitejs/vite-plugin-react-swc/blob/7fde2e9d748fc502f4463e81484cf8d6e34f69b5/src/index.ts#L65

@ArnaudBarre ArnaudBarre merged commit e26bb67 into main Mar 30, 2023
8 checks passed
@ArnaudBarre ArnaudBarre deleted the jsxImportSource branch March 30, 2023 10:42
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.

None yet

2 participants