Installation/compatibility issue: NextAuth with Next.js 16

[rezwana-karim]

Environment

System:
  OS: Windows 11
Binaries:
  Node: 22.17.0
  npm: 11.6.2

Packages:
  next: 16.0.0
  react: 19.0.0
  next-auth: 4.24.11 or 5.0.0

Reproduction URL

https://github.com/syed-reza98/StormCom

Describe the issue

When installing NextAuth (next-auth@4.24.11 or 5.0.0) in a project using Next.js 16.0.0, npm reports a peer dependency error:

Could not resolve dependency:
peer next@"^12.2.5 || ^13 || ^14 || ^15" from next-auth@4.24.11

This blocks installation unless using --legacy-peer-deps or --force. The documentation is unclear whether NextAuth v5+ is intended to support Next.js 16 out of the box. Please clarify:

• Is Next.js 16 officially supported (and from which next-auth release)?
• Does NextAuth v5 peerDependency range need to be updated for Next.js 16?
• Are there any new migration or configuration steps specific to Next.js 16?

Steps taken:

• Tried both next-auth v4 and v5
• Encountered peer dependency error on install
• Checked migration docs, could not find explicit Next.js 16 guidance

How to reproduce

1. Create a new Next.js 16.0.0 project
2. Run npm install next-auth
3. Observe dependency conflict error
4. Try with latest next-auth@beta/v5, same result

Expected behavior

• next-auth should install cleanly with Next.js 16
• Documentation should clearly state support for Next.js 16 and any required migration steps

[NK3678]

Please fix this, as i am facing a issue too

[snowday365]

Please fix this, as i am facing a issue too

[ajatprabha]

A quick workaround I'm using until this gets addressed:

package.json

{
  "name": "***",
  "dependencies": {
    "next": "16.0.0",
    "next-auth": "^4.24.11",
    "react": "19.2.0",
    ...
  },
  "devDependencies": {},
  "overrides": {
    "next-auth": {
      "next": "16.0.0"
    }
  }
}

[NK3678]

Hi @ajatprabha , what about the middleware, as middleware.ts is not supported anymore?

[ajatprabha]

Hi @ajatprabha , what about the middleware, as middleware.ts is not supported anymore?

I followed this doc: Renaming Middleware to Proxy, everything is working as expected.

[edi]

@ajatprabha Can you show us how you implemented it? I used to have a simple file called middleware.ts with the following line export {default} from 'next-auth/middleware' however ... even if i rename it to proxy.ts the warning persists.

Later edit: I managed to fix it by renaming the default export to proxy instead as follows:

export {default as proxy} from 'next-auth/middleware'

[NK3678]

When officially fixed in next-auth v4 ?

[MaxdeoxiS]

Also facing this, blocking me from upgrading to next 16

[nictou-weglot]

Hello, I would also like to upgrade to next 16 but blocked too, using 5.0.0-beta.29

[t-bowden-fas]

Looks like there's a new beta available which is marked as compatible; npm i next-auth@5.0.0-beta.30

[14metehan53]

I encountered the same error yesterday. I installed Next JS 16. I hope it will be resolved as soon as possible.