fix(auth): pin better-auth packages to exact 1.6.22

Dokploy builds with npm install, which resolved the ^1.6.22 range to
better-auth 1.7.0 (unlinkAccount API changed to { accountId }), failing
the production build. Locally bun.lock pinned 1.6.22 while
@better-auth/passkey@1.6.9 and @better-auth/expo@1.6.11 used older
peer deps (better-call 1.3.5), which broke client plugin type inference
(authClient.admin missing).

Pin all better-auth packages to exact 1.6.22 so npm and bun resolve
identically, and align passkey/expo plugins with matching peer deps
(better-call 1.3.7). Verified with a full next build --webpack.
This commit is contained in:
2026-08-19 01:29:15 +08:00
parent 2f9949c2bb
commit 8a945bdd1a
3 changed files with 15 additions and 31 deletions
+5 -5
View File
@@ -18,10 +18,10 @@
},
"dependencies": {
"@aws-sdk/client-s3": "^3.1036.0",
"@better-auth/api-key": "^1.6.22",
"@better-auth/drizzle-adapter": "^1.6.9",
"@better-auth/expo": "^1.6.11",
"@better-auth/passkey": "^1.6.9",
"@better-auth/api-key": "1.6.22",
"@better-auth/drizzle-adapter": "1.6.22",
"@better-auth/expo": "1.6.22",
"@better-auth/passkey": "1.6.22",
"@elysia/cron": "^1.4.2",
"@elysia/eden": "^1.4.10",
"@elysia/openapi": "^1.4.15",
@@ -37,7 +37,7 @@
"@tiptap/pm": "^3.22.4",
"@tiptap/react": "^3.22.4",
"@tiptap/starter-kit": "^3.22.4",
"better-auth": "^1.6.22",
"better-auth": "1.6.22",
"dotenv": "^17.4.2",
"drizzle-orm": "^0.45.2",
"echarts": "^6.0.0",