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
Clean up partial renderer entry points #21682
Merged
sebmarkbage
merged 2 commits into
facebook:master
from
sebmarkbage:fizzcleanupentrypoints
Jun 14, 2021
Merged
Clean up partial renderer entry points #21682
sebmarkbage
merged 2 commits into
facebook:master
from
sebmarkbage:fizzcleanupentrypoints
Jun 14, 2021
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
facebook-github-bot
added
CLA Signed
React Core Team
Opened by a member of the React Core Team
labels
Jun 14, 2021
sebmarkbage
changed the title
[Clean up partial renderer entry points
Clean up partial renderer entry points
Jun 14, 2021
Comparing: bd45ad0...e4e5909 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 made a mistake by leaving server.browser.stable in which is the partial renderer for the browser build of stable. That should use the legacy fizz one. Since the only usage of the partial renderer now is at FB and we don't use it with Node, I removed the Node build of partial renderer too.
No code is running this path anymore. Ideally this should be ported to a Fizz form.
sebmarkbage
force-pushed
the
fizzcleanupentrypoints
branch
from
June 14, 2021 22:35
ddf5e8f
to
e4e5909
Compare
I deleted the GC tests since nothing runs them now. I think there's some similar cases that could be tested in Fizz since there are places where we need to switch context at the right places. Those are very different tests but should ideally exist. |
gaearon
approved these changes
Jun 14, 2021
koto
pushed a commit
to koto/react
that referenced
this pull request
Jun 15, 2021
* Clean up partial renderer entry points I made a mistake by leaving server.browser.stable in which is the partial renderer for the browser build of stable. That should use the legacy fizz one. Since the only usage of the partial renderer now is at FB and we don't use it with Node, I removed the Node build of partial renderer too. * Remove GC test No code is running this path anymore. Ideally this should be ported to a Fizz form.
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.
I made a mistake by leaving server.browser.stable in which is the partial renderer for the browser build of stable. That should use the legacy fizz one.
Since the only usage of the partial renderer now is at FB and we don't use it with Node, I removed the Node build of partial renderer too.