Infer `AuthUser` / `AuthSession` from `auth.ts`: plugin and `additionalFields` columns are missing from `c.get('user')`, `getUser()` and `requireAuth()`
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 53/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- backend, developer-experience
Direzione di ricerca
Start with packages/void/src/runtime/auth.ts and the CloudContextVariables definitions in packages/void/src/runtime/handler.ts; trace how AuthUser and AuthSession flow into getUser(), getSession() and requireAuth(c). Check how .void/env.d.ts generates inferred types and use the Better Auth config type and the issue’s reproduction to verify the expected fields appear. Done when those APIs type the configured plugin and additional fields correctly.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Description
AuthUser and AuthSession are always Better Auth's base shapes, whatever auth.ts configures. Fields added by plugins (role and banned from admin(), impersonatedBy on the session) or by user.additionalFields are present at runtime but missing from the types of c.get('user'), c.get('session'), getUser(), getSession() and requireAuth(c).
The app can't fix this itself:
- Redeclaring
useronCloudContextVariablesfails with TS2717, because the property already has a different type. AuthUseris a type alias, so it can't be augmented.
A cast at every read is the only option.
Void already has the information. defineAuth<T>(config: T): T keeps the config type, and .void/better-auth-schema.ts is generated with the plugin columns.
Steps to reproduce
-
Enable auth and add
auth.tswith a plugin and a custom field:// auth.ts import { admin } from 'better-auth/plugins/admin'; import { defineAuth } from 'void/auth'; export default defineAuth(({ defaults }) => ({ ...defaults, plugins: [admin()], user: { additionalFields: { plan: { type: 'string', required: false } } }, })); -
Read the fields on the server:
import { defineHandler } from 'void'; import { getUser } from 'void/auth'; export const loader = defineHandler((c) => ({ role: c.get('user')?.role, plan: getUser()?.plan, })); -
Run
tsc.
Actual behavior
error TS2339: Property 'role' does not exist on type '{ id: string; createdAt: Date; updatedAt: Date; email: string; emailVerified: boolean; name: string; image?: string | null | undefined; }'.
error TS2339: Property 'plan' does not exist on type '{ id: string; createdAt: Date; updatedAt: Date; email: string; emailVerified: boolean; name: string; image?: string | null | undefined; }'.
Trying to override the type:
declare module 'void' {
interface CloudContextVariables {
user: (AuthUser & { role: string | null }) | null;
}
}
error TS2717: Subsequent property declarations must have the same type. Property 'user' must be of type '{ id: string; … } | null', but here has type '… | null'.
Expected behavior
c.get('user'), getUser() and requireAuth(c) include role, banned, banReason, banExpires and plan. c.get('session') and getSession() include impersonatedBy.
Cause
packages/void/src/runtime/auth.ts (main @ a6de7829bf, lines 6–7):
export type AuthUser = User;
export type AuthSession = Session;
User and Session come from better-auth without any options, so they're the base shapes. CloudContextVariables (runtime/handler.ts lines 29–31), AuthState, getUser, getSession and requireAuth are all typed from them.
Possible fix
Better Auth can already infer both types from the config type. This type-checks with the auth.ts above, and both role and plan are present:
import type { Auth } from 'better-auth';
import type config from './auth';
type Options = ReturnType<typeof config>;
type User = Auth<Options>['$Infer']['Session']['user']; // includes role, banned, plan
type Session = Auth<Options>['$Infer']['Session']['session']; // includes impersonatedBy
Void could generate this the way .void/env.d.ts augments ValidatedEnv and CloudBindings:
- Make
AuthUserandAuthSessioninterfaces:export interface AuthUser extends User {}. - Generate
.void/auth.d.tswhenauth.tsexists:
declare module 'void/auth' {
interface AuthUser extends _InferredUser {}
interface AuthSession extends _InferredSession {}
}
Everything typed from AuthUser, including CloudContextVariables, would then pick up the fields.
Workaround
Cast in one helper:
import { userTable } from '@auth-schema'; // .void/better-auth-schema.ts
type User = typeof userTable.$inferSelect;
export function getCurrentUser(c: CloudContext): User | null {
return c.get('user') as User | null;
}
Environment
- void 1.2.1, better-auth 1.7.11
- TypeScript 7.0.2, vite-plus 1.3.0, Node 22.23.3, macOS 26.6
- Lingua principale
- TypeScript
- Stelle
- 580
- Fork
- 56
- Merge medio
- 8h 32m
- PR unite (30g)
- 111
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di voidzero-dev/void
-
Dev: `better-auth/client/plugins` fails to resolve when auth is enabled (the `better-auth/client` alias matches it as a prefix)Forse già presa @MaxtuneLee l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
voidzero-dev/void#565 ·
I maintainer di solito rispondono entro 1 giorno
-
prepareDeployArtifact omits worker.vars that the CLI managed deploy includesForse già presa @dvkam l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
voidzero-dev/void#529 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 1/5 1-3 ore Idoneità per principianti 78/100
voidzero-dev/void#428 ·
I maintainer di solito rispondono entro 1 giorno
-
voidzero-dev/void#579 ·
I maintainer di solito rispondono entro 1 giorno
-
voidzero-dev/void#577 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di voidzero-dev/void
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
awesome-dsh-plugin/awesome-dsh-plugin#9184 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
farion1231/cc-switch#8829 ·
I maintainer di solito rispondono entro 1 giorno
-
[core-client] Remove unused hand-maintained transport helpers after the definition-table cutoverApertadoc-audit enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100