migrating-async-request-apis

Migrate Next.js request APIs to async by updating params, searchParams, cookies(), headers(), and draftMode() to be awaited in your server components and route handlers. Next.js 16 changed these APIs to return Promises, requiring you to await them and update TypeScript types accordingly to reflect Promise-based returns.

Type errors occur because Next.js 16 made request APIs async. Your code is likely treating params, searchParams, cookies(), headers(), and draftMode() as synchronous values when they now return Promises. Add await keywords and update type annotations to Promise wrappers to resolve these errors.

Yes. In Next.js 16, params and searchParams are Promise-based and must be awaited in pages, layouts, and route handlers. This applies whether you're accessing route parameters or query strings; update your function signatures and component code to handle async values.

In route handlers, call cookies() and headers() but await them since they now return Promises in Next.js 16. Update your code to use await before accessing their methods, and refactor any synchronous patterns to work with async/await or Promise-based flows.

draftMode() is now async in Next.js 16. Await the draftMode() call before accessing its properties, and update your TypeScript types to reflect that it returns a Promise, particularly in server components and middleware.

Phase the migration by updating one API type at a time—start with params, then searchParams, then cookies(), headers(), and draftMode(). This staged approach reduces the scope of type changes and testing, making it easier to identify issues and ensures each layer of your app adapts systematically.