-
Notifications
You must be signed in to change notification settings - Fork 47.1k
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
Enable lazy context propagation #30935
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Comparing: 66cf2cf...e2552bc Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: Expand to show |
I think @jackpope is still investigating this, Jack can you add thoughts here? |
Yes the results were good and we can move forward with this. In terms of timing, we had discussed holding off on the change until after 19 stable just to prevent additional changes from the release out of an abundance of caution. But at this point there's no evidence of bugs or regressions. We have also discussed ways to improve propagation performance when React.memo boundaries are hit by combining the eager propagation fallback pass and the render pass into a single lazy render pass that only checks on changed context values. But this could be an additional optimization we look into and doesn't need to block this improvement. |
Following #30935 let's turn this on across the board so we can clean up experiments in RN.
Last I heard this was great so not sure there are any more blockers to just include it in 19?