chore: update React to v18.x #5887
Draft
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
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.
This is an ongoing PR to update React to v18. Since Clay packages are distributed without
reactdependencies andreact-domonly as peer dependencies, this will not affect those using version 16, but we also cannot yet use the new features of React 18, but we can implement compatibility for some likeuseId.To migrate, the first step now would be to update all tests that are still using
react-test-rendererto jest, there are still some left.The second step would be to add StrictMode to fix component errors and misuse of
useEffectthat may exist.The third step is to add compatibility for some new features like
useIdso that it works for both v16 and v18.