Merged
Conversation
e95c0d3 to
48ab421
Compare
48ab421 to
686b6e7
Compare
Collaborator
|
Great, thanks for this! |
686b6e7 to
2c1d63b
Compare
mattgperry
approved these changes
Apr 16, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR updates the jsx transform to the one introduced with React 17: https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Starting with React 19, there will be a warning when using the old one (see facebook/react#28781), plus the new transform gives a nice speed-bump with React 19: facebook/react#28781
I've also run
npx react-codemod update-react-imports .to update / remove imports where not needed. I've split those into two commits so that the config changes and the autofixes can be looked at separately.