You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently next-auth has a dependency on nodemailer:
peerOptional nodemailer@"^6.6.5" from next-auth@4.24.11
nodemailer@7.0.4 is the current version though with 7.0.0 being released two months ago.
Would it be possible to support this version with next-auth too?
Trying to upgrade nodemailer (which is a dependency in our project) results in:
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: next-auth@4.24.11
npm error Found: nodemailer@7.0.4
npm error node_modules/nodemailer
npm error nodemailer@"~7.0.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional nodemailer@"^6.6.5" from next-auth@4.24.11
npm error node_modules/next-auth
npm error next-auth@"~4.24.11" from the root project
npm error
npm error Conflicting peer dependency: nodemailer@6.10.1
npm error node_modules/nodemailer
npm error peerOptional nodemailer@"^6.6.5" from next-auth@4.24.11
npm error node_modules/next-auth
npm error next-auth@"~4.24.11" 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.
Thanks for consideration :)
Proposal
It actually should work out of the box to update the dependency,looking at the changelog from nodemailer but I did not test it.
The breaking change seems to only affect AWS SES.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-Goals
No response
Background
Currently next-auth has a dependency on nodemailer:
nodemailer@7.0.4 is the current version though with 7.0.0 being released two months ago.
Would it be possible to support this version with next-auth too?
Trying to upgrade nodemailer (which is a dependency in our project) results in:
Thanks for consideration :)
Proposal
It actually should work out of the box to update the dependency,looking at the changelog from nodemailer but I did not test it.
The breaking change seems to only affect AWS SES.
Beta Was this translation helpful? Give feedback.
All reactions