-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
feat: introduce @auth/typeorm-adapter
#7706
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
New dependency changes detected. Learn more about Socket for GitHub ↗︎ 👍 No new dependency issues detected in pull request Bot CommandsTo ignore an alert, reply with a comment starting with Pull request alert summary
📊 Modified Dependency Overview: 🚮 Removed packages: @next-auth/typeorm-legacy-adapter@2.0.2 |
9784f29
to
37bb6eb
Compare
Conflicts: pnpm-lock.yaml
"pg": "^8.7.3", | ||
"sqlite3": "^5.0.8", | ||
"typeorm": "0.3.7", | ||
"typeorm": "0.3.15", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Locked in on 0.3.15
as something is likely broken in 0.3.16
I think typeorm/typeorm#10041 would solve the issue.
Follow-up of #7703
Database adapters are not dependent on Next.js features, so it makes sense to republish them under the
@auth/*
scope.This PR is part of a series to convert adapters, using
@auth/core
for types.BREAKING CHANGE:
If you are coming from the previous adapter, change your
package.json
:And run
npm install
,yarn install
orpnpm install
respectively.Note: This packages is published as ESM-only