nextjs

Next.js 16 App Router migration involves updating async route parameters (params, searchParams, cookies, headers), replacing middleware.ts with proxy.ts, and adopting Cache Components with use cache. This Skill provides production-ready patterns and step-by-step guidance to migrate cleanly across Vercel, AWS, self-hosted, and Cloudflare Workers environments while minimizing breaking changes.

Server Components fetch data and render on the server, reducing client bundle size; Server Actions handle form submissions and mutations server-side. Next.js 16 App Router uses these patterns by default for streaming, progressive enhancement, and secure client-server communication without manual API routes.

Next.js 16 caching uses revalidateTag with two arguments, updateTag, and refresh directives, plus Cache Components with use cache. These APIs reduce server load and improve performance by controlling data revalidation granularly across Server Components and Route Handlers in production.

Yes, Next.js 16 App Router supports parallel routes for rendering multiple segments simultaneously. Parallel routes require default.js files and work with layouts, loading states, and error boundaries to organize complex routing structures efficiently.

proxy.ts is the Next.js 16 replacement for middleware.ts, offering improved request interception and routing logic. This migration addresses breaking changes and aligns with modern App Router patterns for cleaner middleware handling across environments.

Yes, Next.js 16 integrates React 19.2 and Turbopack for faster builds and improved development experience. This Skill covers Turbopack defaults, TypeScript configuration, and modern React patterns to accelerate your migration.