Migrating Existing React Applications to Server Components

8min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

This chapter explores the challenges of migrating an existing React application to server components, discussing the rules for using server and client components together and using a tree metaphor to explain their differences. It also addresses the issue of integrating server and client components and the need for new design patterns.

Wes and Scott talk through server components, the difference between server components and client components, reasons to run something server side, how server components work, using forms and buttons, what they like and don’t like about it, and tips to learn more.

Show Notes

00:10 Welcome
00:52 Syntax Brought to you by Sentry
01:39 New Heights with Scott and Wes
04:33 What are React Server Components?
10:52 The difference between server components and client components
Tweet: "React Server + Client Components Visualized There is a bit of a learning curve to learn new patterns, but the ease of going between client and server will be worth it.
11:37 Why would you want to run something server side?
15:22 Components are server rendered by default
16:40 What is JS sprinkles?
17:29 How do server components work?
18:51 Moving an existing site to React server components take a while
20:27 The rules
27:12 Form Actions + Server Actions
32:07 Buttons can have actions
36:32 React Suspense
39:13 What we like
Ryan Florence thread
41:54 What we don’t like
47:13 Design patterns
47:35 Other things
RSC Devtools
Introducing Waku
Mux
49:22 Sick Picks