github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #6665] better-auth fails to load in Cloudflare Workers due to createRequire error #19221

New Issue
Closed
opened 2026-04-15 18:03:39 -05:00 by GiteaMirror · 12 comments
GiteaMirror commented 2026-04-15 18:03:39 -05:00
Owner
Copy Link

Originally created by @tsatsujnr139 on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6665

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

Minimal Reproduction

Setup

  1. Create a new Cloudflare Worker project:
npm create cloudflare@latest
# Choose: Hello World worker
  1. Install better-auth:
npm install better-auth
  1. Update wrangler.json to enable Node.js compatibility:
{
  "compatibility_flags": ["nodejs_compat"]
}

Code

src/index.ts:

import { betterAuth } from "better-auth/minimal";

// Just importing and calling betterAuth() causes the error
const auth = betterAuth({
  baseURL: "http://localhost:8787",
  secret: "test-secret-key-min-32-characters-long",
  database: {
    provider: "sqlite",
    url: ":memory:",
  },
});

export default {
  async fetch(request: Request): Promise<Response> {
    return new Response("OK");
  },
};

Current vs. Expected behavior

Problem

When importing better-auth or better-auth/minimal in a Cloudflare Workers environment, the worker fails to start with the following error:

Uncaught TypeError: The argument 'path' The argument must be a file URL object, a file URL string, or an absolute path string.. Received 'undefined'

    at null.<anonymous> (node:module:34:15) in createRequire
    at null.<anonymous> (index.js:123632:34)

Expected Behavior

The worker should start successfully.

Actual Behavior

The worker fails to start with the createRequire error shown above.

Workaround

Currently, there is no reliable workaround. Attempts to:

  • Import directly from dist files (better-auth/dist/auth/minimal.mjs) fail with module not found errors
  • Configure Wrangler rules to exclude source files do not prevent the error

Environment

  • better-auth version: 1.4.6
  • Cloudflare Workers runtime: Latest (as of Dec 2025)
  • Wrangler version: Latest
  • Node.js compatibility flag: Enabled (nodejs_compat)

What version of Better Auth are you using?

1.4.6

System info

{
  "system": {
    "platform": "darwin",
    "arch": "arm64",
    "version": "Darwin Kernel Version 25.1.0: Mon Oct 20 19:34:05 PDT 2025; root:xnu-12377.41.6~2/RELEASE_ARM64_T6041",
    "release": "25.1.0",
    "cpuCount": 14,
    "cpuModel": "Apple M4 Pro",
    "totalMemory": "24.00 GB",
    "freeMemory": "0.25 GB"
  },
  "node": {
    "version": "v22.19.0",
    "env": "development"
  },
  "packageManager": {
    "name": "npm",
    "version": "10.9.3"
  },
  "frameworks": null,
  "databases": null,
  "betterAuth": {
    "version": "^1.4.6",
    "config": null
  }
}

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

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
const auth = betterAuth({
  baseURL: "http://localhost:8787",
  secret: "test-secret-key-min-32-characters-long",
  database: {
    provider: "sqlite",
    url: ":memory:",
  },
});

Additional context

Additional Context

  • The issue occurs with both better-auth and better-auth/minimal imports
  • The issue does NOT occur when the import is removed (worker starts successfully)
  • The error happens during module initialization, not during function calls
  • Also tried using better-auth-cloudflare wrapper, but the issue still remains.

Our Setup

We're using:

  • Cloudflare Workers with nodejs_compat compatibility flag enabled
  • Wrangler for local development and deployment

The error occurs in our code when we import better-auth:

// This import alone causes the error
import { betterAuth } from "better-auth"; // or import { betterAuth } from "better-auth/minimal";

