Request data used to be synchronous: cookies() returned the store and params was a plain object. That forces the request to exist before the component starts, so nothing in that render can happen ahead of time.
Next.js 15 changed cookies(), headers(), draftMode(), params (in layouts, pages, route handlers, default.js and image metadata files) and searchParams (in pages) to promises. The 15 release post gives the reason: Next.js wants to prepare as much as possible before a request arrives, so it needs to know when a component waits for the request. Next.js 16 removed the temporary synchronous access.
A promise splits "this component can receive request data" from "this component needs it now":
- A layout or page can pass
paramsorsearchParamsdown without awaiting. Only the child that awaits waits. - With Cache Components, everything outside the
<Suspense>boundary around thatawaitis prerendered into the static shell, and only the awaiting subtree streams per request. - Without Cache Components, the
awaitis what makes the route dynamic: a page that receivessearchParamsbut never awaits it stayed static (○) in 16.4.5.
Server Components use await; a Client Component page reads the same promises with React's use(params).
Legacy: up to 14 these were synchronous; 15 kept synchronous access with warnings; 16.0 removed it.