UndieGravity LogoUndiegravity

Next.js 16: What Changed and How to Upgrade

Next.js 16 makes Turbopack the default, renames middleware to proxy, requires async request APIs, and changes caching. Here is what to update first.

By UndieGravity, , 2 min read

Next.js 16 is a release you notice on day one: builds use a new bundler by default, a familiar file has a new name, and a few APIs that were synchronous are now async. This guide lists the changes that affect most projects and the order to fix them in.

Turbopack is the default bundler

next dev and next build now use Turbopack without any flag. Most projects get faster local reloads and builds with no changes. If your project has a custom webpack function in next.config, next build stops with an error instead of silently ignoring it.

  • Move the config to Turbopack options (for example turbopack.resolveAlias) when possible.
  • Run next build --webpack to keep Webpack while you migrate.
  • Drop the old --turbopack flag from your scripts; it is no longer needed.

middleware.ts is now proxy.ts

The middleware file convention is deprecated and renamed to proxy, and the exported function should be called proxy too. The proxy runs on the Node.js runtime. If you depend on the edge runtime, you can keep middleware for now.

mv middleware.ts proxy.ts
export function proxy(request: Request) {
  // same logic as before
}

Request APIs are async

params, searchParams, cookies(), headers(), and draftMode() must be awaited. Next.js 15 allowed synchronous access with a warning; Next.js 16 removes it.

export default async function Page({ params }: PageProps<"/blog/[slug]">) {
  const { slug } = await params;
  return <h1>{slug}</h1>;
}

Run npx next typegen to generate the global PageProps and LayoutProps helpers, which type params from your real routes.

Caching changes

  • revalidateTag now takes a second argument with a cache profile, for example revalidateTag("posts", "max"). The one-argument form is deprecated.
  • updateTag is new: use it in Server Actions when a user must see their own change immediately.
  • Partial Prerendering is enabled with the cacheComponents option, which replaces the old experimental flags.

next/image defaults

The priority prop is deprecated in favor of preload, the default qualities list is now [75], and the default minimumCacheTTL is longer. Images that load local files with query strings need an explicit localPatterns entry.

React 19.2 and removals

Next.js 16 ships with React 19.2, so <Activity> and useEffectEvent are available. AMP support and the next lint command are removed: run ESLint directly with a flat config instead.

A safe upgrade order

  1. Run the official codemod: npx @next/codemod@canary upgrade latest.
  2. Fix async params and searchParams errors reported by tsc.
  3. Rename middleware.ts to proxy.ts.
  4. Run next build and resolve any Webpack config errors.
  5. Click through your main pages and check images, redirects, and forms.

Starting a new project instead? Each template page lists its exact Next.js version, so you can pick one that already matches. Browse the templates catalog.

Keep reading