[auth-nextjs] Async Request APIs, compat with Next.js 15

[MartinCura]

This PR adapts the @edgedb/auth-nextjs package for the [kinda*] breaking change of Next.js 15, where Request APIs like cookies and params are now async.

To solve this, i simply added await to all corresponding places. Awaiting something sync is not strictly a noop, but for these cases it shouldn't change behavior afaict.

Tested in my own project with both Next.js before their breaking change and after it.

Breaking change: As NextAppAuth.getSession() has to await cookies(), it is now an async function, which means those upgrading have to add await when calling it.

const auth = createAuth(client, {
  baseUrl: `http://localhost:${process.env.PORT || 3000}`,
  authCookieName: "edgedb-session",
  pkceVerifierCookieName: "edgedb-pkce-verifier",
})

export const getCurrentUser = async () => {
- const session = auth.getSession()
+ const session = await auth.getSession()
  const userQuery = e.select(e.User, () => ({
    ...e.User["*"],
    filter_single: { id: e.global.current_user.id },
  }))
  return await userQuery.run(session.client)
}

This necessitates that getSession is now async, which is a breaking change, because it accesses the cookies.

*kinda because as a compatibility layer it is still possible to not await it, but it's not what you want to do.

[edgedb-cla]

All commit authors signed the Contributor License Agreement.

[1st1]

Thank you, we'll take a look soon!

[scotttrinh]

Thanks so much for taking on this mechanical work! It's been on our "next up" list for a few weeks now.

[scotttrinh]

Will this work in <15 or will those users need to do a type-cast?

[MartinCura]

Good question. In runtime it shouldn't be a problem because it would just be awaiting a non-Promise; and i didn't notice any type error when i tried it in <15, but i can check again jic.

[scotttrinh]

Yeah, I'm not worried too much about runtime, and even if it breaks backwards compatibility, I'm fine with shipping it, I just want to understand everything that might break here so we can update the docs.

[MartinCura]

Well the GET is exported in a route.ts to act as a Next.js Route Handler but it's not type checked against anything. I can run and build the project running Next.js before their breaking change with this version, no errors. And i don't know of any way that someone could be type-checking this and get a warning/error after this change.

At most we could add a small note to the docs referencing the change introduced by Next.js 15 and how this small library targets the new behaviour but supports both.

[MartinCura]

Thanks so much for taking on this mechanical work! It's been on our "next up" list for a few weeks now.

No worries! Glad to help and love what you guys are doing. I'm working on a sizable project by myself, so these kinds of helper libraries that help me ship faster are very welcome.

And i'm sure you're quite busy with EdgeDB Gel 6!

[MartinCura]

👋🏼 Small update: React 19 stable finally dropped, and with it a stable release of @types/react, so the overrides i added in this PR should not be needed anymore if you just point to the new version.