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

additional field throw an error when fetch from user session #2656

New Issue
Closed
opened 2026-03-13 10:11:13 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-13 10:11:13 -05:00
Owner
Copy Link

Originally created by @Murlidhar08 on GitHub (Jan 5, 2026).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

I am new to better-auth
help if there any miss configuration

Here is the prisma table schema
`model Session {
id String @id
expiresAt DateTime
token String
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
ipAddress String?
userAgent String?
userId String
user User @relation(fields: [userId], references: [id], onDelete: Cascade)
activeBusinessId String?

@@unique([token])
@@index([userId])
@@map("session")
}`

Here is how I fetch additional field in client component
defaultValues: { name: session?.user?.name || '', email: session?.user?.email || '', contactNo: session?.user?.contactNo || '', },

But Next JS build error

Type error: Property 'contactNo' does not exist on type '{ id: string; createdAt: Date; updatedAt: Date; email: string; emailVerified: boolean; name: string; image?: string | null | undefined; twoFactorEnabled: boolean | null | undefined; }'.

33 | name: session?.user?.name || '',
34 | email: session?.user?.email || '',

35 | contactNo: session?.user?.contactNo || '',
| ^
36 | },
37 | })
38 |
Next.js build worker exited with code: 1 and signal: null

Current vs. Expected behavior

when I add additional fields in user or session section.
It should fetch and not throw an error field does not exits

What version of Better Auth are you using?

1.4.5

System info

{
  "system": {
    "platform": "win32",
    "arch": "x64",
    "version": "Windows 10 Home Single Language",
    "release": "10.0.19045",
    "cpuCount": 4,
    "cpuModel": "Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz",
    "totalMemory": "15.89 GB",
    "freeMemory": "5.94 GB"
  },
  "node": {
    "version": "v25.2.1",
    "env": "development"
  },
  "packageManager": {
    "name": "npm",
    "version": "11.7.0"
  },
  "frameworks": [
    {
      "name": "next",
      "version": "16.1.0"
    },
    {
      "name": "react",
      "version": "19.2.3"
    }
  ],
  "databases": [
    {
      "name": "@prisma/client",
      "version": "^7.1.0"
    }
  ],
  "betterAuth": {
    "version": "^1.4.5",
    "config": {
      "appName": "Settlr",
      "user": {
        "additionalFields": {
          "contactNo": {
            "type": "string",
            "required": false,
            "input": true
          },
          "address": {
            "type": "string",
            "required": false,
            "input": true
          }
        }
      },
      "emailAndPassword": {
        "enabled": true,
        "requireEmailVerification": true
      },
      "emailVerification": {},
      "socialProviders": {
        "google": {
          "clientId": "[REDACTED]",
          "clientSecret": "[REDACTED]"
        },
        "discord": {
          "clientId": "[REDACTED]",
          "clientSecret": "[REDACTED]"
        }
      },
      "session": {
        "additionalFields": {
          "activeBusinessId": {
            "type": "string",
            "required": false,
            "input": true
          }
        }
      },
      "databaseHooks": {
        "session": {
          "create": {}
        }
      },
      "plugins": [
        {
          "name": "next-cookies",
          "config": {
            "id": "next-cookies",
            "hooks": {
              "after": [
                {}
              ]
            }
          }
        },
        {
          "name": "two-factor",
          "config": {
            "id": "two-factor",
            "endpoints": {},
            "hooks": {
              "after": [
                {}
              ]
            },
            "schema": {
              "user": {
                "fields": {
                  "twoFactorEnabled": {
                    "type": "boolean",
                    "required": false,
                    "defaultValue": false,
                    "input": false
                  }
                }
              },
              "twoFactor": {
                "fields": {
                  "secret": {
                    "type": "string",
                    "required": true,
                    "returned": false,
                    "index": true
                  },
                  "backupCodes": {
                    "type": "string",
                    "required": true,
                    "returned": false
                  },
                  "userId": {
                    "type": "string",
                    "required": true,
                    "returned": false,
                    "references": {
                      "model": "user",
                      "field": "id"
                    },
                    "index": true
                  }
                }
              }
            },
            "rateLimit": [
              {
                "window": 10,
                "max": 3
              }
            ],
            "$ERROR_CODES": {
              "OTP_NOT_ENABLED": "OTP not enabled",
              "OTP_HAS_EXPIRED": "OTP has expired",
              "TOTP_NOT_ENABLED": "TOTP not enabled",
              "TWO_FACTOR_NOT_ENABLED": "Two factor isn't enabled",
              "BACKUP_CODES_NOT_ENABLED": "Backup codes aren't enabled",
              "INVALID_BACKUP_CODE": "Invalid backup code",
              "INVALID_CODE": "Invalid code",
              "TOO_MANY_ATTEMPTS_REQUEST_NEW_CODE": "Too many attempts. Please request a new code.",
              "INVALID_TWO_FACTOR_COOKIE": "Invalid two factor cookie"
            }
          }
        }
      ]
    }
  }
}

Which area(s) are affected? (Select all that apply)

Types

Auth config (if applicable)

import { betterAuth } from "better-auth"

export const auth = betterAuth({
  // extra configuration
  user: {
    additionalFields: {
      contactNo: {
        type: "string",
        required: false,
        input: true
      },
      address: {
        type: "string",
        required: false,
        input: true
      },
    },
  },
  // extra configuration
  session: {
    additionalFields: {
      activeBusinessId: {
        type: "string",
        required: false,
        input: true
      }
    },
  },
});

Additional context

No response

Originally created by @Murlidhar08 on GitHub (Jan 5, 2026). ### Is this suited for github? - [ ] Yes, this is suited for github ### To Reproduce I am new to better-auth help if there any miss configuration Here is the prisma table schema `model Session { id String @id expiresAt DateTime token String createdAt DateTime @default(now()) updatedAt DateTime @updatedAt ipAddress String? userAgent String? userId String user User @relation(fields: [userId], references: [id], onDelete: Cascade) activeBusinessId String? @@unique([token]) @@index([userId]) @@map("session") }` Here is how I fetch additional field in client component `defaultValues: { name: session?.user?.name || '', email: session?.user?.email || '', contactNo: session?.user?.contactNo || '', },` **But Next JS build error** Type error: Property 'contactNo' does not exist on type '{ id: string; createdAt: Date; updatedAt: Date; email: string; emailVerified: boolean; name: string; image?: string | null | undefined; twoFactorEnabled: boolean | null | undefined; }'. 33 | name: session?.user?.name || '', 34 | email: session?.user?.email || '', > 35 | contactNo: session?.user?.contactNo || '', | ^ 36 | }, 37 | }) 38 | Next.js build worker exited with code: 1 and signal: null ### Current vs. Expected behavior when I add additional fields in user or session section. It should fetch and not throw an error field does not exits ### What version of Better Auth are you using? 1.4.5 ### System info ```bash { "system": { "platform": "win32", "arch": "x64", "version": "Windows 10 Home Single Language", "release": "10.0.19045", "cpuCount": 4, "cpuModel": "Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz", "totalMemory": "15.89 GB", "freeMemory": "5.94 GB" }, "node": { "version": "v25.2.1", "env": "development" }, "packageManager": { "name": "npm", "version": "11.7.0" }, "frameworks": [ { "name": "next", "version": "16.1.0" }, { "name": "react", "version": "19.2.3" } ], "databases": [ { "name": "@prisma/client", "version": "^7.1.0" } ], "betterAuth": { "version": "^1.4.5", "config": { "appName": "Settlr", "user": { "additionalFields": { "contactNo": { "type": "string", "required": false, "input": true }, "address": { "type": "string", "required": false, "input": true } } }, "emailAndPassword": { "enabled": true, "requireEmailVerification": true }, "emailVerification": {}, "socialProviders": { "google": { "clientId": "[REDACTED]", "clientSecret": "[REDACTED]" }, "discord": { "clientId": "[REDACTED]", "clientSecret": "[REDACTED]" } }, "session": { "additionalFields": { "activeBusinessId": { "type": "string", "required": false, "input": true } } }, "databaseHooks": { "session": { "create": {} } }, "plugins": [ { "name": "next-cookies", "config": { "id": "next-cookies", "hooks": { "after": [ {} ] } } }, { "name": "two-factor", "config": { "id": "two-factor", "endpoints": {}, "hooks": { "after": [ {} ] }, "schema": { "user": { "fields": { "twoFactorEnabled": { "type": "boolean", "required": false, "defaultValue": false, "input": false } } }, "twoFactor": { "fields": { "secret": { "type": "string", "required": true, "returned": false, "index": true }, "backupCodes": { "type": "string", "required": true, "returned": false }, "userId": { "type": "string", "required": true, "returned": false, "references": { "model": "user", "field": "id" }, "index": true } } } }, "rateLimit": [ { "window": 10, "max": 3 } ], "$ERROR_CODES": { "OTP_NOT_ENABLED": "OTP not enabled", "OTP_HAS_EXPIRED": "OTP has expired", "TOTP_NOT_ENABLED": "TOTP not enabled", "TWO_FACTOR_NOT_ENABLED": "Two factor isn't enabled", "BACKUP_CODES_NOT_ENABLED": "Backup codes aren't enabled", "INVALID_BACKUP_CODE": "Invalid backup code", "INVALID_CODE": "Invalid code", "TOO_MANY_ATTEMPTS_REQUEST_NEW_CODE": "Too many attempts. Please request a new code.", "INVALID_TWO_FACTOR_COOKIE": "Invalid two factor cookie" } } } ] } } } ``` ### Which area(s) are affected? (Select all that apply) Types ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ // extra configuration user: { additionalFields: { contactNo: { type: "string", required: false, input: true }, address: { type: "string", required: false, input: true }, }, }, // extra configuration session: { additionalFields: { activeBusinessId: { type: "string", required: false, input: true } }, }, }); ``` ### Additional context _No response_
GiteaMirror added the nextjs label 2026-03-13 10:11:13 -05:00
GiteaMirror commented 2026-03-13 10:11:14 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Jan 5, 2026):

