-
Notifications
You must be signed in to change notification settings - Fork 47k
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
Remove hydrate entry point from www builds #26400
Conversation
Comparing: d310d65...25eab9f Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
Unfortunately, it's still used in some places, eg. https://fburl.com/code/p66av4kc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup
Oh nice catch @kassens |
Actually, this is fine. |
Tests started failing on master after this was merged. Should we revert? |
I think Rick is already taking a look. If we don't have a quick fix, we'll revert |
Fix coming in #26412 |
Reverts #26400. Will take a look at the test failures before re-merging.
As I understand it this isn't used at Meta and it would let us get rid of at least legacy mode hydration code when we remove legacy mode from OSS builds.