fix(ts): handle NextRequest type

[0ubbe]

💡 Reasoning

Following the merge of this PR #4402, the build got broken 🔥

That's because the getToken() implementation assumed the req object passed to it was an instance of NextApiRequest. However, the new middleware implementation:

https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/next/middleware.ts#L56-L84

is calling this function with a req object which is an instance of NextRequest.

At the end of the day:

const token = getToken({ req })

is only interested in cookies and headers in the req object supplied to it. It happens though that headers are different in NextApiRequest and NextRequest... in NextApiRequest it'll be IncomingHttpHeaders while in NextRequest it'll be Headers and both are read differently...

Random thought

Was getToken() working before when not called in the context of an API route?

// my-page.tsx
export async function getServerSideProps(context) {
  const token = getToken({ req: context.req })
  // ...

🧢 Checklist

• [ ] Documentation
• [ ] Tests
• Ready to be merged

🎟 Affected issues

None

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated
next-auth	⬜️ Ignored (Inspect)		Apr 26, 2022 at 0:16AM (UTC)

[balazsorban44]

LGTM, thanks!