-
Notifications
You must be signed in to change notification settings - Fork 23
[Web] Implement lazy loading and code splitting for routes #289
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
Open
Devasy
wants to merge
1
commit into
main
Choose a base branch
from
perf/web-lazy-loading-5373769426958556884
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| import React from 'react'; | ||
| import { Spinner } from './Spinner'; | ||
|
|
||
| export const PageLoader = () => { | ||
| return ( | ||
| <div className="h-screen w-full flex items-center justify-center"> | ||
| <Spinner size={48} className="text-emerald-500 dark:text-emerald-400" /> | ||
| </div> | ||
| ); | ||
| }; |
Oops, something went wrong.
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.
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.
🧹 Nitpick | 🔵 Trivial
Single Suspense boundary will flash the loader on every route transition.
With a single
<Suspense>wrapping all<Routes>, navigating between two already-loaded routes is fine, but navigating to a not-yet-loaded route will unmount the current page and show the full-screen<PageLoader />until the chunk arrives. This can feel jarring compared to keeping the previous page visible while the next one loads.Two mitigation options (non-blocking, can be done as follow-up):
startTransition(or react-router's built-in transition support) so React keeps the old UI visible during the lazy load, showing the spinner only if loading takes too long.<Layout>so the shell (nav, sidebar) stays rendered while only the content area shows a loader.Neither is required for this PR to ship—the current behavior is correct and a clear improvement over no code splitting.
🤖 Prompt for AI Agents