next-best-practices

To detect invalid RSC patterns, validate that Client Components are not async and ensure non-serializable props are not passed to Client Components. Checking directive usage prevents Server/Client boundary violations and serialization errors in your Next.js App Router application.

Handling async params and searchParams in Next.js 15 requires awaiting these request APIs before accessing their values. Validating modern async API usage ensures correct data fetching, directive-aware caching, and prevents runtime errors in App Router route handlers and pages.

Setting up parallel and intercepting routes for modals in Next.js involves using specific App Router file conventions to intercept navigation and render parallel route segments. Correct Suspense boundary placement manages loading states and prevents hydration mismatches during modal workflows.

Next.js App Router requires Suspense boundaries to manage loading states and prevent hydration mismatches during streaming. Wrapping dynamic content in Suspense components ensures reliable client-side hydration and correct fallback rendering for asynchronous server components.

Passing non-serializable props to Client Components in Next.js is limited by RSC serialization constraints, causing runtime errors when functions or class instances cross the boundary. Detecting non-serializable props prevents these violations and maintains Server Component integrity.

Validating Next.js route handlers and metadata OG image generation requires checking specific file conventions and runtime selection. Correct directive usage and modern metadata patterns ensure proper dynamic OG image generation and reliable route handler execution in App Router.