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
Is your feature request related to a problem? Please describe.
Currently, the new JSX transform is activated automatically for React >=17. Unfortunately, the ecosystem may not be ready for that change yet: for instance, SVG inlining may break when using the new Babel transform.
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 29, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature request
Is your feature request related to a problem? Please describe.
Currently, the new JSX transform is activated automatically for React >=17. Unfortunately, the ecosystem may not be ready for that change yet: for instance, SVG inlining may break when using the new Babel transform.
Describe the solution you'd like
According to the docs of Next, the React Babel preset's options could be overridden like below:
The
hasJsxRuntime
variable should respect this override and use the classic runtime when desired:next.js/packages/next/build/babel/preset.ts
Lines 123 to 144 in f7f376f
The text was updated successfully, but these errors were encountered: