Next.js Doesn't Render Pages Anymore. It Streams Something Stranger.

7.9 relevance

Deep dive into Next.js RSC and streaming is highly technical, actionable for web developers, and matches SDLC trends.

DevTools dev.to

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

As a platform engineer building with Next.js, this clarifies the actual rendering model behind App Router, preventing common SSR bugs and informing decisions about component architecture, data fetching, and bundle optimization.

Key Takeaways

Treat 'use client' as a bundling boundary, not an execution environment—always guard browser-only APIs with checks like `typeof window !== 'undefined'`.

Next.js Doesn't Render Pages Anymore. It Streams Something Stranger.

Summary

Next.js Client Components execute on the server during initial SSR, not just in the browser. The 'use client' directive defines a module boundary for bundling, not execution location—both Server and Client Components run on the server for pre-rendering, with Client Components additionally shipping JavaScript for hydration. Misunderstanding this leads to bugs like `window is not defined` during server execution.

Author

S M Tahosin