Support React 18's new client side rendering #1151
Merged
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
With React 18, the rendering interface will be updated in order to benefit from new features. reactwg/react-18#5 This allows React 18 rendering to be supported while creating backwards compatibility. For the time being, the return of the components does not change the output from the previous versions so as to not cause any breaking changes.
BookOfGreg
approved these changes
Dec 19, 2021
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Summary
React 18 is changing the way that client-side components are rendered and hydrated. See reactwg/react-18#5
In order to create a path forward to using React 18, this adds support for both methods of hydrating and rendering so that newer React features can be used while maintaining full backward compatibility.
Other Information
I did not add any specific tests for this because there was no clear way to test for different versions of React. This seems like it should be explored in separately.