Exploring the Concept of Server Components in Vanilla React Apps

2min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

This chapter delves into the concept of server components in vanilla React apps, highlighting that server components in this context refer to what serves the app rather than React components. It touches on how servers in vanilla React apps can take various forms, including servers running React, build steps, or frameworks like Remix, while mentioning upcoming projects like Tan Stack focusing on server components.

Scott and Wes are here to guide you through the world of React Server Components, shedding light on the intricacies of Form Actions and Server Actions. Get ready to level up your React skills as they discuss the ins and outs of these powerful features and share their expert advice on optimizing your applications.

Show Notes

00:00 Welcome to Syntax!
Show 718 React Server Components.
02:04 Brought to you by Sentry.io.
03:04 What are form actions?
GitHub Add React.useActionState PR
04:05 Almost entirely React.
04:31 What is the ‘server’ in Vanilla React?
06:10 Would React ever ship their own server?
07:29 What are actions?
08:34 Two huge benefits to actions.
- 08:45 Avoid custom useEffects or third party libraries.
- 09:17 Calling server code from the client without any APIS.
11:31 Some examples of actions.
12:54 Can these actions be done in a client component?
13:40 Where to use actions.
- 13:49 On a form submit.
- 15:30 In an event handler.
- 15:57 In a useEffect().
17:13 How to actually use an action.
React Hooks
- 17:30 useActionState() hook.
  - 18:49 The state of the action.
  - 19:35 The bound action.
  - 19:46 The pending state.
- 23:16 useFormStatus() hook.
24:38 Action inputs.
26:13 Server vs client.
28:30 This is not PHP.
30:31 What is optimistic UI?
- 33:26 useOptimistic() hook.
37:02 Some final thoughts.
40:18 Sick Picks + Shameless Plugs.