-
-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepping for React 18's render process #1408
Comments
@kylemellander I definitely want to support this. If you've got any suggestions or a PR, very much appreciated! |
@justin808 I've been exploring the way that the dummy apps are generated for the test suite, but have hit a wall with determining how to test against multiple versions of React so that we can make sure that we have forward and backward compatibility. Part of the issue here is that I'm struggling to see a few things about the construction of the test suite since it is very dynamic. My thinking is that if we have multiple react versions that we can set in the package.json, and we can run across multiple versions, then it will ensure that the React versions are compatible. The package.json, though, seems to be generated in an unconventional way, and I am struggling to determine where the react versions are being pulled from (my local version sets them at React 17.0.2, but I don't see that version used anywhere else in the library). I'd love to put our brains together on how to make this happen, but for now, I'm going to focus on getting it to work manually for React 18 and have the tests catch React < 18. |
Also, looking at the updates to use |
Released in 12.5.0. |
In React 18, the render process is triggered differently. For more reference, see reactwg/react-18#5.
I have not dug into the internals, but I do know that there are also updates how to do SSR that could help with performance for React 18. More information is here: reactwg/react-18#22
I'm going to dig into researching this more and potentially opening a PR.
I think this might possibly be related to #1383, but I'm not positive.
The text was updated successfully, but these errors were encountered: