[GH-ISSUE #5954] 客户端引用authClient方法报错Failed to fetch dynamically imported module: http://localhost:5173/src/routes/index.tsx?tsr-split=component #19016

New Issue

2026-04-15T17:47:11-05:00

GiteaMirror commented

2026-04-15 17:47:11 -05:00

Originally created by @Rvvvv1 on GitHub (Nov 13, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/5954

Is this suited for github?

Yes, this is suited for github

To Reproduce

后端hono 使用 "better-auth": "^1.3.9", "hono": "^4.10.2", 前端使用vite 构建tanstack-router模版里面使用authClient方法报错控制台显示bun dev
$ concurrently "bun client" "bun server"
[0] $ cd client && bun dev
[1] $ bun run --hot server/index.ts
[0] $ vite --port 5173
[1] Started development server: http://localhost:3000
[0]
[0] VITE v7.2.2 ready in 377 ms
[0]
[0] ➜ Local: http://localhost:5173/
[0] ➜ Network: use --host to expose
[0] ✘ [ERROR] Could not resolve "react"
[0]
[0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58:
[0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react';
[0] ╵ ~~~~~~~
[0]
[0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
[0]
[0] 13:42:09 [vite] (client) error while updating dependencies:
[0] Error: Error during dependency optimization:
[0]
[0] ✘ [ERROR] Could not resolve "react"
[0]
[0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58:
[0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react';
[0] ╵ ~~~~~~~
[0]
[0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
[0]
[0]
[0] at failureErrorWithLog (/Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467:15)
[0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:926:25
[0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1345:9
[0] at process.processTicksAndRejections (node:internal/process/task_queues:105:5)。

vite配置如下
import { defineConfig } from "vite";
import { devtools } from "@tanstack/devtools-vite";
import viteReact from "@vitejs/plugin-react";
import tailwindcss from "@tailwindcss/vite";

import { tanstackRouter } from "@tanstack/router-plugin/vite";
import { fileURLToPath, URL } from "node:url";

// https://vitejs.dev/config/
export default defineConfig({
plugins: [
devtools(),
tanstackRouter({
target: "react",
autoCodeSplitting: true,
}),
viteReact(),
tailwindcss(),
],
resolve: {
alias: {
"@": fileURLToPath(new URL("./src", import.meta.url)),
},
},
server: {
proxy: {
"/api": {
target: "http://localhost:3000",
changeOrigin: true,
},
},
},
});

使用 "@biomejs/biome": "2.2.4",
"@tanstack/devtools-vite": "^0.3.11",
"@testing-library/dom": "^10.4.0",
"@testing-library/react": "^16.2.0",
"@types/node": "^22.10.2",
"@types/react": "^19.2.0",
"@types/react-dom": "^19.2.0",
"@vitejs/plugin-react": "^5.0.4",
"jsdom": "^27.0.0",
"typescript": "^5.7.2",
"vite": "^7.1.7",
"vitest": "^3.0.5",
"web-vitals": "^5.1.0"

Current vs. Expected behavior

只要当我在前端项目里面下载了better-auth 这些报错就消失了

What version of Better Auth are you using?

1.3.34

System info

"vite": "^7.1.7",
  "better-auth": "^1.3.34",

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

Client

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
});

Additional context

No response

Originally created by @Rvvvv1 on GitHub (Nov 13, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/5954 ### Is this suited for github? - [ ] Yes, this is suited for github ### To Reproduce 后端hono 使用 "better-auth": "^1.3.9", "hono": "^4.10.2", 前端使用vite 构建tanstack-router模版里面使用authClient方法报错控制台显示bun dev $ concurrently "bun client" "bun server" [0] $ cd client && bun dev [1] $ bun run --hot server/index.ts [0] $ vite --port 5173 [1] Started development server: http://localhost:3000 [0] [0] VITE v7.2.2 ready in 377 ms [0] [0] ➜ Local: http://localhost:5173/ [0] ➜ Network: use --host to expose [0] ✘ [ERROR] Could not resolve "react" [0] [0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58: [0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react'; [0] ╵ ~~~~~~~ [0] [0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. [0] [0] 13:42:09 [vite] (client) error while updating dependencies: [0] Error: Error during dependency optimization: [0] [0] ✘ [ERROR] Could not resolve "react" [0] [0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58: [0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react'; [0] ╵ ~~~~~~~ [0] [0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. [0] [0] [0] at failureErrorWithLog (/Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467:15) [0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:926:25 [0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1345:9 [0] at process.processTicksAndRejections (node:internal/process/task_queues:105:5)。 vite配置如下 import { defineConfig } from "vite"; import { devtools } from "@tanstack/devtools-vite"; import viteReact from "@vitejs/plugin-react"; import tailwindcss from "@tailwindcss/vite"; import { tanstackRouter } from "@tanstack/router-plugin/vite"; import { fileURLToPath, URL } from "node:url"; // https://vitejs.dev/config/ export default defineConfig({ plugins: [ devtools(), tanstackRouter({ target: "react", autoCodeSplitting: true, }), viteReact(), tailwindcss(), ], resolve: { alias: { "@": fileURLToPath(new URL("./src", import.meta.url)), }, }, server: { proxy: { "/api": { target: "http://localhost:3000", changeOrigin: true, }, }, }, }); 使用 "@biomejs/biome": "2.2.4", "@tanstack/devtools-vite": "^0.3.11", "@testing-library/dom": "^10.4.0", "@testing-library/react": "^16.2.0", "@types/node": "^22.10.2", "@types/react": "^19.2.0", "@types/react-dom": "^19.2.0", "@vitejs/plugin-react": "^5.0.4", "jsdom": "^27.0.0", "typescript": "^5.7.2", "vite": "^7.1.7", "vitest": "^3.0.5", "web-vitals": "^5.1.0" ### Current vs. Expected behavior 只要当我在前端项目里面下载了better-auth 这些报错就消失了 ### What version of Better Auth are you using? 1.3.34 ### System info ```bash "vite": "^7.1.7", "better-auth": "^1.3.34", ``` ### Which area(s) are affected? (Select all that apply) Client ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, }); ``` ### Additional context _No response_

GiteaMirror added the locked label 2026-04-15 17:47:11 -05:00

GiteaMirror closed this issue

2026-04-15 17:47:12 -05:00

GiteaMirror commented

2026-04-15 17:47:13 -05:00

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

It appears your bundler is failing to resolve React because the Better Auth client expects React to be available as a peer dependency. In your Vite-powered project, even though you’re using Tanstack Router and other dependencies, you’ll need to install both react and react-dom so that the client module for Better Auth can import the hooks it depends on. For example, try running:

npm install react react-dom

Then, restart your dev server. This should allow Vite to properly resolve the import from Better Auth’s client module. Also, you might consider checking your Vite configuration to ensure there are no conflicting alias settings or externalized modules that might inadvertently exclude React from the build [1].

Tag @better-auth-agent if you would like an answer from the Agent. Do you have any additional details or configuration aspects you’d like to go over?

Diagram • Discord • GitHub

@better-auth-agent[bot] commented on GitHub (Nov 13, 2025): It appears your bundler is failing to resolve React because the Better Auth client expects React to be available as a peer dependency. In your Vite-powered project, even though you’re using Tanstack Router and other dependencies, you’ll need to install both react and react-dom so that the client module for Better Auth can import the hooks it depends on. For example, try running: npm install react react-dom Then, restart your dev server. This should allow Vite to properly resolve the import from Better Auth’s client module. Also, you might consider checking your Vite configuration to ensure there are no conflicting alias settings or externalized modules that might inadvertently exclude React from the build [[1]](https://github.com/better-auth/better-auth/issues/4125). Tag @better-auth-agent if you would like an answer from the Agent. Do you have any additional details or configuration aspects you’d like to go over?  [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)

GiteaMirror commented

2026-04-15 17:47:15 -05:00

@Rvvvv1 commented on GitHub (Nov 13, 2025):

❯ bun add react react-dom
bun add v1.3.0 (b0a6feca)

installed react@19.2.0
installed react-dom@19.2.0
❯ bun dev
$ concurrently "bun client" "bun server"
[0] $ cd client && bun dev
[1] $ bun run --hot server/index.ts
[0] $ vite --port 5173
[1] Started development server: http://localhost:3000
[0]
[0] VITE v7.2.2 ready in 351 ms
[0]
[0] ➜ Local: http://localhost:5173/
[0] ➜ Network: use --host to expose
[0] ✘ [ERROR] Could not resolve "react"
[0]
[0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58:
[0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react';
[0] ╵ ~~~~~~~
[0]
[0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
[0]
[0] /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467
[0] let error = new Error(text);
[0] ^
[0]
[0] Error: Error during dependency optimization:
[0]
[0] ✘ [ERROR] Could not resolve "react"
[0]
[0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58:
[0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react';
[0] ╵ ~~~~~~~
[0]
[0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
[0]
[0]
[0] at failureErrorWithLog (/Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467:15)
[0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:926:25
[0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1345:9
[0] at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[0] errors: [Getter/Setter],
[0] warnings: [Getter/Setter]
[0] }
[0]
[0] Node.js v24.9.0
[0] error: script "dev" exited with code 1
[0] error: script "client" exited with code 1
[0] bun client exited with code 1

并没有解决 @better-auth-agent

@Rvvvv1 commented on GitHub (Nov 13, 2025): ❯ bun add react react-dom bun add v1.3.0 (b0a6feca) installed react@19.2.0 installed react-dom@19.2.0 ❯ bun dev $ concurrently "bun client" "bun server" [0] $ cd client && bun dev [1] $ bun run --hot server/index.ts [0] $ vite --port 5173 [1] Started development server: http://localhost:3000 [0] [0] VITE v7.2.2 ready in 351 ms [0] [0] ➜ Local: http://localhost:5173/ [0] ➜ Network: use --host to expose [0] ✘ [ERROR] Could not resolve "react" [0] [0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58: [0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react'; [0] ╵ ~~~~~~~ [0] [0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. [0] [0] /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467 [0] let error = new Error(text); [0] ^ [0] [0] Error: Error during dependency optimization: [0] [0] ✘ [ERROR] Could not resolve "react" [0] [0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58: [0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react'; [0] ╵ ~~~~~~~ [0] [0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. [0] [0] [0] at failureErrorWithLog (/Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467:15) [0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:926:25 [0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1345:9 [0] at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { [0] errors: [Getter/Setter], [0] warnings: [Getter/Setter] [0] } [0] [0] Node.js v24.9.0 [0] error: script "dev" exited with code 1 [0] error: script "client" exited with code 1 [0] bun client exited with code 1 并没有解决 @better-auth-agent

GiteaMirror commented

2026-04-15 17:47:15 -05:00

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

Hi there! It looks like your bundler is having trouble resolving the "react" module when importing Better Auth’s client/react entry. This usually happens when the bundler (esbuild/Vite in your case) isn’t correctly handling the peer dependency. Here are a few steps you could try:

• First, double-check that react and react-dom are correctly installed in your front-end project and are listed as dependencies rather than only devDependencies. This ensures they’re available during bundling [1].
• In your vite.config.js, try adding a resolve.dedupe or optimizeDeps configuration to force Vite to properly consolidate your react dependency. For example, you could add:
resolve: { dedupe: ["react"] }
optimizeDeps: { include: ["react", "react-dom"] }
This helps Vite avoid multiple copies or mis-resolution of react [2].
• Alternatively, you might mark "react" as external in your Vite config’s optimizeDeps.external options (as your error message suggests) so it isn’t bundled by esbuild.
• Since you’re using Bun along with Vite, also verify that Bun’s module resolution isn’t interfering—sometimes switching the bundler’s configuration or updating to a more recent version can help.

Do these steps resolve your issue? Tag @better-auth-agent if you would like an answer from the Agent.

Diagram • Discord • GitHub

@better-auth-agent[bot] commented on GitHub (Nov 13, 2025): Hi there! It looks like your bundler is having trouble resolving the "react" module when importing Better Auth’s client/react entry. This usually happens when the bundler (esbuild/Vite in your case) isn’t correctly handling the peer dependency. Here are a few steps you could try: • First, double-check that react and react-dom are correctly installed in your front-end project and are listed as dependencies rather than only devDependencies. This ensures they’re available during bundling [[1]](https://github.com/better-auth/better-auth/issues/4125). • In your vite.config.js, try adding a resolve.dedupe or optimizeDeps configuration to force Vite to properly consolidate your react dependency. For example, you could add: resolve: { dedupe: ["react"] } optimizeDeps: { include: ["react", "react-dom"] } This helps Vite avoid multiple copies or mis-resolution of react [[2]](https://github.com/better-auth/better-auth/issues/4386). • Alternatively, you might mark "react" as external in your Vite config’s optimizeDeps.external options (as your error message suggests) so it isn’t bundled by esbuild. • Since you’re using Bun along with Vite, also verify that Bun’s module resolution isn’t interfering—sometimes switching the bundler’s configuration or updating to a more recent version can help. Do these steps resolve your issue? Tag @better-auth-agent if you would like an answer from the Agent.  [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)

GiteaMirror commented

2026-04-15 17:47:16 -05:00

@Rvvvv1 commented on GitHub (Nov 13, 2025):

@better-auth-agent vite 构建客户端实例就是会报错无法解决] VITE v7.2.2 ready in 100 ms
[0]
[0] ➜ Local: http://localhost:5173/
[0] ➜ Network: use --host to expose
[0] ✘ [ERROR] Could not resolve "react"
[0]
[0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58:
[0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react';
[0] ╵ ~~~~~~~
[0]
[0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
[0]
[0] /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467
[0] let error = new Error(text);
[0] ^
[0]
[0] Error: Error during dependency optimization:
[0]
[0] ✘ [ERROR] Could not resolve "react"
[0]
[0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58:
[0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react';
[0] ╵ ~~~~~~~
[0]
[0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
[0]
[0]
[0] at failureErrorWithLog (/Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467:15)
[0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:926:25
[0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1345:9
[0] at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[0] errors: [Getter/Setter],
[0] warnings: [Getter/Setter]
[0] }
[0]
[0] Node.js v24.9.0
[0] error: script "dev" exited with code 1
[0] error: script "client" exited with code 1
[0] bun client exited with code 1
^C[1] bun server exited with code SIGINT
error: script "dev" exited with code 1

@Rvvvv1 commented on GitHub (Nov 13, 2025): @better-auth-agent vite 构建客户端实例就是会报错无法解决] VITE v7.2.2 ready in 100 ms [0] [0] ➜ Local: http://localhost:5173/ [0] ➜ Network: use --host to expose [0] ✘ [ERROR] Could not resolve "react" [0] [0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58: [0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react'; [0] ╵ ~~~~~~~ [0] [0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. [0] [0] /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467 [0] let error = new Error(text); [0] ^ [0] [0] Error: Error during dependency optimization: [0] [0] ✘ [ERROR] Could not resolve "react" [0] [0] ../node_modules/better-auth/dist/client/react/index.mjs:3:58: [0] 3 │ import { useRef, useCallback, useSyncExternalStore } from 'react'; [0] ╵ ~~~~~~~ [0] [0] You can mark the path "react" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. [0] [0] [0] at failureErrorWithLog (/Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1467:15) [0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:926:25 [0] at /Users/binlee/Desktop/tank/shadcn-admin/client/node_modules/esbuild/lib/main.js:1345:9 [0] at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { [0] errors: [Getter/Setter], [0] warnings: [Getter/Setter] [0] } [0] [0] Node.js v24.9.0 [0] error: script "dev" exited with code 1 [0] error: script "client" exited with code 1 [0] bun client exited with code 1 ^C[1] bun server exited with code SIGINT error: script "dev" exited with code 1

GiteaMirror commented

2026-04-15 17:47:18 -05:00

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

Hi, thanks for reporting this issue! It looks like Vite is trying to resolve the React dependency from better-auth’s client/react module but can’t find it. This typically happens when your client project doesn’t have React installed as a direct dependency. One step that has resolved similar issues is to install both react and react-dom in your frontend project. Alternatively, you might consider configuring Vite to mark "react" as external so that the bundler doesn’t try to include it from better-auth.

Could you please check if installing React in the client project or updating your Vite configuration resolves the issue? tag @better-auth-agent if you would like an answer from the Agent.

Diagram • Discord • GitHub

@better-auth-agent[bot] commented on GitHub (Nov 13, 2025): Hi, thanks for reporting this issue! It looks like Vite is trying to resolve the React dependency from better-auth’s client/react module but can’t find it. This typically happens when your client project doesn’t have React installed as a direct dependency. One step that has resolved similar issues is to install both react and react-dom in your frontend project. Alternatively, you might consider configuring Vite to mark "react" as external so that the bundler doesn’t try to include it from better-auth. Could you please check if installing React in the client project or updating your Vite configuration resolves the issue? tag @better-auth-agent if you would like an answer from the Agent.  [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)

GiteaMirror commented

2026-04-15 17:47:18 -05:00

@himself65 commented on GitHub (Nov 13, 2025):

只要当我在前端项目里面下载了better-auth 这些报错就消失了

我觉得是你node_modules依赖有问题，听起来像是monorepo，我觉得这并不是better-auth的问题。

@himself65 commented on GitHub (Nov 13, 2025): > 只要当我在前端项目里面下载了better-auth 这些报错就消失了我觉得是你node_modules依赖有问题，听起来像是monorepo，我觉得这并不是better-auth的问题。

Sign in to join this conversation.

Branches Tags

changeset-release/main

main

2026-09-01/refactor/type-safe-vue-session-fetch

2026-09-01/fix/nuxt-session-hydration

2026-08-31/ci/adopt-shared-ci-tooling

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-81cd09af96

dependabot/github_actions/github-actions-49d71e140c

2026-08-27/docs/add-markdown-routes

2026-08-27/refactor/share-api-method-rendering

2026-08-26/feat/versioned-docs

feat/adapter-migration-boundary

v1.6.x

feat/account-identity-plan-reporting

2026-08-19/fix/mysql-disabled-index-introspection

2026-08-18/refactor/simplify-cloudflare-fixture

2026-08-19/ci/stabilize-mssql-startup

starsling/drizzle-kit-push-util

docs/1-7-release

2026-08-14/fix/standardize-plugin-types

2026-08-13/fix/dpop-public-url

2026-08-13/fix/acr-values-voluntary

starsling/CHG-forget-processed-cleanup-rows-b8077b74ef9a-4971f8e41755

refactor/device-authorization-oauth-boundary

2026-08-11/fix/api-key-rate-limit-window

feat/oauth-provider-custom-subject

pr-9793-merge

2026-07-31/chore/bump-better-call

2026-07-30/chore/upgrade-better-call

2026-07-30/fix/nextjs-rsc-session-refresh

2026-07-29/refactor/centralize-placeholder-email-generation

refactor/oauth-client-application-type

2026-07-28/fix/anonymous-oauth-proxy-linking

feat/agent-feedback-endpoint

fix/oauth-provider-session-deletion

feat/scim-demo-workflow

feat/scim-active-user-link

feat/sso-provider-user-resolution

feat/identity-provider-accounts

feat/oauth-provider-remove-silence-warnings

changeset-release/release/vercel-announcement

release/vercel-announcement

2026-06-29/docs/optimize-og-images

feat/yandex-social-provider

feat/ssrf-fetch-boundary

codex/pr-10225-next-comments

fix/phone-number-disable-input

perf/router-build-once

fix/oauth-user-provisioning-fields

codex/ignore-compose-override-spellcheck

2026-06-19/fix/stripe-org-reference-scope

feat/webhooks

feat/baseurl-canonical-serving-split

feat/magic-link-expires-in

fix/esbuild-security-bump

chore/sync-main-to-next-20260615

chore/revert-10053

codex/fix-expo-sdk56-dynamic-import

refactor/oauth-provider-client-authentication-module

fix/oauth-no-store-headers

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

local/fix-invite-accept-idempotency

docs/beta-mdx-component-fallback

fix/dependabot-hono-shell-quote

codex/stateless-account-cookie-resolution

fix/admin-create-user-role-escalation

feat/oauth-provider-oidc-acr

refactor/sign-in-challenges

refactor/optional-kysely-dependency

2026-06-06/chore/kysely-changeset

copilot/fix-code-review-comment

starsling/prisma-migration-reset

2026-06-02/fix/next-cookies-defer-rsc

feat/oauth-contribution-protocol

ping-maxwell/c-ping-maxwell/fix-kysely-adapter-core-utils-string-resolution-68c5

temp/server-only-test

2026-05-31/refactor/kysely-joins-json-helpers

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

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

fix/oauth-callback-path-declarative

2026-05-31/fix/sqlite-dialect-affected-rows

fix/next-cookie-separator

2026-05-29/fix/last-login-method-cookie-prefix

ping-maxwell/c-ping-maxwell/fix-error-link-apostrophe-f89a

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

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

fix/i18n-before-hook-translation

fix/disable-migration-generate

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

2026-05-10/feat/hooks-finally

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

2026-05-09/feat/hooks-finally

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

fix/stripe/subscription-data-merge

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

chore/pnpm-v11

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-idp-initiated-bounce

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

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

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-20/docs/improve-website

v1.5.x

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-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#19016

[GH-ISSUE #5954] 客户端引用authClient方法 报错Failed to fetch dynamically imported module: http://localhost:5173/src/routes/index.tsx?tsr-split=component #19016

Is this suited for github?

To Reproduce

Current vs. Expected behavior

What version of Better Auth are you using?

System info

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

Auth config (if applicable)

Additional context

[GH-ISSUE #5954] 客户端引用authClient方法报错Failed to fetch dynamically imported module: http://localhost:5173/src/routes/index.tsx?tsr-split=component #19016