| name | nextjs-16-2-4 |
| description | Build production-ready React applications with Next.js 16.2.4, providing App Router and Pages Router, server/client components, routing, data fetching, caching, API routes, and deployment. Use when creating modern web applications requiring SSR/SSG/ISR, SEO-friendly rendering, TypeScript support, or full-stack JavaScript development. |
Next.js 16.2.4
Changelog (16.2.3 → 16.2.4)
Patch release with the following fixes:
- reqwest bumped to 0.13.2
- Turbopack: fixed filesystem watcher config not applying
follow_symlinks(false)
- Pages Router: scoped Safari
?ts= cache-buster to CSS/font assets only
- React Compiler: added support for boolean and number primitives in
next.config defines
- turbo-tasks: fixed recomputation loop by allowing cell cleanup on error during recomputation
- Turbopack: shorter error messages for
ChunkGroupInfo::get_index_of and ModuleBatchesGraph::get_entry_index
- Added more system info to the 'initialize project' trace
Overview
Next.js is a React framework for building full-stack web applications. You use React Components to build user interfaces, and Next.js for additional features and optimizations. It automatically configures lower-level tools like bundlers and compilers so you can focus on building your product and shipping quickly.
Whether you're an individual developer or part of a larger team, Next.js helps you build interactive, dynamic, and fast React applications. Used by some of the world's largest companies, it extends the latest React features and integrates powerful Rust-based JavaScript tooling for the fastest builds.
When to Use
- Building full-stack web applications with React
- Projects requiring server-side rendering (SSR) or static site generation (SSG)
- Applications needing SEO-friendly pages with automatic metadata management
- APIs and backend-for-frontend patterns using Route Handlers
- Projects benefiting from file-system based routing
- Applications requiring image optimization, font loading, and CSS handling out of the box
- Deployments to Vercel, Node.js servers, Docker containers, or edge platforms
Core Concepts
Next.js 16 has two routers:
- App Router — The newer router supporting React Server Components, streaming, and the
app/ directory convention. Uses React canary releases built-in (including all stable React 19 changes).
- Pages Router — The original router, still supported and being improved. Uses the React version from your
package.json.
Key architectural pillars:
- File-system routing — Folders and files define routes
- Server Components — Fetch data and render UI on the server by default
- Client Components — Add interactivity with
"use client" directive
- Caching — Built-in data caching with
use cache directive and Cache Components
- Streaming — Progressive rendering of uncached data via
<Suspense>
- Turbopack — Rust-based incremental bundler built into Next.js
Installation / Setup
Minimum Node.js version: 20.9+. Supported operating systems: macOS, Windows (including WSL), and Linux.
Supported browsers: Chrome 111+, Edge 111+, Firefox 111+, Safari 16.4+.
Create a new app with the CLI:
npx create-next-app@latest my-app --yes
cd my-app
npm run dev
The --yes flag skips prompts using defaults: TypeScript, Tailwind CSS, ESLint, App Router, and Turbopack. Without it, you can customize settings including linter choice (ESLint or Biome), React Compiler, src/ directory, and import aliases.
For manual installation:
npm i next@latest react@latest react-dom@latest
Add scripts to package.json:
{
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start"
}
}
Advanced Topics
App Router Fundamentals: Layouts, pages, navigation, and project structure → App Router Fundamentals
Server and Client Components: React Server Components, Client Components, data fetching, and streaming → Server and Client Components
Routing: Dynamic routes, parallel routes, intercepting routes, route groups, and proxy → Routing
Data Caching and Revalidation: Cache Components, use cache, cacheLife, cacheTag, and revalidation strategies → Data Caching and Revalidation
API and Backend: Route Handlers, Server Actions, environment variables, and proxy configuration → API and Backend
Metadata and SEO: Static and dynamic metadata, OG images, sitemaps, and robots → Metadata and SEO
Styling and Assets: CSS, Tailwind CSS, Image optimization, and Font loading → Styling and Assets
Deployment: Node.js servers, Docker, static export, adapters, and platform deployment → Deployment