You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, I had an epiphany while working with Parallel Routes, where each of the "Slots" has its own data-fetching function using async. Due to the nature of async and the layout structure of Parallel Routes, the data is fetched sequentially rather than in parallel, leading to longer data-fetching times in my dashboard.
Is there a known way to leverage the benefits of Parallel Routing while ensuring that data is fetched in parallel?
Any help or guidance would be greatly appreciated!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Next.js users,
Today, I had an epiphany while working with Parallel Routes, where each of the "Slots" has its own data-fetching function using async. Due to the nature of async and the layout structure of Parallel Routes, the data is fetched sequentially rather than in parallel, leading to longer data-fetching times in my dashboard.
Is there a known way to leverage the benefits of Parallel Routing while ensuring that data is fetched in parallel?
Any help or guidance would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions