github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-06-02 04:16:38 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

docs: add field mappings for migrating from next-auth v4 (#2315)

Browse Source 
* Update next-auth-migration-guide.mdx

* Update next-auth-migration-guide.mdx

* Update next-auth-migration-guide.mdx

* Update next-auth-migration-guide.mdx

* Update next-auth-migration-guide.mdx
This commit is contained in:
Rin Arakaki
2025-05-09 11:15:30 +09:00
committed by GitHub
parent ebc2ba753b
commit dcaba6ffd8
1 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/content/docs/guides/next-auth-migration-guide.mdx
View File

@@ -21,7 +21,9 @@ Instead of altering your existing database column names, you can map them to mat
#### User Schema
Your existing user schema is likely compatible with Better Auth, so no changes are needed.
Map the following fields in the session schema:
- (next-auth v4) `emailVerified`: datetime → boolean
#### Session Schema
@@ -29,6 +31,8 @@ Map the following fields in the session schema:
- `expires` → `expiresAt`
- `sessionToken` → `token`
- (next-auth v4) add `createdAt` with datetime type
- (next-auth v4) add `updatedAt` with datetime type
```typescript title="auth.ts"
export const auth = betterAuth({
@@ -48,11 +52,15 @@ Make sure to have `createdAt` and `updatedAt` fields on your session schema.
Map these fields in the account schema:
- (next-auth v4) `provider` → `providerId`
- `providerAccountId` → `accountId`
- `refresh_token` → `refreshToken`
- `access_token` → `accessToken`
- `access_token_expires` → `accessTokenExpiresAt`
- (next-auth v3) `access_token_expires` → `accessTokenExpiresAt` and int → datetime
- (next-auth v4) `expires_at` → `accessTokenExpiresAt` and int → datetime
- `id_token` → `idToken`
- (next-auth v4) add `createdAt` with datetime type
- (next-auth v4) add `updatedAt` with datetime type
Remove the `session_state`, `type`, and `token_type` fields, as they are not required by Better Auth.