Outdated peerDependencies

[aaronfulkerson]

Describe the bug
Installing the package using NPM v7 causes installation to fail unless the --force flag is used.

Steps to reproduce
Create a new Next.js project and attempt to install next-auth.

Expected behavior
No

Screenshots or error logs

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: project@0.1.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"17.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.13.1" from next-auth@3.1.0
npm ERR! node_modules/next-auth
npm ERR!   next-auth@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Additional context
Add any other context about the problem here.

Feedback
Documentation refers to searching through online documentation, code comments and issue history. The example project refers to next-auth-example.

• Found the documentation helpful
• Found documentation but was incomplete
• Could not find relevant documentation
• Found the example project helpful
• Did not find the example project helpful

[balazsorban44]

Thank you! This looks legit. Our canary branch lists react 17 as a possible peer dependency version. We hope to release it to npm this month.

[foaadnami]

related to 814 819

[balazsorban44]

This was released yesterday! You can install it with npm i next-auth@canary