How Next.js is delivering React’s vision for the future
summary
Next.js 13’s implementation of React server components and server actions moves data fetching and mutations back inside component boundaries so UI pieces stay composable. Example: a news story component queries the database on the server, a modal and carousel run client code, recommended reads defer with a suspense boundary to speed first render, and a bookmark mutation runs as a server action instead of an API route. Next.js streams server-rendered fragments and splits client code automatically, and the demo works end to end.
AI-written summary · about
chapters (8)
- 0:00Next.js and React's future
- 2:58Server components like React
- 7:52Composability conflict in React
- 9:35Server components restore composability
- 11:44Streaming and suspense on server
- 13:13Unifying server and client code
- 15:21Server actions and DB mutations
- 18:12Future of server-side in React
related talks
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
01h 07mDemystifying React Server Components
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
54mReact Server Components - Explained for Backend Developers
50mReact Server Components: A New Way to Build Fast and Interactive Web Apps
45mReact Server Components: Fad or Real Progress?
48mReact Server Components: A New Way to Build Fast and Interactive Web Apps
34mWhat's Next? Exploring the future of React