React Server Components
summary
Argues that React Server Components solve both data‑fetching and bundle‑size problems by rendering async components on the server, shows a working demo built with Express and renderToString that awaits data with an unwrapGSX pass, fetches jokes from Keel using the DevJoke dataset, and implements soft navigation that preserves client state. Notes adoption is still tiny (~1% in the room), explains interplay with Next.js and use client client components, and the demo succeeds without flash‑of‑empty content.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:50React Server Components mechanism
- 4:12React purpose and performance
- 7:21Demo setup and client rendering
- 9:09Adding server-side rendering
- 11:39Fetching data on server
- 13:28unwrapJSX for async components
- 15:55Soft navigation with Server Components
- 18:44Server vs Client Components
- 20:06Closing remarks
related talks
30mReact Server Components
12mReact Server Components and SSR: How it Fits
40mServer Components for the Rest of Us
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
50mReact Server Components: A New Way to Build Fast and Interactive Web Apps
45mReact Server Components: Fad or Real Progress?
01h 07mDemystifying React Server Components