Fix 1: Lazy load page sections #1
Open
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
grgur
force-pushed
the
fix/01-lazy-entire-sections
branch
from
3ef83ba
to
7afca01
Compare
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.
Using
SuspenseandReact.lazy(), we isolated entire sections of the page and lazy load them.Note that Suspense is wrapped around each of the lazy components. That ensures separate async threads.
Suspense is not wrapping the entire app because that would cause Menu and Hero to wait for the other components to load before rendering.
Instead, we focus on rendering Hero and Menu first.