Nuxt Server Components Crash Course
summary
Shows how renaming component files with a server suffix makes them render only on the server, and how prop changes trigger fetches that return HTML (demoed with a live counter and visible Network requests). Explains enabling islands via nuxt.config keys componentIslands and selectiveClient: true, nested client hydration using a client attribute, and splitting into counter.server / counter.client files. Warns each server component renders as its own Nuxt app, which can hurt performance.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:13Nuxt Server Components
- 3:37Live counter demo
- 6:15Counter as server component
- 9:26Nesting client in server
- 15:12Paired components
- 18:25Performance tips
- 19:51Nuxt Tips Collection
- 22:01Mastering Nuxt 4 update
- 23:04Q&A
related talks
24mShip less javascript to your client with Nuxt Island
34mFast Nuxt.js Applications with PRPL Pattern
12mExploring the Power of React Server Components
44mReact Server Components 101
29mNuxt.js
38mLarge Scale Nuxt Architecture
45mReact Server Components: Fad or Real Progress?
32mUnderstand the hard parts of Nuxt