Streaming in Next.js
summary
Experimental Next.js feature enables streaming with getServerSideProps by splitting server rendering into a two-flush pattern: first flush sends headers and head as soon as routing finishes, second flush sends body when data is ready. Early tests report a 2–5% LCP gain translating to roughly 400–600 ms saved in many cases. It targets React 17 apps, requires moving next/head and next/script into the top app component, and forces client-side error handling because status headers are sent before full render.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:30CSR Loading
- 13:25Current SSR Loading
- 17:03Two-flush strategy
- 18:45Current API
- 19:56Prospective API
- 20:45Caveats
- 24:05Move and
related talks
16mStreaming Server Side Rendering simplified with Next.JS
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
25mProgressive Rendering – how to make your app render sooner
48mReact Server Components: A New Way to Build Fast and Interactive Web Apps
30mJust another ECMAScript Trait Syntax ProposalStop breaking the web and start building server-rendered web apps using next.js
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
39mWe Deserve a Better Streams API for the Web
16mThe time to go full stack is now
