github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-24 16:11:53 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #4531] Jest Test Failures After @noble/ciphers v2.0.0 Update #18603

New Issue
Closed
opened 2026-04-15 17:08:41 -05:00 by GiteaMirror · 13 comments
GiteaMirror commented 2026-04-15 17:08:41 -05:00
Owner
Copy Link

Originally created by @koudesh3 on GitHub (Sep 8, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/4531

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Create a project with Jest (any version)
  2. Install better-auth@1.3.9
  3. Import Better Auth in a test file:
import { betterAuth } from "better-auth"
  1. Run Jest tests
  2. Observe the module loading error

Current vs. Expected behavior

Current behavior: Jest tests fail with the following error when importing Better Auth:

Cannot use import statement outside a module
  at /node_modules/@noble/ciphers/chacha.js:17
  import { createCipher, createPRG, rotl } from "./_arx.js";
  ^^^^^^

Expected behavior: Jest tests should run successfully when importing Better Auth, as they did before September 5, 2025.

What version of Better Auth are you using?

1.3.9

System info

{                                                                                                                        
       "system": {
         "platform": "darwin",
         "arch": "arm64",
         "version": "Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:29 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6000",
         "release": "24.6.0",
         "cpuCount": 8,
         "cpuModel": "Apple M1 Pro",
         "totalMemory": "16.00 GB",
         "freeMemory": "0.13 GB"
       },
       "node": {
         "version": "v23.11.0",
         "env": "development"
       },
       "packageManager": {
         "name": "npm",
         "version": "11.4.2"
       },
       "frameworks": null,
       "databases": [
         {
           "name": "better-sqlite3",
           "version": "latest"
         }
       ],
       "betterAuth": {
         "version": "1.0.0",
         "config": null
       }
     }

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

Package

Auth config (if applicable)

Additional context

The recent update to @noble/ciphers@2.0.0 (commit 9833a7ed - "chore: update jose and crypto dependencies") introduced a breaking change:

Previous: @noble/ciphers@0.6.0 supported both CommonJS and ESM
Current: @noble/ciphers@2.0.0 is ESM-only and dropped CommonJS support entirely

The Problem: Better Auth's CommonJS build (dist/crypto/index.cjs) tries to require('@noble/ciphers/chacha.js'), but Jest cannot require ESM-only modules in CommonJS environments.
Dependencies that changed:

  • @noble/ciphers: ^0.6.0 → ^2.0.0
  • @noble/hashes: ^1.8.0 → ^2.0.0
Originally created by @koudesh3 on GitHub (Sep 8, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/4531 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Create a project with Jest (any version) 2. Install `better-auth@1.3.9` 3. Import Better Auth in a test file: ``` import { betterAuth } from "better-auth" ``` 4. Run Jest tests 5. Observe the module loading error ### Current vs. Expected behavior **Current behavior:** Jest tests fail with the following error when importing Better Auth: ``` Cannot use import statement outside a module at /node_modules/@noble/ciphers/chacha.js:17 import { createCipher, createPRG, rotl } from "./_arx.js"; ^^^^^^ ``` **Expected behavior:** Jest tests should run successfully when importing Better Auth, as they did before September 5, 2025. ### What version of Better Auth are you using? 1.3.9 ### System info ```bash { "system": { "platform": "darwin", "arch": "arm64", "version": "Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:29 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6000", "release": "24.6.0", "cpuCount": 8, "cpuModel": "Apple M1 Pro", "totalMemory": "16.00 GB", "freeMemory": "0.13 GB" }, "node": { "version": "v23.11.0", "env": "development" }, "packageManager": { "name": "npm", "version": "11.4.2" }, "frameworks": null, "databases": [ { "name": "better-sqlite3", "version": "latest" } ], "betterAuth": { "version": "1.0.0", "config": null } } ``` ### Which area(s) are affected? (Select all that apply) Package ### Auth config (if applicable) ```typescript ``` ### Additional context The recent update to `@noble/ciphers@2.0.0` (commit 9833a7ed - "chore: update jose and crypto dependencies") introduced a breaking change: Previous: `@noble/ciphers@0.6.0` supported both CommonJS and ESM Current: `@noble/ciphers@2.0.0` is ESM-only and dropped CommonJS support entirely **The Problem:** Better Auth's CommonJS build (`dist/crypto/index.cjs`) tries to `require('@noble/ciphers/chacha.js')`, but Jest cannot require ESM-only modules in CommonJS environments. Dependencies that changed: - `@noble/ciphers: ^0.6.0 → ^2.0.0` - `@noble/hashes: ^1.8.0 → ^2.0.0`
GiteaMirror added the locked label 2026-04-15 17:08:41 -05:00
GiteaMirror commented 2026-04-15 17:08:43 -05:00
Author
Owner
Copy Link

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

Also this is the first time I have ever submitted an issue on an open source project, so let me know if this is wrong or I did something unclear. For context my tests worked last week, and I root caused this change with Claude Code bc a recent commit to an unrelated branch (not even touching better-auth) started failing in CI pipeline.

<!-- gh-comment-id:3267982281 --> @koudesh3 commented on GitHub (Sep 8, 2025): Also this is the first time I have ever submitted an issue on an open source project, so let me know if this is wrong or I did something unclear. For context my tests worked last week, and I root caused this change with Claude Code bc a recent commit to an unrelated branch (not even touching better-auth) started failing in CI pipeline.
GiteaMirror commented 2026-04-15 17:08:45 -05:00
Author
Owner
Copy Link

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

@dosu Hey! I dug into this a bit more and found the specific issue. Better Auth's CommonJS build in dist/crypto/index.cjs is trying to require('@noble/ciphers/chacha.js'), I believe the problem is that @noble/ciphers@2.0.0 went pure ESM and completely dropped CommonJS support?

Workaround that worked for me: I managed to get my tests working again by switching Jest to ESM mode with this config:

  module.exports = {
   preset: 'ts-jest/presets/default-esm',
   extensionsToTreatAsEsm: ['.ts'],
   transformIgnorePatterns: [
     'node_modules/(?!(better-auth|@noble))'
   ],
   globals: {
     'ts-jest': { useESM: true }
   }
  }

This tells Jest to handle Better Auth and the @noble packages as ES modules instead of trying to require() them in CommonJS
mode.

<!-- gh-comment-id:3268004543 --> @koudesh3 commented on GitHub (Sep 8, 2025): @dosu Hey! I dug into this a bit more and found the specific issue. Better Auth's CommonJS build in `dist/crypto/index.cjs` is trying to `require('@noble/ciphers/chacha.js')`, I believe the problem is that @noble/ciphers@2.0.0 went pure ESM and completely dropped CommonJS support? **Workaround that worked for me:** I managed to get my tests working again by switching Jest to ESM mode with this config: ``` module.exports = { preset: 'ts-jest/presets/default-esm', extensionsToTreatAsEsm: ['.ts'], transformIgnorePatterns: [ 'node_modules/(?!(better-auth|@noble))' ], globals: { 'ts-jest': { useESM: true } } } ``` This tells Jest to handle Better Auth and the @noble packages as ES modules instead of trying to require() them in CommonJS mode.
GiteaMirror commented 2026-04-15 17:08:46 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Sep 8, 2025):

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

You're exactly right—@noble/ciphers@2.0.0 is now ESM-only, and this breaks Better Auth's CommonJS build when used in environments like Jest that default to CommonJS. The error happens because the CommonJS build tries to require ESM-only modules, which Node and Jest can't handle without special configuration.

Your Jest config workaround (using ESM mode and transforming node_modules for better-auth and @noble) is currently the best way to resolve this for test environments. This approach is necessary because Better Auth's codebase imports @noble/ciphers using ESM syntax and doesn't provide a fallback for CommonJS consumers. The dependency update that introduced this breaking change is documented in PR #4433, which also notes the new Node.js version requirements.

For others running into this: either use a Jest ESM preset as shown above, or ensure your Node.js version is 20.19.0+ (or 22.12.0+/23.0.0+) to get better ESM interop, but Jest will still need ESM config tweaks. There isn't an official alternative workaround or codebase fix at this time—your solution is the recommended path for now.

If you need more background, see the related issue about ESM errors in CommonJS projects.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

<!-- gh-comment-id:3268017952 --> @dosubot[bot] commented on GitHub (Sep 8, 2025): <!-- Greeting --> Hi @koudesh3! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the better-auth team. <!-- Answer --> You're exactly right—@noble/ciphers@2.0.0 is now ESM-only, and this breaks Better Auth's CommonJS build when used in environments like Jest that default to CommonJS. The error happens because the CommonJS build tries to require ESM-only modules, which Node and Jest can't handle without special configuration. Your Jest config workaround (using ESM mode and transforming node_modules for better-auth and @noble) is currently the best way to resolve this for test environments. This approach is necessary because Better Auth's codebase imports @noble/ciphers using ESM syntax and doesn't provide a fallback for CommonJS consumers. The dependency update that introduced this breaking change is documented in [PR #4433](https://github.com/better-auth/better-auth/pull/4433), which also notes the new Node.js version requirements. For others running into this: either use a Jest ESM preset as shown above, or ensure your Node.js version is 20.19.0+ (or 22.12.0+/23.0.0+) to get better ESM interop, but Jest will still need ESM config tweaks. There isn't an official alternative workaround or codebase fix at this time—your solution is the recommended path for now. If you need more background, see the related [issue about ESM errors in CommonJS projects](https://github.com/better-auth/better-auth/issues/3260). <!-- 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/a811e276-2301-4a08-a880-f9cbb79cdc3a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a811e276-2301-4a08-a880-f9cbb79cdc3a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a811e276-2301-4a08-a880-f9cbb79cdc3a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a811e276-2301-4a08-a880-f9cbb79cdc3a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a811e276-2301-4a08-a880-f9cbb79cdc3a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a811e276-2301-4a08-a880-f9cbb79cdc3a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a811e276-2301-4a08-a880-f9cbb79cdc3a?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&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/4531)
GiteaMirror commented 2026-04-15 17:08:49 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Sep 11, 2025):

Node.js 23.11.0 is not a stable version. I believe that the latest Node.js supports load ESM in the CJS module.

<!-- gh-comment-id:3282393636 --> @himself65 commented on GitHub (Sep 11, 2025): Node.js 23.11.0 is not a stable version. I believe that the latest Node.js supports load ESM in the CJS module.
GiteaMirror commented 2026-04-15 17:08:50 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Sep 11, 2025):

Related: https://github.com/nodejs/node/pull/51977

<!-- gh-comment-id:3282400713 --> @himself65 commented on GitHub (Sep 11, 2025): Related: https://github.com/nodejs/node/pull/51977
GiteaMirror commented 2026-04-15 17:08:50 -05:00
Author
Owner
Copy Link

@alan345 commented on GitHub (Sep 15, 2025):

after upgrading from "better-auth": "^1.2.10" to "better-auth": "^1.3.9", it works in localhost, but not when i deploy in render.com

Here you have the full error:

==> Uploading build...
==> Uploaded in 5.1s. Compression took 5.2s
==> Build successful 🎉
==> Deploying...
==> Running 'npm run start:server'
> start:server
> npm run start -w server
> start
> node dist/index.js
/opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs:315
undefined
             ^
Error [ERR_REQUIRE_ESM]: require() of ES Module /opt/render/project/src/node_modules/@noble/ciphers/chacha.js from /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs not supported.
Instead change the require of chacha.js in /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs to a dynamic import() which is available in all CommonJS modules.
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at Object.<anonymous> (/opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs:4:19) {
  code: 'ERR_REQUIRE_ESM'
}
Node.js v22.11.0
npm error Lifecycle script `start` failed with error:
npm error code 1
npm error path /opt/render/project/src/server
npm error workspace @fsb/server
npm error location /opt/render/project/src/server
npm error command failed
npm error command sh -c node dist/index.js
==> Exited with status 1
==> Common ways to troubleshoot your deploy: https://render.com/docs/troubleshooting-deploys
==> Running 'npm run start:server'
> start:server
> npm run start -w server
> start
> node dist/index.js
/opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs:315
undefined
             ^
Error [ERR_REQUIRE_ESM]: require() of ES Module /opt/render/project/src/node_modules/@noble/ciphers/chacha.js from /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs not supported.
Instead change the require of chacha.js in /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs to a dynamic import() which is available in all CommonJS modules.
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at Object.<anonymous> (/opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs:4:19) {
  code: 'ERR_REQUIRE_ESM'
}
Node.js v22.11.0
npm error Lifecycle script `start` failed with error:
npm error code 1
npm error path /opt/render/project/src/server
npm error workspace @fsb/server
npm error location /opt/render/project/src/server
npm error command failed
npm error command sh -c node dist/index.js
<!-- gh-comment-id:3293128722 --> @alan345 commented on GitHub (Sep 15, 2025): after upgrading from `"better-auth": "^1.2.10"` to `"better-auth": "^1.3.9"`, it works in localhost, but not when i deploy in `render.com` Here you have the full error: ``` ==> Uploading build... ==> Uploaded in 5.1s. Compression took 5.2s ==> Build successful 🎉 ==> Deploying... ==> Running 'npm run start:server' > start:server > npm run start -w server > start > node dist/index.js /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs:315 undefined ^ Error [ERR_REQUIRE_ESM]: require() of ES Module /opt/render/project/src/node_modules/@noble/ciphers/chacha.js from /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs not supported. Instead change the require of chacha.js in /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs to a dynamic import() which is available in all CommonJS modules. at TracingChannel.traceSync (node:diagnostics_channel:315:14) at Object.<anonymous> (/opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs:4:19) { code: 'ERR_REQUIRE_ESM' } Node.js v22.11.0 npm error Lifecycle script `start` failed with error: npm error code 1 npm error path /opt/render/project/src/server npm error workspace @fsb/server npm error location /opt/render/project/src/server npm error command failed npm error command sh -c node dist/index.js ==> Exited with status 1 ==> Common ways to troubleshoot your deploy: https://render.com/docs/troubleshooting-deploys ==> Running 'npm run start:server' > start:server > npm run start -w server > start > node dist/index.js /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs:315 undefined ^ Error [ERR_REQUIRE_ESM]: require() of ES Module /opt/render/project/src/node_modules/@noble/ciphers/chacha.js from /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs not supported. Instead change the require of chacha.js in /opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs to a dynamic import() which is available in all CommonJS modules. at TracingChannel.traceSync (node:diagnostics_channel:315:14) at Object.<anonymous> (/opt/render/project/src/node_modules/better-auth/dist/crypto/index.cjs:4:19) { code: 'ERR_REQUIRE_ESM' } Node.js v22.11.0 npm error Lifecycle script `start` failed with error: npm error code 1 npm error path /opt/render/project/src/server npm error workspace @fsb/server npm error location /opt/render/project/src/server npm error command failed npm error command sh -c node dist/index.js ```
GiteaMirror commented 2026-04-15 17:08:51 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Sep 15, 2025):

