- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with @sidebase/nuxt-auth and next-auth: next-auth/core Import Fails + Runtime Error #953
Comments
Hi @PawelRod, you don't need to set any aliases to get Please, check the output using
|
Hi @phoenix-ru, Thank you for your help. Delete aliases from nuxt.config.ts, installing the packages using pnpm and adjusting the imports for NuxtAuthHandler resolved the previous issue. However, I am now encountering a new error:
It seems there is an issue with Vue app aliases being used in the server runtime. Could you advise on the correct way to resolve this? I tried to set openAPI to true/false and nuxi force update, but it also not working:
|
Hi again @PawelRod , nice to know that the initial issue was solved. Regarding the issue you are facing, it doesn't appear to be related to our module, but probably because of your setup, see nuxt/nuxt#14869 or nuxt-modules/i18n#3111 for a similar issue. We haven't yet encountered it on any of our projects, so you may try downgrading Nuxt or NuxtAuth to see if that solves the issue. I have a feeling it is related to one of the other modules you are installing |
Environment
Reproduction
npm install @sidebase/nuxt-auth@0.9.4 next-auth@4.21.1
npm run dev
Describe the bug
When using @sidebase/nuxt-auth with next-auth, the following issues arise:
These errors persist across various configurations and attempts to resolve the next-auth/core module.
Additional context
• I have tried multiple versions of next-auth (e.g., 4.21.1, 4.24.10) and the issue persists.
• Alias for next-auth/core → next-auth was added in vite.resolve.alias.
• Ensured all environment variables for Auth0 are set correctly:
Request for Assistance
Logs
The text was updated successfully, but these errors were encountered: