#app-router

Why Next.js 16 throws this error at build time, where the Suspense boundary actually has to go, and the two common fixes that quietly make things worse.

App Router file-based conventions that make Next.js predictable for humans also make it easy for AI agents to navigate. Here is why that is not a coincidence.

Lessons from building a real Next.js 16 app — async searchParams, MDX rendering, generateStaticParams, and the Server Component patterns I reach for.