Next.js documentation (opens in a new tab)
The official reference for the tools used in this lesson.
Link
What server components actually do
Server components run on the server and send rendered output rather than code. That is why they can read a database directly and why they add nothing to your bundle.
Lesson 2.115m 48sIntermediate15.4k students
Chapters
15:48- 0:00Introduction
- 0:45Basic Differences
- 3:23Server Component Benefit #1
- 5:22Server Component Benefit #2
- 6:32Server Component Benefit #3
- 7:58Server Component Benefit #4
- 8:25Server Component Benefit #5
- 8:58Server Component Downside #1
- 10:25Server Component Downside #2
- 10:45How To Nest Server And Client Components
What this lesson covers
- Render on the server and ship no component code to the client
- Read data and secrets directly, without an API round trip
- Understand why server components cannot hold state or effects
This lesson sits in Server and Client Components, part of Next.js App Router in Depth. It assumes what came before it and leads directly into the next lesson in the module.
In this lesson you will
- Render on the server and ship no component code to the client
- Read data and secrets directly, without an API round trip
- Understand why server components cannot hold state or effects
Resources
React docs: Server Components (opens in a new tab)
The upstream React explanation the Next.js implementation follows.
Link
Personal notes are coming soon.