Frontend First

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

Feb 25, 2022

01:12:36

Creator website

AI Chapters

Episode notes

Introduction

2min

Snowboarding in Taho

3min

Deferred Value

4min

React

4min

React 17 - Is There a Transition?

5min

What's the Difference Between Update and Transition?

3min

Is Skeleton a Suspense Boundary?

2min

Y, You Want to Preload a New Page?

4min

A Pland React Tree React

4min

10.

React Modeling

2min

11.

How Does It Know Which Components Depend on It?

3min

12.

React

4min

13.

React Is a Server Component, You Don't Need a Grap C Server.

2min

14.

Transition of Suspense

2min

15.

Is the Server Component Just Running on the Server?

4min

16.

Using Ritis, Is It Really a Server Component?

2min

17.

Server Components

4min

18.

React

4min

19.

React 18 Is in Release Candidate?

2min

20.

Transition With a React Framework

4min

21.

A New Kind of Miny Course for Queering and Sorting

4min

22.

How to Write Tests That Are Easy to Write

4min

23.

Servrc Omponents - Lie, Ye, It Was Good, Ie.

1min

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: