Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Infer `AuthUser` / `AuthSession` from `auth.ts`: plugin and `additionalFields` columns are missing from `c.get('user')`, `getUser()` and `requireAuth()`

Offen
  • Stimmt etwas nicht?
#567 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
53/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
backend, developer-experience

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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 user on CloudContextVariables fails with TS2717, because the property already has a different type.
  • AuthUser is 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

  1. Enable auth and add auth.ts with 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 } } },
}));

  2. 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,
}));

  3. 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:

  1. Make AuthUser and AuthSession interfaces: export interface AuthUser extends User {}.
  2. Generate .void/auth.d.ts when auth.ts exists:
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
Vorherrschende Sprache
TypeScript
Sterne
402
Forks
32
Ø Merge
8 Std. 32 Min.
Gemergte PRs (30 T.)
111

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus voidzero-dev/void

Alle Issues in voidzero-dev/void

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.