Use in App router with authOptions obj

[aychernov]

How to use SteamProvider without req?

I`m use something like this structure:

import NextAuth from "next-auth"
import {authOptions} from "@/lib/auth";

const handler = NextAuth(authOptions)

export {handler as GET, handler as POST}

And my authOptions:

export const authOptions: NextAuthOptions = {
    pages: {
        signIn: '/sign-in',
    },
    providers: [
        SteamProvider(req? ,{
            clientId: ...!,
            callbackUrl: ...!
        }),
}

Where i`m getting error about req and callbackUrl not found and define Some solutions or advice?

[Nekonyx]

Hey, there's an example: https://github.com/Nekonyx/next-auth-steam/blob/956b70425be5cc3f395d91e4ee3f9952faecc7e4/examples/get-server-session/pages/api/auth/%5B...nextauth%5D.ts#L14

[danfmn]

Hey, there's an example:

https://github.com/Nekonyx/next-auth-steam/blob/956b70425be5cc3f395d91e4ee3f9952faecc7e4/examples/get-server-session/pages/api/auth/%5B...nextauth%5D.ts#L14

I'm looking to support the new routing here and I think that's what @aychernov is referring to as well? Do you have an example with this new structure? https://nextjs.org/docs/app/building-your-application/upgrading/app-router-migration#accessing-request-object

[jhammond2012]

I am getting the same

I am guessing that I should downgrade next for now?

[Nekonyx]

Nope, you can type // @ts-expect-error for now. It seems Next.js or next-auth made some breaking changes in their API. Gonna take a look ASAP.

[Nekonyx]

Fixed