Next.js 16.2 for dummies - our thoughts on the latest

Yo Vercel Community,

As always, we just published a breakdown of Next.js 16.2. It’s less of a top level overview and more of what changed, what we measured on our own site, and whether it’s worth the five minutes it takes to upgrade.

  • Dev startup is about 80% faster for us.
  • Server fast refresh is now on by default, no more experimental flag. It only re-executes the module you changed instead of the entire import chain.
  • Rendering got 25-60% faster. React replaced the old JSON.parse reviver with a plain JSON.parse() plus a recursive walk. You get this for free by bumping the version.
  • ImageResponse is 2-20x faster. We use this for OG images on every project, page and blog so that one made us pretty happy. Significantly faster when playing with the OG image generation.
  • Browser log forwarding pipes client-side errors to your terminal. Configure it with logging.browserToTerminal in next.config.ts. This is great, one less step for us having to press the error when it happens and going back to Claude Code. It can literally auto-solve problems.
  • transitionTypes on Link is a new stable prop for per-link view transition control. This is just really cool. We’ve got to find a way to shoe-horn this somewhere.

We upgraded both our Next.js apps in about five minutes. No breaking changes, no config updates. Build times were the same (our site was already fast after the 16.0 Turbopack migration), but the dev experience is
noticeably better. You feel it every time you save a file.

Full post has benchmarks, a comparison table, and code examples. Curious how the upgrade goes for anyone running larger apps.

1 Like

TL;DR: it’s faster, dev server go brrr, go upgrade

1 Like

This looks like a solid iteration on Next.js Jonoroboto. The Fast Refresh change (module-level re-execution) is probably the most impactful here, aslo reducing unnecessary invalidation across the import graph has a real effect on dev feedback loops. Curious how consistent these gains are at scale and how this holds up on larger apps though?? especially with Turbopack already in place.

But overall, seems like one of those low-risk, high-impact upgrades :rocket: