-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
@auth/drizzle-adapter incompatibility - linkAccount #8283
Comments
I outline the issue here, if anyone wants to fix: #8280 (comment) |
I released a fix in It's included in @auth/core@0.10.4 If that doesn't work, you can check your package manager's override config, eg. for pnpm adding the following to your "pnpm": {
"overrides": {
"@auth/core": "^0.10.4"
}
} |
Hello, I'm still experiencing this problem even after installing latest version of auth/core. Attempted doing what you mentioned above with no luck. I'm implementing a custom adapter where I have imported the types from @auth/adapters. I receive typescript errors when I pass the custom adapter via NextAuthOptions. same errors as above with some others I really wish next-auth would export their adapter types that would make all of this much easier.
Edit: I was able to side step the type error by defining the type of Edit 2: @balazsorban44 just saw your comment on this issue so sorry for the extra noise #8280 (comment) |
If you are importing types from Here is the explanation #8294 |
Fixed via 20c3fe3, will release later. 馃檹 |
Question 馃挰
While using the latest version of next-auth (4.22.5) and @auth/drizzle-adapter (0.2.1), the following error occurred in the NextAuthOptions:
Types of property 'linkAccount' are incompatible.
I've set up the minimum required adapter in Postgres according to the documentation.
Here is my code:
Any idea how to resolve this issue?
Thanks in advance!
How to reproduce 鈽曪笍
Follow the documentation for setting up the drizzle adapter with Postgres: https://authjs.dev/reference/adapter/drizzle#drizzleadapter
Contributing 馃檶馃徑
Yes, I am willing to help answer this question in a PR
The text was updated successfully, but these errors were encountered: