ππππππ-πππ‘π-πππ 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.
@ππππππ/πππ‘π-ππππ πππ lets agents inspect a running Next.js app from the terminal. Component trees, PPR shells, screenshots, network requests.
Agents can lower Suspense allowing more cached content to be included in the static prerender.
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
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-tuβ¦
The error overlay now displays up to five levels of π΄ππππ.πππππ chains, making it easier to trace errors that wrap other errors.
The default production error page has been redesigned.
If you haven't defined a custom πππππ.πππ‘ or ππππππ-πππππ.πππ‘, the built-in fallback now has a cleaner, more modern look.
Server Function calls are now logged in the terminal during πππ‘π πππ.
You'll see the function name, arguments, execution time, and source file.
We contributed a change to React that makes Server Components payload deserialization up to ~350% faster.
In real Next.js apps, that's 25β60% faster rendering to HTML.
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.