What’s the link between Server Components and Suspense for Data Fetching?
from Frontend First Hosted by Frontend First
Sam and Ryan talk about why Suspense for Data Fetching isn’t ready yet, and how both it and the Server Components feature of React 18 rely on the ability to evict a cache that’s internal to React. They also talk about Transitions. Topics include: 0:00 - Intro 5:19 - Using startTransition with a router 9:36 - How React 18 yields 21:37 - Why both Suspense for Data Fetching and Server Components need a way to invalidate React’s cache 37:24 - How Server Components can remove the need for explicit API calls without sacrificing any of React’s composability 1:01:00 - Real-world problems concurrent features address 1:03:20 - Moving state from React to the URL Links: Sam’s video: How to remove loading spinners in Next.js Ryan’s video: Transitions that Suspend React Server Components React Working Group - React 18 React Server Components and Remix
Embed this episode
What this episode covers
Sam and Ryan talk about why Suspense for Data Fetching isn’t ready yet, and how both it and the Server Components feature of React 18 rely on the ability to evict a cache that’s internal to React. They also talk about Transitions.
No transcript yet.