You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I attempted to simply drop the babel config in the react() plugin and set the esbuild: {target: "es2022"} and that didn't seem to work.
Do we have to wait for a new release or can we force it to use the feature with the right configuration? It's not clear to me how the puglin decides whether to use babel or not (it seems to even when I don't have have a babel config it does.
Suggested solution
Describe configuration to use latest esbuild with decorator support or bump the package?
You will need Vite to ship the new version of esbuild that was marked as breaking change by safety by Evan Wallace. This is plan for 5.3 that should be shipped this month. You can follow this issue for updates: vitejs/vite#16616
Description
ESBuild added support for decorators in 0.21. Hopefully this means a lot of projects can kill their usage of babel.
evanw/esbuild#104 (comment)
I attempted to simply drop the babel config in the
react()
plugin and set theesbuild: {target: "es2022"}
and that didn't seem to work.Do we have to wait for a new release or can we force it to use the feature with the right configuration? It's not clear to me how the puglin decides whether to use babel or not (it seems to even when I don't have have a babel config it does.
Suggested solution
Describe configuration to use latest esbuild with decorator support or bump the package?
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: