next-best-practices

To fix invalid RSC boundaries in Next.js, detect async client components and non-serializable props passed to them. Enforce correct Server Component boundaries by moving async logic to server-only code and ensuring client components remain synchronous.

Next.js App Router file conventions require correct project structure, dynamic segments, and proper route handler placement. Avoid route.ts conflicts by following parallel and intercepting route patterns, and apply middleware to proxy migration guidance for reliable routing.

Next.js hydration errors usually stem from client-server markup mismatches or invalid async API misuse. Debug them by applying prescriptive remediation patterns, checking error.tsx and global-error boundaries, and resolving navigation gotchas that cause rendering inconsistencies.

Optimize Next.js images and fonts by avoiding bundling anti-patterns and applying correct optimization configurations. For self-hosting, ensure proper metadata setup, OG image generation via generateMetadata, and runtime practices that prevent resource loading pitfalls.

Yes, you can use Next.js Server Actions and new async request APIs with Route Handlers by enforcing correct async patterns. Ensure server actions are properly scoped, avoid non-serializable props, and validate data fetching practices to maintain reliable runtime behavior.