22.11.0 doesn't support it by default. You might need --experimental-require-module I think

<!-- gh-comment-id:3293140868 --> @himself65 commented on GitHub (Sep 15, 2025): 22.11.0 doesn't support it by default. You might need `--experimental-require-module` I think
GiteaMirror commented 2026-04-15 17:08:52 -05:00
Author
Owner
Copy Link

@koudesh3 commented on GitHub (Sep 15, 2025):

Node.js 23.11.0 is not a stable version. I believe that the latest Node.js supports load ESM in the CJS module.

Thank you!!

<!-- gh-comment-id:3294060314 --> @koudesh3 commented on GitHub (Sep 15, 2025): > Node.js 23.11.0 is not a stable version. I believe that the latest Node.js supports load ESM in the CJS module. Thank you!!
GiteaMirror commented 2026-04-15 17:08:53 -05:00
Author
Owner
Copy Link

@OscarCornish commented on GitHub (Sep 30, 2025):

For anyone whom comes across this using pnpm, the solution from koudesh3 worked for me, but after tweaking to allow for pnpms node_modules structure:

{
  ...
  transformIgnorePatterns: ["/node_modules/(?!.*(better-auth|@noble)/)"],
  ...
}
<!-- gh-comment-id:3353262573 --> @OscarCornish commented on GitHub (Sep 30, 2025): For anyone whom comes across this **using pnpm**, the solution from koudesh3 worked for me, but after tweaking to allow for pnpms node_modules structure: ```js { ... transformIgnorePatterns: ["/node_modules/(?!.*(better-auth|@noble)/)"], ... } ```
GiteaMirror commented 2026-04-15 17:08:53 -05:00
Author
Owner
Copy Link

