Error to try reinstalling on Next 16

[OkitegamiKyoko]

Checklist

• The issue can be reproduced in the nextjs-auth0 sample app (or N/A).
• I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

I had a problem with another dependency, so I deleted the directory node_modules and executed:

npm i

And just receive this message:

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @auth0/nextjs-auth0@4.11.1
npm error Found: next@16.0.1
npm error node_modules/next
npm error   next@"16.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer next@"^14.2.25 || ^15.2.3" from @auth0/nextjs-auth0@4.11.1
npm error node_modules/@auth0/nextjs-auth0
npm error   @auth0/nextjs-auth0@"4.11.1" from the root project
npm error
npm error Conflicting peer dependency: next@15.5.6
npm error node_modules/next
npm error   peer next@"^14.2.25 || ^15.2.3" from @auth0/nextjs-auth0@4.11.1
npm error   node_modules/@auth0/nextjs-auth0
npm error     @auth0/nextjs-auth0@"4.11.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

Reproduction

1. Delete node_modules directory.
2. Execute npm i

Additional context

I see a message about this error when migrating from Next15, but I now receive this message always when I reinstall my project on a clean installation

nextjs-auth0 version

4.11.0

Next.js version

16.0.1

Node.js version

24.11.0

[matthew-gladman-oua]

Next 16 isn't officially supported yet, more info:

• Next.js 16 support #2375

---

If you want to workaround this issue, you can add this to package.json:

"overrides": {
  "@auth0/nextjs-auth0": {
    "next": "16.0.0"
  }
}

But you're mileage may vary

[OkitegamiKyoko]

Thank you for taking the time to ask me.

I was using --force in an update branch for a workaround this, but i'll take your solution, becaouse --fore is insecure and --legacy-peer-deps breaked another dependencies.

Again, thank you for your support, and I hope that this Issue helps someone.

[tusharpandey13]

Hi 👋
A PR is open to add support of Next 16: #2405
Till that is released, @matthew-gladman-oua's suggestion should be good to work with.
Closing this for now, ping me here if any other queries and we'll re-open this issue again.