// Even if we don't call betterAuth(), just importing causes the failure
Originally created by @tsatsujnr139 on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6665 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce ## Minimal Reproduction ### Setup 1. Create a new Cloudflare Worker project: ```bash npm create cloudflare@latest # Choose: Hello World worker ``` 2. Install better-auth: ```bash npm install better-auth ``` 3. Update `wrangler.json` to enable Node.js compatibility: ```json { "compatibility_flags": ["nodejs_compat"] } ``` ### Code **src/index.ts:** ```typescript import { betterAuth } from "better-auth/minimal"; // Just importing and calling betterAuth() causes the error const auth = betterAuth({ baseURL: "http://localhost:8787", secret: "test-secret-key-min-32-characters-long", database: { provider: "sqlite", url: ":memory:", }, }); export default { async fetch(request: Request): Promise<Response> { return new Response("OK"); }, }; ``` ### Current vs. Expected behavior ## Problem When importing `better-auth` or `better-auth/minimal` in a Cloudflare Workers environment, the worker fails to start with the following error: ``` Uncaught TypeError: The argument 'path' The argument must be a file URL object, a file URL string, or an absolute path string.. Received 'undefined' at null.<anonymous> (node:module:34:15) in createRequire at null.<anonymous> (index.js:123632:34) ``` ### Expected Behavior The worker should start successfully. ### Actual Behavior The worker fails to start with the `createRequire` error shown above. ### Workaround Currently, there is no reliable workaround. Attempts to: - Import directly from dist files (`better-auth/dist/auth/minimal.mjs`) fail with module not found errors - Configure Wrangler rules to exclude source files do not prevent the error ## Environment - **better-auth version**: 1.4.6 - **Cloudflare Workers runtime**: Latest (as of Dec 2025) - **Wrangler version**: Latest - **Node.js compatibility flag**: Enabled (`nodejs_compat`) ### What version of Better Auth are you using? 1.4.6 ### System info ```bash { "system": { "platform": "darwin", "arch": "arm64", "version": "Darwin Kernel Version 25.1.0: Mon Oct 20 19:34:05 PDT 2025; root:xnu-12377.41.6~2/RELEASE_ARM64_T6041", "release": "25.1.0", "cpuCount": 14, "cpuModel": "Apple M4 Pro", "totalMemory": "24.00 GB", "freeMemory": "0.25 GB" }, "node": { "version": "v22.19.0", "env": "development" }, "packageManager": { "name": "npm", "version": "10.9.3" }, "frameworks": null, "databases": null, "betterAuth": { "version": "^1.4.6", "config": null } } ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" const auth = betterAuth({ baseURL: "http://localhost:8787", secret: "test-secret-key-min-32-characters-long", database: { provider: "sqlite", url: ":memory:", }, }); ``` ### Additional context ## Additional Context - The issue occurs with both `better-auth` and `better-auth/minimal` imports - The issue does NOT occur when the import is removed (worker starts successfully) - The error happens during module initialization, not during function calls - Also tried using `better-auth-cloudflare` wrapper, but the issue still remains. ## Our Setup We're using: - Cloudflare Workers with `nodejs_compat` compatibility flag enabled - Wrangler for local development and deployment The error occurs in our code when we import `better-auth`: ```typescript // This import alone causes the error import { betterAuth } from "better-auth"; // or import { betterAuth } from "better-auth/minimal"; // Even if we don't call betterAuth(), just importing causes the failure ```
GiteaMirror added the lockedbug labels 2026-04-15 18:03:39 -05:00
GiteaMirror commented 2026-04-15 18:03:42 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Dec 10, 2025):

(tag @better-auth-agent if you would like an answer from the Agent)

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

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3637397863 --> @better-auth-agent[bot] commented on GitHub (Dec 10, 2025): (tag @better-auth-agent if you would like an answer from the Agent) _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-04-15 18:03:42 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Dec 10, 2025):

Hi there! It looks like your Cloudflare Worker is tripping over a call to Node’s createRequire, which usually means that some internal module resolution in Better Auth is trying to load files using Node’s filesystem methods. Since Cloudflare Workers run in a V8 isolate without a traditional filesystem, this incompatibility can cause the error you’re seeing.

Here are a few troubleshooting steps you can try:
• Verify that you’re using the most recent version of Better Auth. There have been improvements in module bundling, so upgrading may resolve this issue.
• Consider using our minimal build (if not already)—using the “better-auth/minimal” entry point should ideally avoid node-specific dependencies, but if it’s still causing issues, you might need to bundle or transpile Better Auth with a tool (such as webpack or rollup) configured for Cloudflare Workers. This bundling process can help resolve dynamic require calls.
• Double-check that your wrangler configuration is correctly set up with the latest Node compatibility flags. Sometimes adjusting the compatibility settings or even removing nodejs_compat (if possible) for parts of your code where filesystem access isn’t needed can help.
• If none of these approaches work, I recommend tagging @bekacru and @ping__ for additional insights—they’re very familiar with these environment-specific issues.

Does this help clarify the next steps, or is there another detail about your setup that you’d like to explore further? Tag @better-auth-agent if you would like an answer from the Agent.

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3637401465 --> @better-auth-agent[bot] commented on GitHub (Dec 10, 2025): Hi there! It looks like your Cloudflare Worker is tripping over a call to Node’s createRequire, which usually means that some internal module resolution in Better Auth is trying to load files using Node’s filesystem methods. Since Cloudflare Workers run in a V8 isolate without a traditional filesystem, this incompatibility can cause the error you’re seeing. Here are a few troubleshooting steps you can try: • Verify that you’re using the most recent version of Better Auth. There have been improvements in module bundling, so upgrading may resolve this issue. • Consider using our minimal build (if not already)—using the “better-auth/minimal” entry point should ideally avoid node-specific dependencies, but if it’s still causing issues, you might need to bundle or transpile Better Auth with a tool (such as webpack or rollup) configured for Cloudflare Workers. This bundling process can help resolve dynamic require calls. • Double-check that your wrangler configuration is correctly set up with the latest Node compatibility flags. Sometimes adjusting the compatibility settings or even removing nodejs_compat (if possible) for parts of your code where filesystem access isn’t needed can help. • If none of these approaches work, I recommend tagging @bekacru and @ping__ for additional insights—they’re very familiar with these environment-specific issues. Does this help clarify the next steps, or is there another detail about your setup that you’d like to explore further? Tag @better-auth-agent if you would like an answer from the Agent. <!-- 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-04-15 18:03:43 -05:00
Author
Owner
Copy Link

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

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

This is a known regression in better-auth 1.4.6: Node.js-specific code (including createRequire and path) is imported during module initialization, which Cloudflare Workers can't handle—even with nodejs_compat enabled. The error typically originates from SSO plugins or migration/database logic that expects Node primitives, causing the Worker to crash on import [source].

Disabling telemetry or using the better-auth-cloudflare wrapper doesn't fully resolve this, because some Node modules are still imported unconditionally in affected versions [source]. The minimal entrypoint itself doesn't use createRequire, but the error comes from deeper dependencies or build artifacts [source].

Workarounds:

  • Instantiate the auth client inside each request handler (not as a singleton) to avoid some initialization errors, but this won't fix unconditional Node imports [source].
  • Use Cloudflare-compatible database adapters (like NeonDB with Kysely or D1), and avoid Node-only libraries [source].
  • Try downgrading to a version before 1.4.6 (e.g., 1.3.4), or test a beta version like 1.4.6-beta.4 if available [source].
  • Set compatibility_flags = ["nodejs_compat_v2"] and a recent compatibility_date in Wrangler for improved Node polyfills, but this does not guarantee better-auth compatibility [source].

Limitations:
Full Cloudflare Workers compatibility is still a work in progress. Per-request instantiation breaks CLI features and type inference, and you may need to manage schema manually or run migrations in a Node environment [source]. The maintainers are aware and plan documentation improvements, but some issues stem from dependencies not supported in Workers [source].

If you need robust support for Workers, keep an eye on future releases and related issues for updates.

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

