[GH-ISSUE #3322] Get provider of current session? #9569

New Issue

GiteaMirror · 2026-04-13T05:05:22-05:00

GiteaMirror commented

2026-04-13 05:05:22 -05:00

Originally created by @piscopancer on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/3322

Cannot read it from useSession, are there any methods except for when somehow passing a search param with param that i will then read on the server, will I be able to? why? idk

Originally created by @piscopancer on GitHub (Jul 9, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/3322 Cannot read it from `useSession`, are there any methods except for when somehow passing a search param with param that i will then read on the server, will I be able to? why? idk

GiteaMirror added the locked label 2026-04-13 05:05:22 -05:00

GiteaMirror closed this issue

2026-04-13 05:05:22 -05:00

GiteaMirror commented

2026-04-13 05:05:24 -05:00

@dosubot[bot] commented on GitHub (Jul 9, 2025):

You can't get the provider (like Google, GitHub, etc.) of the current session directly from useSession, because the session object in better-auth doesn't include provider info by default—it only has fields like id, userId, and timestamps. Provider info is stored in the account object, not the session, so useSession won't expose it out of the box [code reference].

The standard way to get the provider for the current user is to look up the account(s) for the userId from the session on the server side. This is intentional: a user can have multiple linked accounts/providers, and the session is kept minimal for security and flexibility reasons.

If you really need the provider in the session, you can add it yourself using the additionalFields config and hooks at login, but this is not the default or recommended pattern [docs]. Passing the provider as a search param and reading it on the server is not a standard or secure workaround.

In short: useSession won't give you the provider, and the best practice is to fetch the user's accounts on the server using their userId from the session. If you need provider info on the client, you'll need to explicitly wire it into the session yourself.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 9, 2025):  You can't get the provider (like Google, GitHub, etc.) of the current session directly from useSession, because the session object in better-auth doesn't include provider info by default—it only has fields like id, userId, and timestamps. Provider info is stored in the account object, not the session, so useSession won't expose it out of the box [[code reference]](https://github.com/better-auth/better-auth/blob/b766b22865895f5cdd7dc575b0cc2e023e795740/packages/better-auth/src/db/schema.ts). The standard way to get the provider for the current user is to look up the account(s) for the userId from the session on the server side. This is intentional: a user can have multiple linked accounts/providers, and the session is kept minimal for security and flexibility reasons. If you really need the provider in the session, you can add it yourself using the additionalFields config and hooks at login, but this is not the default or recommended pattern [[docs]](https://github.com/better-auth/better-auth/blob/b766b22865895f5cdd7dc575b0cc2e023e795740/packages/better-auth/src/types/options.ts). Passing the provider as a search param and reading it on the server is not a standard or secure workaround. In short: useSession won't give you the provider, and the best practice is to fetch the user's accounts on the server using their userId from the session. If you need provider info on the client, you'll need to explicitly wire it into the session yourself.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/b077f63a-7146-4afd-b58e-be2b4d757768?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b077f63a-7146-4afd-b58e-be2b4d757768?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b077f63a-7146-4afd-b58e-be2b4d757768?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b077f63a-7146-4afd-b58e-be2b4d757768?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b077f63a-7146-4afd-b58e-be2b4d757768?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b077f63a-7146-4afd-b58e-be2b4d757768?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b077f63a-7146-4afd-b58e-be2b4d757768?feedback_type=other)  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3322)

GiteaMirror commented

2026-04-13 05:05:25 -05:00

@piscopancer commented on GitHub (Jul 9, 2025):

@dosu alr i found a way to get accounts, but what must the circumstance for 2 accounts to be in the array? I am having oauth only authorization using google and github and I am not planning to use account linking. I guess in my case a user will never have two accounts per their session

@piscopancer commented on GitHub (Jul 9, 2025): @dosu alr i found a way to get accounts, but what must the circumstance for 2 accounts to be in the array? I am having oauth only authorization using google and github and I am not planning to use account linking. I guess in my case a user will never have two accounts per their session

GiteaMirror commented

2026-04-13 05:05:25 -05:00

@dosubot[bot] commented on GitHub (Jul 9, 2025):

You're correct: with only OAuth (Google and GitHub) and no account linking enabled, a user will never have more than one account per provider, so you won't see multiple accounts in the array for a single userId. Multiple accounts only appear if account linking is explicitly enabled and used—there are no implicit or edge-case scenarios where this happens in your setup. This is by design in better-auth to avoid accidental account merging and keep things predictable for OAuth-only flows [code reference].

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 9, 2025):  You're correct: with only OAuth (Google and GitHub) and no account linking enabled, a user will never have more than one account per provider, so you won't see multiple accounts in the array for a single userId. Multiple accounts only appear if account linking is explicitly enabled and used—there are no implicit or edge-case scenarios where this happens in your setup. This is by design in better-auth to avoid accidental account merging and keep things predictable for OAuth-only flows [[code reference]](https://github.com/better-auth/better-auth/blob/b766b22865895f5cdd7dc575b0cc2e023e795740/packages/better-auth/src/oauth2/link-account.ts).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/2f396d7d-14e7-4e74-8747-59eb1b49ed9e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2f396d7d-14e7-4e74-8747-59eb1b49ed9e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2f396d7d-14e7-4e74-8747-59eb1b49ed9e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2f396d7d-14e7-4e74-8747-59eb1b49ed9e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2f396d7d-14e7-4e74-8747-59eb1b49ed9e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2f396d7d-14e7-4e74-8747-59eb1b49ed9e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2f396d7d-14e7-4e74-8747-59eb1b49ed9e?feedback_type=other)  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3322)

GiteaMirror commented

2026-04-13 05:05:26 -05:00

@dagmawibabi commented on GitHub (Jul 10, 2025):

Hi @piscopancer does the answer from @dosubot answer your question?

I've reviewed it and it's accurate!

@dagmawibabi commented on GitHub (Jul 10, 2025): Hi @piscopancer does the answer from @dosubot answer your question? I've reviewed it and it's accurate!

GiteaMirror commented

2026-04-13 05:05:27 -05:00

@piscopancer commented on GitHub (Jul 10, 2025):

@dagmawibabi yeah i followed dosu's explanation, worked for me where i read oauth data to upsert to the db (i prefer doing it manually)

@piscopancer commented on GitHub (Jul 10, 2025): @dagmawibabi yeah i followed dosu's explanation, worked for me where i read oauth data to upsert to the db (i prefer doing it manually)

GiteaMirror commented

2026-04-13 05:05:28 -05:00

@dosubot[bot] commented on GitHub (Jul 10, 2025):

Thanks for reviewing and confirming! If you have any other questions or need more details about session providers or account handling, just let me know.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 10, 2025):  Thanks for reviewing and confirming! If you have any other questions or need more details about session providers or account handling, just let me know.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/e6100599-89e7-4995-8654-e16570b06c34?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e6100599-89e7-4995-8654-e16570b06c34?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e6100599-89e7-4995-8654-e16570b06c34?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e6100599-89e7-4995-8654-e16570b06c34?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e6100599-89e7-4995-8654-e16570b06c34?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e6100599-89e7-4995-8654-e16570b06c34?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e6100599-89e7-4995-8654-e16570b06c34?feedback_type=other)  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3322)

GiteaMirror commented

2026-04-13 05:05:29 -05:00

@bauchdj commented on GitHub (Jul 15, 2025):

@dosu how do I make it so additionalFields show up when I use authclient.useSession()?

@bauchdj commented on GitHub (Jul 15, 2025): @dosu how do I make it so additionalFields show up when I use authclient.useSession()?

GiteaMirror commented

2026-04-13 05:05:29 -05:00

@dagmawibabi commented on GitHub (Jul 15, 2025):

@bauchdj we're currently building an option to do that for version 1.3, but until then you'd have to create your own database query to fetch the remaining data. But v1.3 will hopefully be released by the end of this week.

@dagmawibabi commented on GitHub (Jul 15, 2025): @bauchdj we're currently building an option to do that for version 1.3, but until then you'd have to create your own database query to fetch the remaining data. But v1.3 will hopefully be released by the end of this week.

GiteaMirror commented

2026-04-13 05:05:30 -05:00

@matt-roz commented on GitHub (Sep 1, 2025):

For anyone that follows after me; I am using the following workaround with a hook on ctx.path.startsWith('/callback/:id'):

// _zod.ts
export const AUTH_PROVIDERS = {
  TWITCH: 'twitch',
  DISCORD: 'discord'
} as const

export type AuthProvider = (typeof AUTH_PROVIDERS)[keyof typeof AUTH_PROVIDERS]

export const ZBetterAuthProviderResponse = z.object({
  id: z.enum(AUTH_PROVIDERS)
})

export const ZSession = z.object({
  id: z.string(),
  expiresAt: z.date(),
  token: z.string(),
  createdAt: z.date(),
  updatedAt: z.date(),
  ipAddress: z.string().nullable(),
  userAgent: z.string().nullable(),
  userId: z.string(),
  provider_id: z.string().nullable()
})

// auth.ts
export const auth = betterAuth({
  /* ... */
  session: { additionalFields: { provider_id: { type: 'string', required: false, input: false } } },

  /* ... */
  socialProviders: {
    twitch: { clientId: TWITCH_CLIENT_ID, clientSecret: TWITCH_CLIENT_SECRET },
    discord: { clientId: DISCORD_CLIENT_ID, clientSecret: DISCORD_CLIENT_SECRET }
  },

  /* ... */
  hooks: {
    after: createAuthMiddleware(async (ctx) => {
      if (ctx.path.startsWith('/callback/:id')) {
        let prov: z.infer<typeof ZBetterAuthProviderResponse>
        let sess: z.infer<typeof ZSession>
        let accs: Account[] = []

        try {
          prov = ZBetterAuthProviderResponse.parse(ctx.params)
        } catch (error: unknown) {
          const errMsg = stringifyUnknownError(error).unwrapOr('unknown error')
          const statusMsg = `failed to parse provider from params ${JSON.stringify(ctx.params)} as {"id": "providerId"}`
          throw new APIError('BAD_REQUEST', { message: `${statusMsg}: ${errMsg}` })
        }

        try {
          sess = ZSession.parse(ctx.context.newSession?.session)
        } catch (error: unknown) {
          const errMsg = stringifyUnknownError(error).unwrapOr('unknown error')
          const statusMsg = `could not parse session: ${JSON.stringify(ctx.context.newSession?.session)}`
          throw new APIError('EXPECTATION_FAILED', { message: `${statusMsg}: ${errMsg}` })
        }

        if (sess.provider_id !== null) {
          const message = `provider_id already set: ${sess.provider_id}`
          throw new APIError('CONFLICT', { message })
        }

        try {
          accs = await drizzle.select().from(accounts).where(eq(accounts.userId, sess.userId))
        } catch (error: unknown) {
          const errMsg = stringifyUnknownError(error).unwrapOr('unknown error')
          const statusMsg = `could not retrieve accounts: ${JSON.stringify(sess.userId)}`
          throw new APIError('INTERNAL_SERVER_ERROR', { message: `${statusMsg}: ${errMsg}` })
        }

        // user potentially intercepted redirect and manually set params - check if account type exists
        if (!accs.some((acc) => acc.providerId === prov.id)) {
          const message = `account with providerId ${prov.id} not found`
          throw new APIError('NOT_FOUND', { message })
        }

        try {
          // the user has an account with the providerId - update session to reflect
          await drizzle.update(sessions).set({ provider_id: prov.id }).where(eq(sessions.id, sess.id))
        } catch (error: unknown) {
          const errMsg = stringifyUnknownError(error).unwrapOr('unknown error')
          const statusMsg = `Could Not Update Session: ${JSON.stringify(sess.id)}`
          throw new APIError('INTERNAL_SERVER_ERROR', { message: `${statusMsg}: ${errMsg}` })
        }
      }
    })
  }
})

@matt-roz commented on GitHub (Sep 1, 2025): For anyone that follows after me; I am using the following workaround with a hook on `ctx.path.startsWith('/callback/:id')`: ```typescript // _zod.ts export const AUTH_PROVIDERS = { TWITCH: 'twitch', DISCORD: 'discord' } as const export type AuthProvider = (typeof AUTH_PROVIDERS)[keyof typeof AUTH_PROVIDERS] export const ZBetterAuthProviderResponse = z.object({ id: z.enum(AUTH_PROVIDERS) }) export const ZSession = z.object({ id: z.string(), expiresAt: z.date(), token: z.string(), createdAt: z.date(), updatedAt: z.date(), ipAddress: z.string().nullable(), userAgent: z.string().nullable(), userId: z.string(), provider_id: z.string().nullable() }) ``` ```typescript // auth.ts export const auth = betterAuth({ /* ... */ session: { additionalFields: { provider_id: { type: 'string', required: false, input: false } } }, /* ... */ socialProviders: { twitch: { clientId: TWITCH_CLIENT_ID, clientSecret: TWITCH_CLIENT_SECRET }, discord: { clientId: DISCORD_CLIENT_ID, clientSecret: DISCORD_CLIENT_SECRET } }, /* ... */ hooks: { after: createAuthMiddleware(async (ctx) => { if (ctx.path.startsWith('/callback/:id')) { let prov: z.infer<typeof ZBetterAuthProviderResponse> let sess: z.infer<typeof ZSession> let accs: Account[] = [] try { prov = ZBetterAuthProviderResponse.parse(ctx.params) } catch (error: unknown) { const errMsg = stringifyUnknownError(error).unwrapOr('unknown error') const statusMsg = `failed to parse provider from params ${JSON.stringify(ctx.params)} as {"id": "providerId"}` throw new APIError('BAD_REQUEST', { message: `${statusMsg}: ${errMsg}` }) } try { sess = ZSession.parse(ctx.context.newSession?.session) } catch (error: unknown) { const errMsg = stringifyUnknownError(error).unwrapOr('unknown error') const statusMsg = `could not parse session: ${JSON.stringify(ctx.context.newSession?.session)}` throw new APIError('EXPECTATION_FAILED', { message: `${statusMsg}: ${errMsg}` }) } if (sess.provider_id !== null) { const message = `provider_id already set: ${sess.provider_id}` throw new APIError('CONFLICT', { message }) } try { accs = await drizzle.select().from(accounts).where(eq(accounts.userId, sess.userId)) } catch (error: unknown) { const errMsg = stringifyUnknownError(error).unwrapOr('unknown error') const statusMsg = `could not retrieve accounts: ${JSON.stringify(sess.userId)}` throw new APIError('INTERNAL_SERVER_ERROR', { message: `${statusMsg}: ${errMsg}` }) } // user potentially intercepted redirect and manually set params - check if account type exists if (!accs.some((acc) => acc.providerId === prov.id)) { const message = `account with providerId ${prov.id} not found` throw new APIError('NOT_FOUND', { message }) } try { // the user has an account with the providerId - update session to reflect await drizzle.update(sessions).set({ provider_id: prov.id }).where(eq(sessions.id, sess.id)) } catch (error: unknown) { const errMsg = stringifyUnknownError(error).unwrapOr('unknown error') const statusMsg = `Could Not Update Session: ${JSON.stringify(sess.id)}` throw new APIError('INTERNAL_SERVER_ERROR', { message: `${statusMsg}: ${errMsg}` }) } } }) } }) ```

GiteaMirror commented

2026-04-13 05:05:31 -05:00

@Jackinatox commented on GitHub (Sep 8, 2025):

The answer from @dosu was already useful, but i couldnt figure it out. My Account model only references the user and because i dont have account linking on, i have multiple accounts per user and now way to tell which session they belong to.

model Account {
  id                    String    @id
  accountId             String
  providerId            String
  userId                String
  user                  User      @relation(fields: [userId], references: [id], onDelete: Cascade)
  accessToken           String?
  refreshToken          String?
  idToken               String?
  accessTokenExpiresAt  DateTime?
  refreshTokenExpiresAt DateTime?
  scope                 String?
  password              String?
  createdAt             DateTime  @default(now())
  updatedAt             DateTime  @updatedAt

  @@map("account")
}

Edit: So either I set it up wrong, or i need to modify the session and create a database before hook to save the account in the session.

@Jackinatox commented on GitHub (Sep 8, 2025): The answer from @dosu was already useful, but i couldnt figure it out. My Account model only references the user and because i dont have account linking on, i have multiple accounts per user and now way to tell which session they belong to. ``` model Account { id String @id accountId String providerId String userId String user User @relation(fields: [userId], references: [id], onDelete: Cascade) accessToken String? refreshToken String? idToken String? accessTokenExpiresAt DateTime? refreshTokenExpiresAt DateTime? scope String? password String? createdAt DateTime @default(now()) updatedAt DateTime @updatedAt @@map("account") } ``` Edit: So either I set it up wrong, or i need to modify the session and create a database before hook to save the account in the session.

Sign in to join this conversation.

Branches Tags

changeset-release/main

main

dependabot/npm_and_yarn/hono-4.12.18

dependabot/npm_and_yarn/fast-xml-parser-5.7.0

2026-05-13/fix/access-authorize-edge-cases

fix/oauth-provider-consent-missing-client

fix/oauth-provider-basic-auth-secret-colon

2026-05-13/feat/captcha-wildcard-endpoints

dependabot/github_actions/github-actions-98f3470200

dependabot/npm_and_yarn/demo/nextjs/hono-4.12.18

dependabot/npm_and_yarn/demo/electron/postcss-8.5.13

2026-05-13/ci/stabilize-docker-startup

changeset-release/next

fix/disable-migration-generate

2026-05-07/fix/admin-set-password-upsert

2026-05-10/fix/lenient-cookie-parser

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

dependabot/npm_and_yarn/demo/expo/babel/plugin-transform-modules-systemjs-7.29.4

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

dependabot/npm_and_yarn/demo/nextjs/fast-uri-3.1.2

dependabot/npm_and_yarn/demo/electron/fast-uri-3.1.2

2026-05-08/feat/register-before-send

dependabot/npm_and_yarn/demo/electron/ip-address-10.2.0

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-additional-params

feat/oauth-provider-backchannel-logout-next

feat/oauth-idp-initiated-bounce-next

feat/oauth-idp-initiated-bounce

refactor/sign-in-challenges

2026-04-21/fix/oauth-rfc-input-validation

fix/release-notes-new-packages

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

2026-04-12/security/dynamic-baseurl-proxy-trust-default

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

claude/slack-update-stripe-docs-consistency-8Sc0w

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-24/fix/update-user-info-on-link

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#9569