What’s the link between Server Components and Suspense for Data Fetching?

Frontend First

English - February 25, 2022 17:33 - 1 hour - 66.5 MB - ★★★★★ - 18 ratings
Technology technology web javascript ember ember.js software development design Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed

Previous Episode: Internal apps vs. public websites

Next Episode: Auth-based route guards in Next.js and debugging in production

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 - Intro5:19 - Using startTransition with a router9:36 - How React 18 yields21:37 - Why both Suspense for Data Fetching and Server Components need a way to invalidate React’s cache37:24 - How Server Components can remove the need for explicit API calls without sacrificing any of React’s composability1:01:00 - Real-world problems concurrent features address1: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