chore(client-entry): Slight tweaks around entry.client handling #10741
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 was trying to better understand how
entry.client.tsx
was used during SSR, and when following the code I found a few things I wanted to change to, in my opinion, make the code easier to read, understand and follow.Even though
entry.server.tsx
is the main entry point for SSR, we still need to read the client build manifest and findentry.client.tsx
to get the correct links to insert for the initial CSS files the browser will eventually render when the finalized html output is being streamed to the browser. We also need it to tell React what JS bundle containshydrateRoot
when it'll eventually get to hydrating things in the browser