nextjs-16

Migrating to Next.js 16 requires adopting async params in the app router to avoid breaking changes. The skill provides migration strategies and examples to guide teams smoothly through upgrading from Next.js 15 and implementing the correct patterns.

Next.js 16 app router conventions include async params, proxy.ts, and default.js for parallel routes. The skill guides developers in adopting these updated conventions and outlines top-level configuration changes like cacheComponents to ensure projects follow best practices.

Yes, Next.js 16 introduces Turbopack defaults that require top-level configuration changes. The skill explains how to implement these Turbopack configurations alongside cacheComponents to ensure your project adheres to the new framework standards.

Setting up parallel routes in Next.js 16 requires using default.js to avoid rendering errors. The skill guides developers through implementing this app router pattern correctly, providing examples for both new projects and existing migrations.

Starting a new Next.js 16 project involves enabling cacheComponents and using Turbopack defaults. The skill provides migration-focused guidance and examples for initializing projects with these best practices to avoid common pitfalls from the beginning.

Upgrading to Next.js 16 causes proxy.ts errors if the new conventions are not adopted correctly. The skill guides developers through implementing proxy.ts and other app router patterns to avoid these common migration pitfalls.