Question 1

What are the biggest changes in Next.js 16 beta?

Accepted Answer

The headline features are Turbopack stability (dev + production), built-in React Compiler support, a major routing/navigation overhaul, and new caching APIs. I also cover Build Adapters, Cache Components with PPR changes, and React 19.2 (canary) integration. It’s a version that’s clearly pushing Next.js toward faster builds and more explicit caching control.

Question 2

Is Turbopack stable in Next.js 16 and should I switch from Webpack?

Accepted Answer

Yes—Turbopack is now stable for both development and production builds, and it becomes the default bundler. You can still opt into Webpack with a flag if you need it. The point is you get speed (2–5x faster prod builds, up to 10x faster Fast Refresh) without needing extra config.

Question 3

How do the new caching APIs work in Next.js 16 (revalidateTag, updateTag, refresh)?

Accepted Answer

I explain them as three different tools with very different intent. revalidateTag is like stale-while-revalidate for tagged cache—serve old content instantly and refresh quietly in the background, but now you must pass a cache profile (max is the recommended default). updateTag is server actions only and gives you immediate “read-your-writes” behavior by expiring and refreshing cache within the same request, while refresh is for uncached data only and doesn’t touch the cache at all.

Question 4

What is updateTag in Next.js 16 and why is it a game changer?

Accepted Answer

updateTag is a new server-actions-only API that expires and refreshes cache immediately, so users see their changes right away. This solved a real problem on my course platform: when a student marks a lesson as completed, I want the tick to show instantly and then route them forward. I can combine that with Next.js after() to run heavier work in the background while navigation stays snappy.

Question 5

What changed with revalidateTag in Next.js 16?

Accepted Answer

The main breaking change is that revalidateTag now requires a cache profile. That profile tells Next.js how long the tag should be cached, when to revalidate, and when it expires. For most apps, the recommended default is max, but you can choose more granular behavior for dashboards, listings, or analytics-style pages.

Question 6

What are Build Adapters in Next.js 16 and who are they for?

Accepted Answer

Build Adapters let you hook into the build process so you can deploy Next.js on your own infrastructure and customize build steps. Think Cloudflare Workers, transforming output, uploading assets to S3—those kinds of workflows. It’s basically a plug-and-play deployment adapter model so you’re not tied to one provider.

Question 7

What routing and prefetching improvements landed in Next.js 16?

Accepted Answer

Next.js 16 overhauls routing and navigation to make transitions more linear and faster. Layout deduplication means shared layouts are downloaded once instead of repeatedly when you prefetch many links (huge for pages with lots of links). Incremental prefetching fetches only what’s missing from cache, cancels requests when links leave the viewport, and prioritizes hover/viewport—more requests sometimes, but lower total transfer size.

Question 8

What are the breaking changes to watch out for when upgrading to Next.js 16?

Accepted Answer

You need to account for minimum Node and TypeScript changes (TypeScript 5+ is required). If you use revalidateTag, you must add the cache profile parameter now. Also, the middleware file has been renamed to proxy, and the old experimental PPR flag is evolving into Cache Components, so you’ll need to update your config accordingly.

Next.js 16 Just Changed Everything (Again)

🛍️ Products Mentioned (6)

Ready to go deeper? Build & deploy 7+ production apps from scratch

Join Frontend Snacks — my free weekly newsletter

my FREE Goodies (cheatsheets, templates & more)

Free Next.js Hot Tips Course

Opened a few coaching calls, grab them before they are gone

use-cache blog post

About This Video

Frequently Asked Questions

🎬 More from Ankita Kulkarni