View Transitions just got simpler with Next.js 16.2.
<π»πππ> now has a ππππππππππππ’πππ prop. Tag your navigation with a type, and <π πππ ππππππππππ> picks the right animation.
Adapters are now stable!
A typed versioned description of the built Next.js application that platforms can use to deploy Next.js.
We've also published how to run the Next.js test suite for platforms, allowing platforms teams to continuously run the latest Next.js test suite.
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
https://t.co/t9i9gl5UdS
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
https://t.co/ZCguYywhVV
@jantimon@aurorascharff Hey @jantimon! `unstable_catchError()` does work in Pages Router! Would love to hear your feedback on it.
One thing to note is that `unstable_retry()` is unavailable, which depends on the App Router `router.refresh()` under the hood.
https://t.co/SURkX1dUJn
πππππ-πππππ-ππππππππ’ is great for declarative error handling, but it breaks with Server Components: it swallows ππππ΅ππππ() and ππππππππ(), and πππππ() can't re-fetch server data.
Next.js 16.2 ππππππ΄ππππ: framework-aware, πππππ’() re-fetches RSC data, and internal errors propagate correctly.
Blog post + demo in the thread β
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.
can tap the screen to call dog over to you faster
- dog has base speed (similar to irl)
- each tap gives +1pts speed, exponentially decaying with each successive tap
- speed decays over time (dog gets tired)
- speed resets when reaching cursor
one week ago we announced the redesign of the Vercel dashboard, and since then weβve been busy addressing your feedback
here are several things weβve changedβ¦