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
While this PR solves a great issue, it emits creatElement() which is a React only API for backcompatibility, since key is part of the props. It would be great to have a way to emit modern JSX only, without fallback to support a legacy / only-react API.
Input code
No response
Config
No response
Playground link
No response
Expected behavior
Always emit jsx(), never createElement()
Actual behavior
No response
Version
nightly
Additional context
No response
The text was updated successfully, but these errors were encountered:
I'm not sure if I understood this correctly: are you saying swc does not allow to use new api, or either there is a condition forces your code transpiled into createelement?
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
Describe the bug
#7128
While this PR solves a great issue, it emits
creatElement()
which is a React only API for backcompatibility, since key is part of the props. It would be great to have a way to emit modern JSX only, without fallback to support a legacy / only-react API.Input code
No response
Config
No response
Playground link
No response
Expected behavior
Always emit
jsx()
, nevercreateElement()
Actual behavior
No response
Version
nightly
Additional context
No response
The text was updated successfully, but these errors were encountered: