next-best-practices

Next.js 15+ makes params, searchParams, cookies(), and headers() asynchronous, returning Promises. You must await these APIs in Server Components or route handlers to resolve values correctly and prevent rendering inconsistencies.

Common RSC boundary mistakes include marking client components as async and passing non-serializable props like functions from Server to Client components. Enforcing correct 'use client' and 'use server' directives prevents these violations.

Implementing generateMetadata and OG image generation requires following App Router file conventions and route handler constraints. Adhering to documented metadata patterns ensures correct dynamic rendering and bundling compatibility.

Production-grade routing requires following App Router file conventions for route handlers and deterministic error-handling files. Adhering to server and client directive rules ensures proper runtime selection and bundling compatibility.

No, passing non-serializable props across RSC boundaries violates Next.js App Router rules. You must validate that all data passed from Server to Client components is fully serializable to prevent runtime errors and rendering failures.

Next.js 15 migration breaks async request APIs because params, searchParams, cookies(), and headers() now return Promises. Updating your codebase to await these asynchronous APIs resolves migration errors and restores deterministic behavior.