@Wellshh commented on GitHub (Nov 6, 2025):

Thanks for @koudesh3's solution, it worked out fine for me.
For anyone who has the same problem with jest version 29 or later, jest may output
(WARN) Define `ts-jest` config under `globals` is deprecated. Please do transform: { <transform_regex>: ['ts-jest', { /* ts-jest config goes here in Jest */ }], },, just do as it suggested and replace the global part with this: transform {'^.+\\.(t|j)s$':['ts-jest', {useESM: true}]}.

As an alternative solution, instead of configuring jest and ts-jest to use ESM mode, try the config here: https://github.com/jestjs/jest/issues/15275#issuecomment-2495971960. It basically ask ts-jest to transform all pure ESM packages to CJS:).

<!-- gh-comment-id:3497061847 --> @Wellshh commented on GitHub (Nov 6, 2025): Thanks for @koudesh3's solution, it worked out fine for me. For anyone who has the same problem with jest version 29 or later, jest may output ```(WARN) Define `ts-jest` config under `globals` is deprecated. Please do transform: { <transform_regex>: ['ts-jest', { /* ts-jest config goes here in Jest */ }], },```, just do as it suggested and replace the global part with this: `transform {'^.+\\.(t|j)s$':['ts-jest', {useESM: true}]}`. As an alternative solution, instead of configuring jest and ts-jest to use ESM mode, try the config here: https://github.com/jestjs/jest/issues/15275#issuecomment-2495971960. It basically ask ts-jest to transform all pure ESM packages to CJS:).
GiteaMirror commented 2026-04-15 17:08:54 -05:00
Author
Owner
Copy Link

@Drischdaan commented on GitHub (Jan 21, 2026):

I am having the same issue in a nestjs project, but with an other package:

