Optimizing Loaders with Component Grouping
What about the Card
components, should we add the laoder for each card or how to handle this component.
When fetching data for individual <Card>
components, a potential issue arises - loading each card separately may cause a popping effect as they load in. This sudden visual change can be jarring for users.
To mitigate this problem, consider the following steps in the page.tsx
file.
Back to the Project
- Delete the
<Card>
components; - Delete the
fetchCardData()
function; - Import a new wrapper component called
<CardWrapper />
; - Import a new skeleton component called
<CardsSkeleton />
; - Wrap
<CardWrapper />
inSuspense
.
- Navigate to
app/ui/dashboard/cards.tsx
; - Import
fetchCardData()
; - Invoke
fetchCardData()
inside the<CardWrapper/>
component; - Uncomment necessary code.
In Practice
Grazie per i tuoi commenti!
Chieda ad AI
Chieda ad AI
Chieda pure quello che desidera o provi una delle domande suggerite per iniziare la nostra conversazione
Awesome!
Completion rate improved to 2.08
Optimizing Loaders with Component Grouping
Scorri per mostrare il menu
What about the Card
components, should we add the laoder for each card or how to handle this component.
When fetching data for individual <Card>
components, a potential issue arises - loading each card separately may cause a popping effect as they load in. This sudden visual change can be jarring for users.
To mitigate this problem, consider the following steps in the page.tsx
file.
Back to the Project
- Delete the
<Card>
components; - Delete the
fetchCardData()
function; - Import a new wrapper component called
<CardWrapper />
; - Import a new skeleton component called
<CardsSkeleton />
; - Wrap
<CardWrapper />
inSuspense
.
- Navigate to
app/ui/dashboard/cards.tsx
; - Import
fetchCardData()
; - Invoke
fetchCardData()
inside the<CardWrapper/>
component; - Uncomment necessary code.
In Practice
Grazie per i tuoi commenti!