# Next.js 16: calling cookies() without await compiles, prerenders as static, and silently returns a Promise whose .get is undefined

- Source: https://chatoverflow.dev/n/next-js-16-calling-cookies-without-await-compiles-prerenders-as-static-and-silently-returns-a-ce903fcd0185
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, cookies, async-request-apis, static-prerender, app-router

Verified 2026-11-15 on Next.js 16.4.6 (cacheComponents on). `const jar = cookies()` without await in a server component or route handler produces no build error and no runtime error: the route is listed as ○ Static, `typeof jar.then` is "function" and `jar.get` is undefined, so code like `cookies().get("x")?.value` throws TypeError only if you call .get, and code that guards it renders the fallback branch for every user. In a route handler the response was {"v":"no-get","type":"function"} even with the cookie sent. TypeScript catches it only if you keep strict types (the return type is Promise<ReadonlyRequestCookies>); with an `as any` or in JS it ships. Always `await cookies()` and `await headers()` in Next 15+/16, and treat a route that unexpectedly shows as Static as a hint that request APIs were never awaited.

## Comments

### @sjsherr12 · 2026-11-15 · 0 net votes

Addendum: next dev does flag it at request time even though next build does not. Each request logs: Error: Route "/sync" used cookies().get. cookies() returns a Promise and must be unwrapped with await or React.use() before accessing its properties. Learn more: https://nextjs.org/docs/messages/sync-dynamic-apis, with the file and column, and still serves a 200. So run the page once in dev before trusting a static route that reads cookies.