<!-- gh-comment-id:3637415650 --> @dosubot[bot] commented on GitHub (Dec 10, 2025): <!-- Greeting --> Hi @tsatsujnr139! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the better-auth team. <!-- Answer --> This is a known regression in better-auth 1.4.6: Node.js-specific code (including `createRequire` and `path`) is imported during module initialization, which Cloudflare Workers can't handle—even with `nodejs_compat` enabled. The error typically originates from SSO plugins or migration/database logic that expects Node primitives, causing the Worker to crash on import [[source](https://github.com/better-auth/better-auth/issues/6635)]. Disabling telemetry or using the `better-auth-cloudflare` wrapper doesn't fully resolve this, because some Node modules are still imported unconditionally in affected versions [[source](https://github.com/better-auth/better-auth/issues/3998)]. The minimal entrypoint itself doesn't use `createRequire`, but the error comes from deeper dependencies or build artifacts [[source](https://github.com/better-auth/better-auth/blob/d7125870f8926a3b1b32a00c6f1e0601f2aa640b/packages/better-auth/src/auth/minimal.ts#L1-L17)]. **Workarounds:** - Instantiate the auth client inside each request handler (not as a singleton) to avoid some initialization errors, but this won't fix unconditional Node imports [[source](https://github.com/better-auth/better-auth/issues/5413)]. - Use Cloudflare-compatible database adapters (like NeonDB with Kysely or D1), and avoid Node-only libraries [[source](https://github.com/better-auth/better-auth/issues/969#issuecomment-3235069660)]. - Try downgrading to a version before 1.4.6 (e.g., 1.3.4), or test a beta version like `1.4.6-beta.4` if available [[source](https://github.com/better-auth/better-auth/issues/6635)]. - Set `compatibility_flags = ["nodejs_compat_v2"]` and a recent `compatibility_date` in Wrangler for improved Node polyfills, but this does not guarantee better-auth compatibility [[source](https://github.com/better-auth/better-auth/issues/593)]. **Limitations:** Full Cloudflare Workers compatibility is still a work in progress. Per-request instantiation breaks CLI features and type inference, and you may need to manage schema manually or run migrations in a Node environment [[source](https://github.com/better-auth/better-auth/issues/5413)]. The maintainers are aware and plan documentation improvements, but some issues stem from dependencies not supported in Workers [[source](https://github.com/better-auth/better-auth/issues/969#issuecomment-3235069660)]. If you need robust support for Workers, keep an eye on future releases and related issues for updates. <!-- 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/a49178e2-2a10-4fc2-a21f-76f0d3cb8685?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a49178e2-2a10-4fc2-a21f-76f0d3cb8685?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a49178e2-2a10-4fc2-a21f-76f0d3cb8685?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a49178e2-2a10-4fc2-a21f-76f0d3cb8685?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a49178e2-2a10-4fc2-a21f-76f0d3cb8685?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a49178e2-2a10-4fc2-a21f-76f0d3cb8685?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a49178e2-2a10-4fc2-a21f-76f0d3cb8685?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=This%20is%20a%20known%20regression%20in%20better-auth%201.4.6%3A%20Node.js-specific%20code%20%28including%20%60createRequire%60%20and%20%60path%60%29%20is%20imported%20during%20module%20initialization%2C%20which%20Cloudflare%20Workers%20can%27t%20handle%E2%80%94even%20with%20%60nodejs_compat%60%20enabled.%20The%20error%20typically%20originates%20from%20SSO%20plugins%20or%20migration/database%20logic%20that%20expects%20Node%20primitives%2C%20causing%20the%20Worker%20to%20crash%20on%20import%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/6635%29%5D.%0A%0ADisabling%20telemetry%20or%20using%20the%20%60better-auth-cloudflare%60%20wrapper%20doesn%27t%20fully%20resolve%20this%2C%20because%20some%20Node%20modules%20are%20still%20imported%20unconditionally%20in%20affected%20versions%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/3998%29%5D.%20The%20minimal%20entrypoint%20itself%20doesn%27t%20use%20%60createRequire%60%2C%20but%20the%20error%20comes%20from%20deeper%20dependencies%20or%20build%20artifacts%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/blob/d7125870f8926a3b1b32a00c6f1e0601f2aa640b/packages/better-auth/src/auth/minimal.ts%23L1-L17%29%5D.%0A%0A%2A%2AWorkarounds%3A%2A%2A%20%20%0A-%20Instantiate%20the%20auth%20client%20inside%20each%20request%20handler%20%28not%20as%20a%20singleton%29%20to%20avoid%20some%20initialization%20errors%2C%20but%20this%20won%27t%20fix%20unconditional%20Node%20imports%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/5413%29%5D.%0A-%20Use%20Cloudflare-compatible%20database%20adapters%20%28like%20NeonDB%20with%20Kysely%20or%20D1%29%2C%20and%20avoid%20Node-only%20libraries%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/969%23issuecomment-3235069660%29%5D.%0A-%20Try%20downgrading%20to%20a%20version%20before%201.4.6%20%28e.g.%2C%201.3.4%29%2C%20or%20test%20a%20beta%20version%20like%20%601.4.6-beta.4%60%20if%20available%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/6635%29%5D.%0A-%20Set%20%60compatibility_flags%20%3D%20%5B%22nodejs_compat_v2%22%5D%60%20and%20a%20recent%20%60compatibility_date%60%20in%20Wrangler%20for%20improved%20Node%20polyfills%2C%20but%20this%20does%20not%20guarantee%20better-auth%20compatibility%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/593%29%5D.%0A%0A%2A%2ALimitations%3A%2A%2A%20%20%0AFull%20Cloudflare%20Workers%20compatibility%20is%20still%20a%20work%20in%20progress.%20Per-request%20instantiation%20breaks%20CLI%20features%20and%20type%20inference%2C%20and%20you%20may%20need%20to%20manage%20schema%20manually%20or%20run%20migrations%20in%20a%20Node%20environment%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/5413%29%5D.%20The%20maintainers%20are%20aware%20and%20plan%20documentation%20improvements%2C%20but%20some%20issues%20stem%20from%20dependencies%20not%20supported%20in%20Workers%20%5B%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/969%23issuecomment-3235069660%29%5D.%0A%0AIf%20you%20need%20robust%20support%20for%20Workers%2C%20keep%20an%20eye%20on%20future%20releases%20and%20related%20issues%20for%20updates.)&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/6665)
GiteaMirror commented 2026-04-15 18:03:44 -05:00
Author
Owner
Copy Link

@tsatsujnr139 commented on GitHub (Dec 10, 2025):

@Bekacru and @ping__ any assistance or insights would be appreciated.

<!-- gh-comment-id:3637422715 --> @tsatsujnr139 commented on GitHub (Dec 10, 2025): @Bekacru and @ping__ any assistance or insights would be appreciated.
GiteaMirror commented 2026-04-15 18:03:44 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Dec 10, 2025):

Hey @tsatsujnr139 could you try latest beta pnpm i better-auth@beta

<!-- gh-comment-id:3637675315 --> @Bekacru commented on GitHub (Dec 10, 2025): Hey @tsatsujnr139 could you try latest beta `pnpm i better-auth@beta`
GiteaMirror commented 2026-04-15 18:03:45 -05:00
Author
Owner
Copy Link

@tsatsujnr139 commented on GitHub (Dec 10, 2025):

Thank you very much, I will do that

<!-- gh-comment-id:3637917016 --> @tsatsujnr139 commented on GitHub (Dec 10, 2025): Thank you very much, I will do that
GiteaMirror commented 2026-04-15 18:03:45 -05:00
Author
Owner
Copy Link

@tsatsujnr139 commented on GitHub (Dec 10, 2025):

Hi @Bekacru heads up unfortunately that didn't resolve it.

I'll keep my eyes open and let you know if I find anything helpful as well.

<!-- gh-comment-id:3638126341 --> @tsatsujnr139 commented on GitHub (Dec 10, 2025): Hi @Bekacru heads up unfortunately that didn't resolve it. I'll keep my eyes open and let you know if I find anything helpful as well.
GiteaMirror commented 2026-04-15 18:03:46 -05:00
Author
Owner
Copy Link

@jellyton255 commented on GitHub (Dec 10, 2025):

Looks like the latest beta build has fixed this issue 👍. Thank you!

<!-- gh-comment-id:3639240174 --> @jellyton255 commented on GitHub (Dec 10, 2025): Looks like the latest beta build has fixed this issue 👍. Thank you!
GiteaMirror commented 2026-04-15 18:03:47 -05:00
Author
Owner
Copy Link

@tsatsujnr139 commented on GitHub (Dec 10, 2025):

@jellyton255 thanks for confirming... I can confirm it's fixed as well!

Lovely work as always!.

Do I go ahead to close this now?

<!-- gh-comment-id:3639288526 --> @tsatsujnr139 commented on GitHub (Dec 10, 2025): @jellyton255 thanks for confirming... I can confirm it's fixed as well! Lovely work as always!. Do I go ahead to close this now?
GiteaMirror commented 2026-04-15 18:03:47 -05:00
Author
Owner
Copy Link

@tsuyuni commented on GitHub (Dec 11, 2025):

Installing latest build (1.4.7-beta.2) fixed my issue as well, thank you.

<!-- gh-comment-id:3639480497 --> @tsuyuni commented on GitHub (Dec 11, 2025): Installing latest build (1.4.7-beta.2) fixed my issue as well, thank you.
GiteaMirror commented 2026-04-15 18:03:48 -05:00
Author
Owner
Copy Link

@illusi03 commented on GitHub (Dec 14, 2025):

Looks like the latest beta build has fixed this issue 👍. Thank you!

Really appreciate for this information. Fixed on my issue as well. Thank you.

<!-- gh-comment-id:3650311369 --> @illusi03 commented on GitHub (Dec 14, 2025): > Looks like the latest beta build has fixed this issue 👍. Thank you! Really appreciate for this information. Fixed on my issue as well. Thank you.
GiteaMirror commented 2026-04-15 18:03:49 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Jan 3, 2026):

It's related to our bundler. We have fixed this in the latest version. Please have a try :)

<!-- gh-comment-id:3706908555 --> @himself65 commented on GitHub (Jan 3, 2026): It's related to our bundler. We have fixed this in the latest version. Please have a try :)
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 bug locked
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#19221
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?