Blog

One file to guard every route — plus the Next.js 16 rename that moves it off the Edge runtime, the request-vs-response header trap that leaks user IDs to the browser, and the CVE that explains why this can never be your only auth layer.

Server Actions collapse form handling into a single server function—no API route, no manual fetch, no useState for loading. Here's the pattern that replaces 80% of your mutation boilerplate.

Parallel routes let a single layout render multiple independent pages at once. Combine them with intercepting routes and you get URL-aware modals with zero hacks.

Four caching layers, three revalidation APIs, and the Next.js 16 rename that turns everything you learned in 15 into the "previous model". Here's the complete mental model for data fetching in the App Router.

If you're still writing pages/api/... files in a new Next.js project, stop. Route Handlers are the App Router's replacement, and they're meaningfully better — typed, streaming-capable, and built on the same Web platform APIs that Cloudflare.

Astro's JavaScript floor is zero; Next.js's is a framework baseline. That one architectural difference — hydration opt-in vs opt-out — decides most of this comparison, and it matters much less than it sounds once your users are logged in.

One 'use client' at the top of your layout wipes out every performance benefit RSC offers. Learn how to push the boundary to leaf components and keep your server tree intact.

Next.js has the ecosystem and Vercel's backing. React Router has a cleaner model for interactive apps and a lighter client bundle. Also: "Remix 3" is now a different framework entirely — here's what that means for the choice.

Most teams hit 'use client' everywhere and wonder why their bundle explodes. The fix is a single mental model: keep the boundary as low as possible, and use composition to thread server-rendered content through client islands.