Fixing 'useSearchParams() should be wrapped in a suspense boundary' in Next.js 16
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.
Tag
6 posts
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.
React Compiler auto-memoizes at build time and is one of 2026's most-discussed shifts. What it does, and the specific reason this site hasn't adopted it yet.
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.
How I decide between simple and scalable architecture early in a project — file-based content, CMS-ready layers, and when to actually add complexity.
How I architected a developer platform on Next.js 16, Tailwind v4 and a file-based content layer — the decisions that held up, and the ones that cost me hours.
Lessons from building a real Next.js 16 app — async searchParams, MDX rendering, generateStaticParams, and the Server Component patterns I reach for.