It seems like you're encountering a TypeScript error indicating that the property 'contactNo' does not exist on the user object in your Better Auth setup. This typically happens when additional fields that you've defined in your user.additionalFields are not properly reflected in the TypeScript types.

To resolve this, ensure that your Better Auth configuration properly includes the contactNo field in the user schema. Here's a brief checklist:

  1. Check Configuration: Make sure that your user.additionalFields definition in your Better Auth configuration includes contactNo.
user: {
    additionalFields: {
      contactNo: {
        type: "string",
        required: false,
        input: true,
      },
      address: { /* ... */ },
    },
},

  1. TypeScript Definitions: Ensure that the TypeScript type definitions have been updated to include the new fields. If you've recently added contactNo, you may need to restart the TypeScript server or recompile your application.

  2. Check for Type Inference: If you're using custom user types in your application, make sure they extend the default user object type to include the new fields.

If the problem persists, consider checking for any existing issues in the Better Auth GitHub repository regarding TypeScript field inference or similar errors, as it might be a common problem that has been documented.

If you need further assistance, feel free to tag @bekacru or @ping__ in the repository, as they'll be able to provide more targeted help!

Have you tried updating your TypeScript definitions or restarting your development environment after adding contactNo? What was the result?

If you need more help, tag @better-auth-agent in a comment so I can respond.

Diagram • Discord • GitHub

Diagram Join Star

@better-auth-agent[bot] commented on GitHub (Jan 5, 2026): It seems like you're encountering a TypeScript error indicating that the property 'contactNo' does not exist on the user object in your Better Auth setup. This typically happens when additional fields that you've defined in your `user.additionalFields` are not properly reflected in the TypeScript types. To resolve this, ensure that your Better Auth configuration properly includes the `contactNo` field in the user schema. Here's a brief checklist: 1. **Check Configuration**: Make sure that your `user.additionalFields` definition in your Better Auth configuration includes `contactNo`. ```typescript user: { additionalFields: { contactNo: { type: "string", required: false, input: true, }, address: { /* ... */ }, }, }, ``` 2. **TypeScript Definitions**: Ensure that the TypeScript type definitions have been updated to include the new fields. If you've recently added `contactNo`, you may need to restart the TypeScript server or recompile your application. 3. **Check for Type Inference**: If you're using custom user types in your application, make sure they extend the default user object type to include the new fields. If the problem persists, consider checking for any existing issues in the Better Auth GitHub repository regarding TypeScript field inference or similar errors, as it might be a common problem that has been documented. If you need further assistance, feel free to tag @bekacru or @ping__ in the repository, as they'll be able to provide more targeted help! Have you tried updating your TypeScript definitions or restarting your development environment after adding `contactNo`? What was the result? _If you need more help, tag @better-auth-agent in a comment so I can respond._ <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/skyvern_ultra_detailed_interactive.html) • [Discord](https://discord.gg/fG2XXEuQX3) • [GitHub](https://github.com/Skyvern-AI/Skyvern) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/skyvern_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/fG2XXEuQX3) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/Skyvern-AI/Skyvern)
GiteaMirror commented 2026-03-13 10:11:15 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jan 5, 2026):

Hi @Murlidhar08! I'm Dosu and I’m helping the better-auth team.

The TypeScript error happens because Better Auth doesn't automatically add custom fields like contactNo to the session user type on the client side. To fix this, you need to do two things:

  1. Make sure contactNo exists in your Prisma User model and is migrated to your database. If it's missing from your schema, add it and run a migration.

  2. Update your client setup to use the inferAdditionalFields plugin for type inference.
    On your server, export your auth instance type:

    // lib/auth.ts
export const auth = betterAuth({ ... });
export type Auth = typeof auth;

    On your client, set up your auth client like this:

    import { createAuthClient, inferAdditionalFields } from "better-auth/client";
import type { Auth } from "@/lib/auth";

export const authClient = createAuthClient({
  plugins: [inferAdditionalFields<Auth>()],
});

export const { useSession } = authClient;

    Now, session.user.contactNo should be recognized by TypeScript if the field is present in your database and returned by your adapter.
    Reference

If you still get type errors, you can use a workaround like manual type assertion or //@ts-expect-error above the line, but the plugin approach is preferred for type safety.

If the field is missing at runtime, double-check your Prisma schema, migration, and that your adapter is selecting contactNo in its queries. Only fields present in the DB and loaded by the adapter will show up in the session object.
Reference

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 5, 2026): <!-- Greeting --> Hi @Murlidhar08! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the better-auth team. <!-- Answer --> The TypeScript error happens because Better Auth doesn't automatically add custom fields like `contactNo` to the session user type on the client side. To fix this, you need to do two things: 1. **Make sure `contactNo` exists in your Prisma User model and is migrated to your database.** If it's missing from your schema, add it and run a migration. 2. **Update your client setup to use the `inferAdditionalFields` plugin for type inference.** On your server, export your auth instance type: ```ts // lib/auth.ts export const auth = betterAuth({ ... }); export type Auth = typeof auth; ``` On your client, set up your auth client like this: ```ts import { createAuthClient, inferAdditionalFields } from "better-auth/client"; import type { Auth } from "@/lib/auth"; export const authClient = createAuthClient({ plugins: [inferAdditionalFields<Auth>()], }); export const { useSession } = authClient; ``` Now, `session.user.contactNo` should be recognized by TypeScript if the field is present in your database and returned by your adapter. [Reference](https://github.com/better-auth/better-auth/issues/3328) If you still get type errors, you can use a workaround like manual type assertion or `//@ts-expect-error` above the line, but the plugin approach is preferred for type safety. If the field is missing at runtime, double-check your Prisma schema, migration, and that your adapter is selecting `contactNo` in its queries. Only fields present in the DB and loaded by the adapter will show up in the session object. [Reference](https://github.com/better-auth/better-auth/issues/4870) <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/243bad07-1c2b-413f-b9a9-4fbf14244a0a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/243bad07-1c2b-413f-b9a9-4fbf14244a0a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/243bad07-1c2b-413f-b9a9-4fbf14244a0a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/243bad07-1c2b-413f-b9a9-4fbf14244a0a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/243bad07-1c2b-413f-b9a9-4fbf14244a0a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/243bad07-1c2b-413f-b9a9-4fbf14244a0a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/243bad07-1c2b-413f-b9a9-4fbf14244a0a?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20TypeScript%20error%20happens%20because%20Better%20Auth%20doesn%27t%20automatically%20add%20custom%20fields%20like%20%60contactNo%60%20to%20the%20session%20user%20type%20on%20the%20client%20side.%20To%20fix%20this%2C%20you%20need%20to%20do%20two%20things%3A%0A%0A1.%20%2A%2AMake%20sure%20%60contactNo%60%20exists%20in%20your%20Prisma%20User%20model%20and%20is%20migrated%20to%20your%20database.%2A%2A%20If%20it%27s%20missing%20from%20your%20schema%2C%20add%20it%20and%20run%20a%20migration.%0A%0A2.%20%2A%2AUpdate%20your%20client%20setup%20to%20use%20the%20%60inferAdditionalFields%60%20plugin%20for%20type%20inference.%2A%2A%20%20%0A%20%20%20On%20your%20server%2C%20export%20your%20auth%20instance%20type%3A%0A%20%20%20%60%60%60ts%0A%20%20%20//%20lib/auth.ts%0A%20%20%20export%20const%20auth%20%3D%20betterAuth%28%7B%20...%20%7D%29%3B%0A%20%20%20export%20type%20Auth%20%3D%20typeof%20auth%3B%0A%20%20%20%60%60%60%0A%20%20%20On%20your%20client%2C%20set%20up%20your%20auth%20client%20like%20this%3A%0A%20%20%20%60%60%60ts%0A%20%20%20import%20%7B%20createAuthClient%2C%20inferAdditionalFields%20%7D%20from%20%22better-auth/client%22%3B%0A%20%20%20import%20type%20%7B%20Auth%20%7D%20from%20%22%40/lib/auth%22%3B%0A%0A%20%20%20export%20const%20authClient%20%3D%20createAuthClient%28%7B%0A%20%20%20%20%20plugins%3A%20%5BinferAdditionalFields%3CAuth%3E%28%29%5D%2C%0A%20%20%20%7D%29%3B%0A%0A%20%20%20export%20const%20%7B%20useSession%20%7D%20%3D%20authClient%3B%0A%20%20%20%60%60%60%0A%20%20%20Now%2C%20%60session.user.contactNo%60%20should%20be%20recognized%20by%20TypeScript%20if%20the%20field%20is%20present%20in%20your%20database%20and%20returned%20by%20your%20adapter.%20%20%0A%20%20%20%5BReference%5D%28https%3A//github.com/better-auth/better-auth/issues/3328%29%0A%0AIf%20you%20still%20get%20type%20errors%2C%20you%20can%20use%20a%20workaround%20like%20manual%20type%20assertion%20or%20%60//%40ts-expect-error%60%20above%20the%20line%2C%20but%20the%20plugin%20approach%20is%20preferred%20for%20type%20safety.%0A%0AIf%20the%20field%20is%20missing%20at%20runtime%2C%20double-check%20your%20Prisma%20schema%2C%20migration%2C%20and%20that%20your%20adapter%20is%20selecting%20%60contactNo%60%20in%20its%20queries.%20Only%20fields%20present%20in%20the%20DB%20and%20loaded%20by%20the%20adapter%20will%20show%20up%20in%20the%20session%20object.%20%20%0A%5BReference%5D%28https%3A//github.com/better-auth/better-auth/issues/4870%29)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![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/7138)
GiteaMirror commented 2026-03-13 10:11:15 -05:00
Author
Owner
Copy Link

@Murlidhar08 commented on GitHub (Jan 6, 2026):

Thank you @dosu
I works for me.

@Murlidhar08 commented on GitHub (Jan 6, 2026): Thank you @dosu I works for me.
GiteaMirror commented 2026-03-13 10:11:15 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jan 6, 2026):

You're welcome! Happy to help—feel free to reach out anytime if you need more assistance.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 6, 2026): <!-- Answer --> You're welcome! Happy to help—feel free to reach out anytime if you need more assistance. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/53138140-5d71-4b45-bc6e-888385c5cde3?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/53138140-5d71-4b45-bc6e-888385c5cde3?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/53138140-5d71-4b45-bc6e-888385c5cde3?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/53138140-5d71-4b45-bc6e-888385c5cde3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/53138140-5d71-4b45-bc6e-888385c5cde3?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/53138140-5d71-4b45-bc6e-888385c5cde3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/53138140-5d71-4b45-bc6e-888385c5cde3?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=You%27re%20welcome%21%20Happy%20to%20help%E2%80%94feel%20free%20to%20reach%20out%20anytime%20if%20you%20need%20more%20assistance.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![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/7138)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label nextjs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#2656
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?