nextjs

Next.js 16 App Router migration involves updating async route parameters (params, searchParams, cookies, headers), adopting cache components with the 'use cache' directive, and migrating API routes to proxy.ts. This Skill provides step-by-step patterns for each phase, including TypeScript configuration and Turbopack setup.

Server Components render on the server, reducing client bundle size and enabling direct database access. Server Actions are async functions that run server-side and can be called from Client Components. Next.js 16 App Router integrates both with improved caching APIs (revalidateTag, updateTag, refresh) for production performance.

Parallel routes in Next.js allow simultaneous rendering of multiple segments within the same layout. Use default.js files to define fallback UI for unmatched routes. This Skill covers production patterns for structuring layouts, managing route state, and optimizing load behavior across parallel segments.

Yes. Proxy.ts is the recommended approach for API route migration in Next.js 16, replacing traditional pages/api routes. This Skill provides adoption patterns, configuration examples, and integration guidance with route handlers to establish production-ready API layers.

Next.js 16 introduces cache components and updated revalidation APIs: revalidateTag invalidates specific tags, updateTag refreshes cached content, and refresh forces revalidation. This Skill demonstrates production patterns for combining these APIs with Server Components to manage data freshness at scale.

Yes. Next.js 16 integrates React 19.2 within App Router, enabling advanced patterns for Server Components, concurrent rendering, and async operations. This Skill covers integration patterns, compatibility considerations, and optimization techniques across Turbopack and deployment platforms.