Next.js

Next.js 16 • Cache Components • Turbopack enabled by default • Turbopack file system caching (beta) • Optimized navigations and prefetching • Improved caching APIs • Build Adapters API (alpha) • React 19.2 nextjs.org/blog/next-16

Turbopack now tree shakes destructured dynamic imports the same way it does static imports. 𝚌𝚘𝚗𝚜𝚝 { 𝚌𝚊𝚝 } = 𝚊𝚠𝚊𝚒𝚝 𝚒𝚖𝚙𝚘𝚛𝚝('./𝚕𝚒𝚋') Unused exports are removed from the bundle.

Server Fast Refresh brings browser-style hot reloading to server code. Only the changed module is reloaded instead of clearing the entire 𝚛𝚎𝚚𝚞𝚒𝚛𝚎.𝚌𝚊𝚌𝚑𝚎 chain. Up to ~375% faster server-side updates in real Next.js apps.

Turbopack: What's New in Next.js 16.2 • Up to ~375% faster updates with Server Fast Refresh • Improved Web Workers support • Subresource Integrity (SRI) support • Tree shaking for dynamic 𝚒𝚖𝚙𝚘𝚛𝚝() • 200+ bug fixes nextjs.org/blog/next-16-2…

The error overlay now displays up to five levels of 𝙴𝚛𝚛𝚘𝚛.𝚌𝚊𝚞𝚜𝚎 chains, making it easier to trace errors that wrap other errors.

Hydration mismatch errors now show a + 𝙲𝚕𝚒𝚎𝚗𝚝 / - 𝚂𝚎𝚛𝚟𝚎𝚛 label, so you can clearly spot each environment.

Next.js 16.2 • Up to ~60% faster rendering • Up to ~400% faster 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 startup • Server Function 𝚍𝚎𝚟 logging • Redesigned error page • Better hydration errors • 𝙴𝚛𝚛𝚘𝚛.𝚌𝚊𝚞𝚜𝚎 display in error overlay nextjs.org/blog/next-16-2

Updated evals: nextjs.org/evals Set up guide: nextjs.org/docs/app/guide…

Next.js installs will soon include version-matched docs, giving agents context on new and recently updated APIs. In our evals, this improved success rates by ~20%. Try it out: 𝚗𝚙𝚡 𝚌𝚛𝚎𝚊𝚝𝚎-𝚗𝚎𝚡𝚝-𝚊𝚙𝚙@𝚌𝚊𝚗𝚊𝚛𝚢

As more Next.js apps are built with AI, we've been focusing on improving the agent experience. Here's what we've learned, and how we're thinking about agents as first-class users ↓ nextjs.org/blog/agentic-f…

GPT 5.3 Codex has achieved the highest success rate on Next.js evals. View the leaderboard ↓ vercel.fyi/next-evals-2-5

Learn more about this pattern: nextjs.org/docs/app/guide…

Two ways to handle a blocking component in Next.js: • Cache: so it can be prerendered with the rest of the page. • Stream: so the rest of the page doesn't have to wait for it.

How we're making Turbopack fast. In this deep dive, @lukeisandberg explains how Turbopack uses incremental caching and compilation so the cost of work scales with your change, not the size of your app.

Introducing next-skills, a skill set for Next.js App Router best practices, version upgrades, and performance features like cache components. How to install ↓ npx skills add vercel-labs/next-skills

Learn how we built Turbopack with incremental computation to scale development and builds to Next.js applications of all sizes. nextjs.org/blog/turbopack…

More: #turbopack-file-system-caching-for-next-dev" target="_blank" rel="nofollow noopener">nextjs.org/blog/next-16-1…

Next.js 16.1: Turbopack filesystem caching for 𝚍𝚎𝚟 is now enabled by default. Example field test in an open-source app: 3.7s → 336ms