Heb
Did you try the default authorization link fix ?
@namdevel As this is not an issue with authjs-nuxt but with authjs itself, you're gonna have to look for help and changes in authjs itself https://github.com/nextauthjs/next-auth/issues/7764 :/
@namdevel try this https://github.com/nextauthjs/next-auth/discussions/948
> Was there a reason you parsed the cookies yourself instead of using the h3 `parseCookies` function? It wasn't implemented properly in h3 when I created the module, but pretty...
The fix look good, but I need to find the time to test it as we don't have good test coverage set-up.
@ferat Could you give #167 a try ? I believe this will resolve the issue and we'll close this PR.
@ghs thanks for reporting, here's the auth.js relevant option https://authjs.dev/reference/core#cookies (next-auth is different) and the [code.](https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/lib/cookie.ts) I believe nobody should be touching that, but we should try to support it...
I was trying to get this module merged into the official repo to avoid such issues, but from what I understand, Nuxt is not a priority and they're working on...
That's an interesting bug that appears to be Nuxt related. As a workaround, could you use a separated page for your reserved-area instead?
I am not sure why this bug is happening, but as a workaround, you can try to install cookie, and to add this to your package.json : ```ts export default...