Next.js 16.2: AI Improvements
• Next.js-aware browser lets Agents improve your app
• 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 included in 𝚌𝚛𝚎𝚊𝚝𝚎-𝚗𝚎𝚡𝚝-𝚊𝚙𝚙 by default
• Browser errors forwarded to terminal
• Dev server lock file prevents duplicate servers
nextjs.org/blog/next-16-2-ai
𝚌𝚛𝚎𝚊𝚝𝚎-𝚗𝚎𝚡𝚝-𝚊𝚙𝚙 now ships 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 by default, pointing agents to version-matched docs bundled in 𝚗𝚘𝚍𝚎_𝚖𝚘𝚍𝚞𝚕𝚎𝚜.
This hit a 100% eval pass rate vs. 79% for skill-based approaches.
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-tu…
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 now tree shakes destructured dynamic imports the same way it does static imports.
𝚌𝚘𝚗𝚜𝚝 { 𝚌𝚊𝚝 } = 𝚊𝚠𝚊𝚒𝚝 𝚒𝚖𝚙𝚘𝚛𝚝('./𝚕𝚒𝚋')
Unused exports are removed from the bundle.
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-futu…
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.