Next.js 16

Next.js 16 introduces breaking changes including async request APIs, proxy.ts replacement, cacheLife requirement updates, and image config modifications. Review the migration guide to identify deprecated patterns in your codebase and plan updates to maintain compatibility.

Server actions in Next.js 16 support Zod-based input validation and ActionState-based return types for typed handlers. Define your action with Zod schemas, handle validation errors centrally, and return structured state to enable client-side error handling and type safety.

The 'use cache' directive enables per-component caching with cacheLife profiles in Next.js 16's App Router. Apply it at the component level to define cache duration, then use tag-based or path-based revalidation to invalidate stale data when needed.

Migration to Next.js 16 is gradual—adopt new patterns incrementally while removing deprecated APIs like proxy.ts and updating image config. Focus on App Router alignment, server-action patterns, and caching strategies; existing routes can coexist during the transition.

Combine tag-based revalidation for content updates and path-based revalidation for route-specific data. Use cacheLife profiles to set default durations, apply 'use cache' at the component level for granular control, and centralize revalidation logic for maintainability.

Next.js 16 deprecates proxy.ts; migrate to proxy-based middleware using the updated middleware APIs. Define routing and request transformation logic in middleware.ts, then reference it in next.config.js for unified request handling across your app.