next.js: a full-stack React framework

What it is

Next.js is a full-stack React framework with routing, server and client components, data access, rendering modes, asset handling and deployment conventions under one roof. The App Router makes the server and browser halves of a React product explicit, even if “explicit” sometimes arrives as a stack trace written in modern dance.

Best for

It fits product teams that want React across the stack, need server rendering or static generation, and prefer a well-travelled convention over assembling routers, build tools and server glue themselves. The ecosystem and Vercel path are difficult to match.

Avoid it if

Do not choose it merely because the frontend uses React. A client-only application may need Vite and a router, not an entire rendering framework. Teams that require portable, transparent infrastructure should also price in caching semantics, framework upgrades and the difference between Next.js itself and Vercel-specific convenience.

Current state

Next.js 16.3.2 shipped on 21 August 2026. Version 16 requires Node.js 20.9 or newer and TypeScript 5.1 or newer. Turbopack is the default for development and builds. Synchronous request APIs are gone, middleware is deprecated in favour of proxy, and custom Webpack configurations need deliberate handling because a default Turbopack build will stop rather than silently ignore them.

Alternatives

Astro is the sharper choice when content dominates. Remix and React Router Framework Mode lean closer to web primitives. Nuxt and SvelteKit offer comparable full-stack models in other component ecosystems. Vite plus a router remains gloriously sufficient for many browser applications.

Why it belongs

It belongs because Next.js is no longer just a React starter. It is a consequential systems choice with excellent capabilities, a huge knowledge base and enough opinions to deserve an informed yes rather than an automatic one.

Get started

• Scaffold: npx create-next-app@latest.
• Start with the App Router and identify each component as server or client by necessity, not habit.
• Before upgrading an existing application, run the official codemod and read the version-specific migration guide, particularly caching and Turbopack changes.