Use the new JSX transform #25064
Merged
Use the new JSX transform #25064
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ClearlyClaire
requested changes
May 22, 2023
renchap
force-pushed
the
new-jsx-transform
branch
from
f1b7e16
to
bd0d207
Compare
Changes done using the official codemod, then a few manual changes to remove `import *`
renchap
force-pushed
the
new-jsx-transform
branch
from
bd0d207
to
28af36b
Compare
ClearlyClaire
approved these changes
May 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the React 18 PR has been merge, here is the second part.
React 17 introduced a new way of handling JSX: https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
I used the official codemod (
npx react-codemod update-react-imports) to remove every import, with a few hand-made changes where the codemod did not work.