-
-
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
_interopRequireDefault2 is not a function #945
Comments
Could you please share which version of |
@phoenix-ru it's 4.21.1
I did like in documentation says |
I got this trouble, when updated nuxt version to latest. |
Thank you for sharing. I noticed you have a "lousy" specifier "next-auth": "4.21.1" and rerun the install. It should work if the version is correct. To check the correctness, run
You should see the same If you use a correct version and the issue still persists, please share if you're using |
@phoenix-ru unfortunately, this not work me. I tried set next-auth to 4.21.1 and I have same problem. For now my package.json
When I use npm why next-auth I have next message:
I am using vite for my project. |
any updates? |
Hi @bobrov-site 👋 I have not tested NuxtAuth with Nuxt version 3.14 yet. As there were some big breaking changes in 3.13 it would be related to this. We are still working on resolving the issues that occured when upgrading to 3.13 in this PR: #942 Could you do me the favour of installing this version of NuxtAuth built from the PR mentoned above and checking if this resolves the issue?
|
@zoey-kaiser i will try soon your instructions. Thanks for replaying! |
@zoey-kaiser i use npm and follow your command. This is not work for me. Now my package.json looks now:
|
Hi @bobrov-site, thats too bad 😢 Do you think you could create a minimal reproduction of the issue please? Without it I fear it will be hard for us to investigate the issue futhur. |
Hello 👋 Please provide a reproduction for this issue 🙏 How can I create a reproduction?Please use one of the following links to reproduce your issue.
Please ensure that the reproduction is as minimal as possible. This will allow us to isolate the issue as best as possible. Here are some more amazing posts about the importance of reproductions: |
@zoey-kaiser i tried to create reproduction. https://stackblitz.com/edit/github-adkgbz7q?file=server%2Fapi%2Fauth%2F%5B...%5D.ts . In this case it's seems like okay. But in my original project, I have mongo db and I have auth logic there. I cannot share to public with my project because inside I have secret data. How can we resolve this problem? |
@bobrov-site You don't really need to share your data or application to reproduce. What is the output of the following command? npm ls next-auth On the reproduction you created it correctly returns
Do you still get this problem if you install for example |
@phoenix-ru I have same data for npm ls next-auth, that you share
I still have problem, even installed @sidebase/nuxt-auth@next |
Environment
Darwin
v20.11.0
3.14.159
3.15.0
2.10.4
[email protected]
-
default
@nuxt/[email protected]
,vue-yandex-maps/nuxt
,[email protected]
,@pinia/[email protected]
,[email protected]
,@sidebase/[email protected]
,@nuxt/test-utils/[email protected]
,[email protected]
,@nuxtjs/[email protected]
,@nuxtjs/[email protected]
-
Reproduction
my [...].ts file
nuxt.config.ts
Describe the bug
I have this an error
next-auth_react.js?v=ff837320:4048 Uncaught TypeError: _interopRequireDefault2 is not a function
at node_modules/next-auth/react/index.js (next-auth_react.js?v=ff837320:4048:24)
at __require (chunk-V4OQ3NZ2.js?v=ff837320:11:50)
at next-auth_react.js?v=ff837320:4628:16
Additional context
When I run my nuxt application via npm run dev, I have this problem. But in production building I don't have it.
Logs
No response
The text was updated successfully, but these errors were encountered: