Does not work with babel's babel-plugin-jsx-control-statements plugin about vite-plugin-react HOT 4 CLOSED

Seems like an issue with the plugin that's doesn't work if the jsx transform is not done at the same time with Babel.
With vite-plugin-inspect:

JSX transform is done with esbuild since 3.0.

So for me this is not an issue with the vite plugin, more a limitation of a plugin built for a Babel only world. I would advice migrating away from Babel plugins for such a small gain. This can be implemented in few lines by a React component that does the same, or simply using ternary that are much more flexible. When using Babel plugins, you're running Babel in production build too, which is slower and blocks you from using other native toolchain like SWC, bun or new one to come.

from vite-plugin-react.

Ah! So the 3.0 version of the plugin can't work with any Babel plugins that work with JSX code since esbuild handles it now.

Will Babel plugins still work for pure JS files? I just want to understand if any Babel plugins would work with new 3.0 plugin version.

Is it possible to update the docs with these details?

from vite-plugin-react.

Everything should as normal, it just the plugin that doesn't handle the case of "jsx output".

The plugin should output {true ? "foo" : null} in that case instead of true ? "foo" : null

Other plugins that don't depend on that or handle it should work the same.

from vite-plugin-react.

Cool thanks! You can mark this issue closed.

from vite-plugin-react.