node_modules/.pnpm/better-auth@1.4.16_@prisma+client@7.2.0_prisma@7.2.0_@types+react@19.2.9_react-dom@19.2_81191c1fa7c8d926ad08a18f97a7ee66/node_modules/better-auth/dist/integrations/node.mjs:1
({"Object.":function(module,exports,require,__dirname,__filename,jest){import { toNodeHandler as toNodeHandler$1 } from "better-call/node";

I tried using @OscarCornish fix, but that doesn't work

<!-- gh-comment-id:3777236463 --> @Drischdaan commented on GitHub (Jan 21, 2026): I am having the same issue in a nestjs project, but with an other package: node_modules/.pnpm/better-auth@1.4.16_@prisma+client@7.2.0_prisma@7.2.0_@types+react@19.2.9_react-dom@19.2_81191c1fa7c8d926ad08a18f97a7ee66/node_modules/better-auth/dist/integrations/node.mjs:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { toNodeHandler as toNodeHandler$1 } from "better-call/node"; I tried using @OscarCornish fix, but that doesn't work
GiteaMirror commented 2026-04-15 17:08:55 -05:00
Author
Owner
Copy Link

@OscarCornish commented on GitHub (Jan 21, 2026):

@Drischdaan Not sure what has changed in recent versions that might break my fix, but I ended up moving our project to use Vitest, which worked with no issues. If you have the capacity, I'd recommend it.

Otherwise, I think I setup a test file with just the better-auth import, then I was checking the jest output to see which modules weren't getting transformed properly, and adding them to the regex

<!-- gh-comment-id:3777274016 --> @OscarCornish commented on GitHub (Jan 21, 2026): @Drischdaan Not sure what has changed in recent versions that might break my fix, but I ended up moving our project to use Vitest, which worked with no issues. If you have the capacity, I'd recommend it. Otherwise, I think I setup a test file with just the better-auth import, then I was checking the jest output to see which modules weren't getting transformed properly, and adding them to the regex
GiteaMirror commented 2026-04-15 17:08:56 -05:00
Author
Owner
Copy Link

@Drischdaan commented on GitHub (Jan 21, 2026):

EDIT:
Switching to vitest fixed the issues. Thanks for the help

Original Comment:
@OscarCornish I created just a file with the import and added all the packages to the list. This is my jest config:

{
  "preset": "ts-jest/presets/default-esm",
  "moduleFileExtensions": ["js", "json", "ts"],
  "rootDir": ".",
  "testRegex": ".e2e-spec.ts$",
  "setupFilesAfterEnv": ["./setup.e2e.ts"],
  "transform": {
    "^.+\\.(t|j)s$": ["ts-jest", { "useESM": true }]
  },
  "extensionsToTreatAsEsm": [".ts"],
  "transformIgnorePatterns": [
    "/node_modules/(?!.*(better-auth|@noble|@thallesp)/)"
  ]
}

And that's the console output:

node_modules/.pnpm/better-auth@1.4.16_@prisma+client@7.2.0_prisma@7.2.0_@types+react@19.2.9_react-dom@19.2_81191c1fa7c8d926ad08a18f97a7ee66/node_modules/better-auth/dist/index.mjs:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { generateState, parseState } from "./oauth2/state.mjs";
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module
<!-- gh-comment-id:3777662141 --> @Drischdaan commented on GitHub (Jan 21, 2026): **EDIT:** Switching to vitest fixed the issues. Thanks for the help **Original Comment:** @OscarCornish I created just a file with the import and added all the packages to the list. This is my jest config: ```json { "preset": "ts-jest/presets/default-esm", "moduleFileExtensions": ["js", "json", "ts"], "rootDir": ".", "testRegex": ".e2e-spec.ts$", "setupFilesAfterEnv": ["./setup.e2e.ts"], "transform": { "^.+\\.(t|j)s$": ["ts-jest", { "useESM": true }] }, "extensionsToTreatAsEsm": [".ts"], "transformIgnorePatterns": [ "/node_modules/(?!.*(better-auth|@noble|@thallesp)/)" ] } ``` And that's the console output: ``` node_modules/.pnpm/better-auth@1.4.16_@prisma+client@7.2.0_prisma@7.2.0_@types+react@19.2.9_react-dom@19.2_81191c1fa7c8d926ad08a18f97a7ee66/node_modules/better-auth/dist/index.mjs:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { generateState, parseState } from "./oauth2/state.mjs"; ^^^^^^ SyntaxError: Cannot use import statement outside a module ```
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 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#18603
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?