-
Notifications
You must be signed in to change notification settings - Fork 54
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
Doesn't work with swc #72
Comments
I recall that was fixed at #52 by @spa5k, but it seems the related issue at Also here's the related closed issue at |
There seems to be some problems related with jsx tsx stuff and vite isn't compiling them (swc version) |
@oedotme since vite isnt considering tsx / jsx files, maybe we can do an experimental package if it works after transpiling it to latest JS ESNEXT (through tsup or rollup) |
@spa5k TBH, I'd vote to wait for |
@oedotme |
It works with latest vite, you need to use react plugin, not the react plugin swc one |
Although it's recommended to use the latest Vite versions, Vite v3 still working fine with This issue is about the new plugin for React with Vite based on |
Hi, So turns out ts + dts file are not working to silence the error. So I think it's better to bundle the lib to avoid this kind of issue. I still think we should push TS to better support this and I added support for transpiling TS files in node_modules in the SWC plugin (not released yet). For info I think the modal is not working on the basic demo for react-router. |
Hey everyone, I've tested it with the latest version I'm closing this now, please let me know if you have any issues with the |
@ArnaudBarre Thanks for mentioning the modals with the basic example, I believe it's working but there's no modals created/available to show 😃 I'm currently working on improving the examples and docs 🙌 |
When using
"@vitejs/plugin-react-swc": "^3.1.0"
instead of"@vitejs/plugin-react": "^3.1.0"
, running the app fails with an exception2:50:04 PM [vite] Internal server error: Invalid glob import syntax: Expect CallExpression, got BinaryExpression
The text was updated successfully, but these errors were encountered: