feat: Add ability to customize client-side fetch calls

willwill96 commented 1 week ago

☕️ Reasoning

Currently, if you have your next-auth SessionProvider is configured to point to a separate domain from the next.js app, next-auth related cookies will not be sent in your requests. In order to send cookies on cross-origin request, you have to use { credentials: 'include' } when you make your fetch request. This approach allows users to pass custom fetch options that will be passed to the underlying fetch calls.

🧢 Checklist

[ ] Documentation
[ ] Tests - I'm having trouble running tests locally, I guess I'm missing some env vars needed for local but I'm not sure what they all are.
[ ] Ready to be merged

🎫 Affected issues

(These are discussions, not issues):

Fixes: https://github.com/nextauthjs/next-auth/discussions/12203 Fixes: https://github.com/nextauthjs/next-auth/discussions/8799

📌 Resources

vercel[bot] commented 1 week ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
auth-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 9, 2024 2:48am

1 Skipped Deployment

vercel[bot] commented 1 week ago

@willwill96 is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

nextauthjs / next-auth