feat(next): allow unstable_getServerSession in Server Components

[balazsorban44]

Next.js 13 shipped with the new app/ directory that implements React Server Components. With the recently introduced change of allowing async/await directly, there is a need for accessing the session in server components in a clean way.

With this PR, unstable_getServerSession will now work in Server Components as well:

// app/page.tsx
import { unstable_getServerSession } from "next-auth/next"
import { authOptions } from "pages/api/auth/[...nextauth]"

export default async function Page() {
  const session = await unstable_getServerSession(authOptions)
  return <pre>{JSON.stringify(session, null, 2)}</pre>
}

Notes:

1. Currently, the underlying Next.js cookies() method does only provides read access to the request cookies. This means that the expires value is stripped away from session in Server Components. Furthermore, there is a hard expiry on sessions, after which the user will be required to sign in again. (The default expiry is 30 days).

2. Since app/ is experimental in Next.js, we are considering this to be experimental in NextAuth.js so we can iterate on the implementation if upstream changes require it.

Fixes #5647

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated
next-auth	⬜️ Ignored (Inspect)		Nov 6, 2022 at 4:02AM (UTC)

[ThangHuuVu]

🚢

[glenarama]

While this appears to work in dev - i get no session when hosted on Vercel. Is anyone else able to confirm if this is true or perhaps related to my setup?
Fixed as i was writing this :-)

Thanks!