fix: use upgraded require optional

[balazsorban44]

What:

Having another stab at #1682

Why:

The end goal is to not bundle/require typeorm and nodemailer, if someone doesn't use any of these in their project.

How:

I took require_optional as a base, but published my own version under @balazsorban/require-optional. The difference is that it will use the now seemingly established fields peerDependencies and peerDependenciesMeta, instead of peerOptionalDependencies, which doesn't appear to be anywhere. In fact, googling it will point to one of this repository's issue with mongodb!

Side note, mongodb themselves decided to turn away from peerOptionalDependencies: https://jira.mongodb.org/browse/NODE-2867

Checklist:

• Documentation
• Tests
• Ready to be merged
  

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nextauthjs/next-auth/964cDCS73H27Y5dRF62r8hMmRMXu
✅ Preview: https://next-auth-git-fix-upgraded-require-optional-nextauthjs.vercel.app

[github-actions]

🎉 This PR is included in version 4.0.0-next.4 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[ndom91]

@balazsorban44 Yeah strange, right? I couldn't find peerOptionalDependencies referenced anywhere online really. Not sure where that originated from haha.

Anyway, is your require-optional fork doing the trick?

[balazsorban44]

peerOptionalDependencies comes from the require_optional package. It was written BEFORE peerDependenciesMeta was a thing. And no, unfortunately my solution did not work. Searching for peerDependenciesMeta up in the node_modules tree stopped looking for nodemailer in my next's package.json.. 😵 I start to think that the best option is to drop the database config, asking the user to explicitly choose a adapter, and use the form next-auth/providers/your-provider for importing built-in providers. (wrote about this here as well: #1682 (comment)). These two things would mean that we don't need any additional package for requiring optionally. Having imports like this would make it explicit and opt-in which packages you will have to use. I could use your help @ndom91 with testing.