0
Challenge · 100React 19 Frontier
Server Actions, Hydration & Streaming SSR
React 19used in ~15% of apps
Your page loads instantly as HTML — then for a split second nothing works. That gap between "painted" and "interactive" is hydration, and the way modern React closes it (streaming SSR) and the way it lets a form talk to the server with no API route you hand-write (Server Actions) are the three frontier ideas that make a fast full-stack React app possible.
Core idea. The server renders your components to HTML and streams it to the browser so the user sees content fast; the browser then runs your JS to attach event handlers to that existing HTML (hydration); and Server Actions let a function marked "use server" run on the server when a form is submitted — no fetch, no API endpoint.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
0
Idle1
Server render2
Stream chunks3
First paint4
JS arrives5
HydratedRequest the page
browser viewportblank
waiting for request…
server: renderToPipeableStream(<App/>)
stream: <html>… flushed in chunks →
stream: <Suspense> fallback first, then data
browser: paint HTML (fast FCP, no JS)
browser: download client bundle.js
hydrateRoot(el, <App/>) — attach handlers
JS attached: no
Try clicking Like before stage 5.
↑ play a little first, then dig in