feat: Handle splitted next-auth.session-token cookie

[jals1212]

🔗 Linked issue

#139 #160

❓ Type of change

• [ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• [x] 🐞 Bug fix (a non-breaking change that fixes an issue)
• [ ] 👌 Enhancement (improving an existing functionality like performance)
• [x] ✨ New feature (a non-breaking change that adds functionality)
• [ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

• Module options fills the runtimeConfig (private and public).
• RuntimeConfig typings updated.
• useAuth's sessionToken returns the cookie handled by makeSessionCookie (handles splitted session token).
• NuxtAuthHandler uses getAuthJsSecret if receives no token from AuthConfig.
• getServerToken uses makeCookiesFromHeaders to manage cookies.
• Added end edited some utils:

1. A - getAuthJsSecret: gets the secret from runtime or env vars.
2. A - getConfigBaseUrl: gets the baseUrl from runtime or env vars.
3. M - checkOrigin: uses getConfigBaseUrl
4. M - getServerOrigin: uses getConfigBaseUrl.
5. A - mergeCookieObject: merges cookies.
6. A - makeSessionCookie: gets the next-auth.session-token (handles splitted session token).
7. A - makeCookiesFromHeaders: manage multiple 'set-cookie' and makes native Headers.
8. M - makeNativeHeaders: made it an utility.
9. M - makeNativeHeadersFromCookieObject: uses makeNativeHeaders.

• Added some tests.

Resolves the 'getServerToken returns null issue'.

#139 #160

📝 Checklist

• [x] I have linked an issue or discussion.
• [ ] I have updated the documentation accordingly.

[AndrewR3K]

@Hebilicious Any progress on this PR? I am having the issue with getServerToken returning Null on the current npm version 😿

Thanks for this wonderful package, I hope to continue to use this.

[Hebilicious]

@Hebilicious Any progress on this PR? I am having the issue with getServerToken returning Null on the current npm version 😿

Thanks for this wonderful package, I hope to continue to use this.

Hello there. The problem is that I don't personally use auth.js anymore and I have no easy way to test if this PR will break existing code ... I'm also no longer maintaining this package, as the auth.js team never moved forward with their plans. Now issues are piling up and I don't have the time, the incentive or the desire to fix them. If someone is willing to test this PR, I would merge it.