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

[GH-ISSUE #2908] @better-auth/cli fails to satisfy or propagate the peer dependecy @babel/core #26714

New Issue
Closed
opened 2026-04-17 17:22:01 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-17 17:22:01 -05:00
Owner
Copy Link

Originally created by @NormalGaussian on GitHub (Jun 4, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2908

Issue

My original error; cleaned by redacting my local directories with {projectRoot}:

When attempting to run yarn dlx @better-auth/cli generate --config {configFile}, this error is eventually presented:

{projectRoot}/.pnp.cjs:12208
      Error.captureStackTrace(firstError);
            ^

Error: @babel/helper-create-class-features-plugin tried to access @babel/core (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

Required package: @babel/core
Required by: @babel/helper-create-class-features-plugin@virtual:868dbcd5ddfd0f02c5e350de117637169db0c200f336100146606f4c388b20ddf15a57a2b338a562d4c472c00f366c24fc91b7e42a001e5e065850baf67e2b20#npm:7.27.1 (via {projectRoot}/.yarn/__virtual__/@babel-helper-create-class-features-plugin-virtual-9d8cf8d8bf/0/cache/@babel-helper-create-class-features-plugin-npm-7.27.1-65d3087eb1-701579b490.zip/node_modules/@babel/helper-create-class-features-plugin/lib/)

Ancestor breaking the chain: @better-auth/cli@npm:1.2.8


Require stack:
- {projectRoot}/.yarn/__virtual__/@babel-helper-create-class-features-plugin-virtual-9d8cf8d8bf/0/cache/@babel-helper-create-class-features-plugin-npm-7.27.1-65d3087eb1-701579b490.zip/node_modules/@babel/helper-create-class-features-plugin/lib/index.js
- {projectRoot}/.yarn/__virtual__/@babel-plugin-transform-typescript-virtual-868dbcd5dd/0/cache/@babel-plugin-transform-typescript-npm-7.27.1-9a4091f89b-069b37c5be.zip/node_modules/@babel/plugin-transform-typescript/lib/index.js
- {projectRoot}/.yarn/__virtual__/@babel-preset-typescript-virtual-00769bb29d/0/cache/@babel-preset-typescript-npm-7.27.1-b9b5e53f61-9d8e75326b.zip/node_modules/@babel/preset-typescript/lib/index.js
    at require$$0.Module._resolveFilename ({projectRoot}/.pnp.cjs:12208:13)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1061:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1066:22)
    at Module.<anonymous> (node:internal/modules/cjs/loader:1215:37)
    at require$$0.Module._load ({projectRoot}/.pnp.cjs:12099:31)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
    at Module.require (node:internal/modules/cjs/loader:1491:12)
    at require (node:internal/modules/helpers:135:16)
    at Object.<anonymous> ({projectRoot}/.yarn/__virtual__/@babel-helper-create-class-features-plugin-virtual-9d8cf8d8bf/0/cache/@babel-helper-create-class-features-plugin-npm-7.27.1-65d3087eb1-701579b490.zip/node_modules/@babel/helper-create-class-features-plugin/src/index.ts:1:1)

Node.js v24.1.0

Workaround:

If using yarn, add this to your .yarnrc.yml:

packageExtensions:
  "@better-auth/cli@*":
    dependencies:
      "@babel/core": "^7.0.0"

If using other package managers (npm, pnpm):

If your package manager does not verify dependency resolution, you should be fine to just install @babel/core.

If your package manager does verify dependency resolution, you need to install both @babel/core and @better-auth/cli then *go into your downloaded dependencies, and add @babel/core as either a dependency or peer-dependency to @better-auth/cli.

Related issues:

https://github.com/better-auth/better-auth/issues/886 - Dec 14 2024 to Mar 5 2025; closed due a workaround being linked and labelled a solution.

https://github.com/better-auth/better-auth/issues/1467 - Feb 17 2025 to Mar 23 2025; closed due to being incorrectly labelled as an end user configuration issue.

Diagnosis:

From inspection of the error, there is a peer dependency that has not been either propagated or satisfied by @better-auth/cli.

Installing @better-auth/cli via yarn (4.9.1) using pnp allows for easier inspection.

Once installed, running yarn cli duplicates the issue.

Adding the dependency to .yarnrc.yml causes the issue to become resolved and no other issues to become presented.

packageExtensions:
  "@better-auth/cli@*":
    dependencies:
      "@babel/core": "*" # note, see above for workaround

Therefore, from direct testing, the issue is that @better-auth/cli doesn't satisfy or propagate the peer dependency @babel/core.

Context

Does any package in the monorepo satisfy this dependency?

Yes: ./examples/expo-example/package.json is shown to install @babel/core.

Found by running

find . -name "package.json" -type f | xargs -I {} -- bash -c 'echo -e "{}\n" && grep -rn "@babel/core" {}'

Which gives (as a partial result):

./examples/expo-example/package.json

55:    "@babel/core": "^7.26.0",

Does any other package use the babel family of dependencies, and therefore may also have this issue?

Yes: ./packages/expo/package.json and ./packages/cli/package.json; however expo-example satisfies the dependency, and so does not have this issue.

Found by running

find . -name "package.json" -type f | xargs -I {} -- bash -c 'echo -e "{}\n" && grep -rn "@babel" {}'

Which gives (as a partial result):

./examples/expo-example/package.json

55:    "@babel/core": "^7.26.0",
56:    "@babel/preset-env": "^7.26.0",
57:    "@babel/runtime": "^7.26.0",

./packages/cli/package.json

33:    "@babel/preset-react": "^7.26.3",
34:    "@babel/preset-typescript": "^7.26.0",

Which version of babel core is required by existing dependencies?

This one: ^7.0.0

Determined by:

Cloning https://github.com/babel/babel and running:

find . -name package.json -type f | xargs -I {} -- grep -r "\"@babel/core" "{}" | grep -v workspace | sort | uniq -c

Shows that versions in use by the latest main are:

     17     "@babel/core": "^7.0.0"
    106     "@babel/core": "^7.0.0-0"
      1           "@babel/core": ">=7.11.0",
      1     "@babel/core": "^7.11.0",
      2     "@babel/core": "^7.12.0"
      1     "@babel/core-7.12": "npm:@babel/core@7.12.9",
      2     "@babel/core": "^7.13.0"
      1     "@babel/core": "^7.17.0"
      3     "@babel/core": "^7.22.0"
      1     "@babel/core": "^7.22.5"
      1     "@babel/core": "8.0.0-alpha.16",

Using the commands:

find . -name package.json -type f | xargs -I {} -- bash -c 'grep -rn "\"@babel/core\": \"^7.1" "{}" && echo "{}"'
find . -name package.json -type f | xargs -I {} -- bash -c 'grep -rn "\"@babel/core\": \"^7.2" "{}" && echo "{}"'

We see that the non-7.0.0 dependencies are from packages (note, package follows version):

37:    "@babel/core": "^7.11.0",
./eslint/babel-eslint-parser/package.json
33:    "@babel/core": "^7.13.0"
./packages/babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining/package.json
32:    "@babel/core": "^7.12.0"
./packages/babel-plugin-proposal-record-and-tuple/package.json
30:    "@babel/core": "^7.12.0"
./packages/babel-plugin-transform-class-static-block/package.json
24:    "@babel/core": "^7.17.0"
./packages/babel-plugin-proposal-destructuring-private/package.json
30:    "@babel/core": "^7.13.0"
./packages/babel-plugin-proposal-async-do-expressions/package.json

and

40:    "@babel/core": "^7.22.0"
./packages/babel-plugin-proposal-import-wasm-source/package.json
36:    "@babel/core": "^7.22.0"
./packages/babel-plugin-proposal-import-attributes-to-assertions/package.json
40:    "@babel/core": "^7.22.0"
./packages/babel-plugin-transform-json-modules/package.json
26:    "@babel/core": "^7.22.5"
./packages/babel-plugin-proposal-optional-chaining-assign/package.json

By inspection the latest version of @babel/core is 7.27.4.

Running yarn why -R --peers @babel/core in the local project with @better-auth/cli installed and the packageExtension applied, shows:

   └─ @better-auth/cli@npm:1.2.8 (via npm:^1.2.8)
      ├─ @babel/core@npm:7.27.4 (via npm:*)
      │  └─ @babel/helper-module-transforms@npm:7.27.3 [801e5] (via npm:^7.27.3 [801e5])
      │     └─ @babel/core@npm:7.27.4 (via npm:*)
      ├─ @babel/preset-react@npm:7.27.1 [3f43d] (via npm:^7.26.3 [3f43d])
      │  ├─ @babel/core@npm:7.27.4 (via npm:*)
      │  ├─ @babel/plugin-transform-react-display-name@npm:7.27.1 [072ea] (via npm:^7.27.1 [072ea])
      │  │  └─ @babel/core@npm:7.27.4 (via npm:*)
      │  ├─ @babel/plugin-transform-react-jsx@npm:7.27.1 [072ea] (via npm:^7.27.1 [072ea])
      │  │  ├─ @babel/core@npm:7.27.4 (via npm:*)
      │  │  └─ @babel/plugin-syntax-jsx@npm:7.27.1 [7c871] (via npm:^7.27.1 [7c871])
      │  │     └─ @babel/core@npm:7.27.4 (via npm:*)
      │  ├─ @babel/plugin-transform-react-jsx-development@npm:7.27.1 [072ea] (via npm:^7.27.1 [072ea])
      │  │  ├─ @babel/core@npm:7.27.4 (via npm:*)
      │  │  └─ @babel/plugin-transform-react-jsx@npm:7.27.1 [072ea] (via npm:^7.27.1 [b849c])
      │  └─ @babel/plugin-transform-react-pure-annotations@npm:7.27.1 [072ea] (via npm:^7.27.1 [072ea])
      │     └─ @babel/core@npm:7.27.4 (via npm:*)
      └─ @babel/preset-typescript@npm:7.27.1 [3f43d] (via npm:^7.26.0 [3f43d])
         ├─ @babel/core@npm:7.27.4 (via npm:*)
         ├─ @babel/plugin-syntax-jsx@npm:7.27.1 [7c871] (via npm:^7.27.1 [00769])
         ├─ @babel/plugin-transform-modules-commonjs@npm:7.27.1 [00769] (via npm:^7.27.1 [00769])
         │  ├─ @babel/core@npm:7.27.4 (via npm:*)
         │  └─ @babel/helper-module-transforms@npm:7.27.3 [801e5] (via npm:^7.27.1 [c6bc4])
         └─ @babel/plugin-transform-typescript@npm:7.27.1 [00769] (via npm:^7.27.1 [00769])
            ├─ @babel/core@npm:7.27.4 (via npm:*)
            ├─ @babel/helper-create-class-features-plugin@npm:7.27.1 [868db] (via npm:^7.27.1 [868db])
            │  ├─ @babel/core@npm:7.27.4 (via npm:*)
            │  └─ @babel/helper-replace-supers@npm:7.27.1 [9d8cf] (via npm:^7.27.1 [9d8cf])
            │     └─ @babel/core@npm:7.27.4 (via npm:*)
            └─ @babel/plugin-syntax-typescript@npm:7.27.1 [868db] (via npm:^7.27.1 [868db])
               └─ @babel/core@npm:7.27.4 (via npm:*)

Overall, any ^7.0.0 dependency will suffice, giving maximum compatibility with modules in use by end users. If some specific babel modules were to be added to better-auth the minimum versoin may need to be increased. Note, that if @babel/core isn't already installed, the standard behaviour of most (all?) package managers is to install the latest version that satisfies the range.

Should it be a propagated peer dependency or a direct dependency?

It should be a direct dependency.

If added as a peer dependency, it will be unlikely to work with npx / yarn dlx unless the user already has @babel/core@^7.0.0 installed.

Conclusion

The @better-auth/cli package should have @babel/core@^7.0.0 added as a dependency. No other changes need made.

Notes for retrospective

Package managers, including pnpm which is used by this repo, often warn about missing / unsatisfied peer-dependencies. It is likely that this warning was missed because of the large number of react peer-dependency warnings. React peer dependency warnings cannot often be trivially resolved without fixes to third party packages (many of which are in progress) due to the scale of the ecosystem and the high compatiblity between react versions.

Originally created by @NormalGaussian on GitHub (Jun 4, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2908 # Issue My original error; cleaned by redacting my local directories with `{projectRoot}`: When attempting to run `yarn dlx @better-auth/cli generate --config {configFile}`, this error is eventually presented: ``` {projectRoot}/.pnp.cjs:12208 Error.captureStackTrace(firstError); ^ Error: @babel/helper-create-class-features-plugin tried to access @babel/core (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound. Required package: @babel/core Required by: @babel/helper-create-class-features-plugin@virtual:868dbcd5ddfd0f02c5e350de117637169db0c200f336100146606f4c388b20ddf15a57a2b338a562d4c472c00f366c24fc91b7e42a001e5e065850baf67e2b20#npm:7.27.1 (via {projectRoot}/.yarn/__virtual__/@babel-helper-create-class-features-plugin-virtual-9d8cf8d8bf/0/cache/@babel-helper-create-class-features-plugin-npm-7.27.1-65d3087eb1-701579b490.zip/node_modules/@babel/helper-create-class-features-plugin/lib/) Ancestor breaking the chain: @better-auth/cli@npm:1.2.8 Require stack: - {projectRoot}/.yarn/__virtual__/@babel-helper-create-class-features-plugin-virtual-9d8cf8d8bf/0/cache/@babel-helper-create-class-features-plugin-npm-7.27.1-65d3087eb1-701579b490.zip/node_modules/@babel/helper-create-class-features-plugin/lib/index.js - {projectRoot}/.yarn/__virtual__/@babel-plugin-transform-typescript-virtual-868dbcd5dd/0/cache/@babel-plugin-transform-typescript-npm-7.27.1-9a4091f89b-069b37c5be.zip/node_modules/@babel/plugin-transform-typescript/lib/index.js - {projectRoot}/.yarn/__virtual__/@babel-preset-typescript-virtual-00769bb29d/0/cache/@babel-preset-typescript-npm-7.27.1-b9b5e53f61-9d8e75326b.zip/node_modules/@babel/preset-typescript/lib/index.js at require$$0.Module._resolveFilename ({projectRoot}/.pnp.cjs:12208:13) at defaultResolveImpl (node:internal/modules/cjs/loader:1061:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1066:22) at Module.<anonymous> (node:internal/modules/cjs/loader:1215:37) at require$$0.Module._load ({projectRoot}/.pnp.cjs:12099:31) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:235:24) at Module.require (node:internal/modules/cjs/loader:1491:12) at require (node:internal/modules/helpers:135:16) at Object.<anonymous> ({projectRoot}/.yarn/__virtual__/@babel-helper-create-class-features-plugin-virtual-9d8cf8d8bf/0/cache/@babel-helper-create-class-features-plugin-npm-7.27.1-65d3087eb1-701579b490.zip/node_modules/@babel/helper-create-class-features-plugin/src/index.ts:1:1) Node.js v24.1.0 ``` # Workaround: If using yarn, add this to your `.yarnrc.yml`: ```yaml packageExtensions: "@better-auth/cli@*": dependencies: "@babel/core": "^7.0.0" ``` If using other package managers (npm, pnpm): If your package manager does not verify dependency resolution, you should be fine to just install `@babel/core`. If your package manager does verify dependency resolution, you need to install both `@babel/core` and `@better-auth/cli` then *go into your downloaded dependencies, and add `@babel/core` as either a dependency or peer-dependency to `@better-auth/cli`. # Related issues: https://github.com/better-auth/better-auth/issues/886 - Dec 14 2024 to Mar 5 2025; closed due a workaround being linked and labelled a solution. https://github.com/better-auth/better-auth/issues/1467 - Feb 17 2025 to Mar 23 2025; closed due to being incorrectly labelled as an end user configuration issue. # Diagnosis: From inspection of the error, there is a peer dependency that has not been either propagated or satisfied by `@better-auth/cli`. Installing `@better-auth/cli` via yarn (4.9.1) using pnp allows for easier inspection. Once installed, running `yarn cli` duplicates the issue. Adding the dependency to `.yarnrc.yml` causes the issue to become resolved and no other issues to become presented. ```yaml packageExtensions: "@better-auth/cli@*": dependencies: "@babel/core": "*" # note, see above for workaround ``` Therefore, from direct testing, the issue is that `@better-auth/cli` doesn't satisfy or propagate the peer dependency `@babel/core`. # Context ## Does any package in the monorepo satisfy this dependency? Yes: `./examples/expo-example/package.json` is shown to install `@babel/core`. Found by running ``` find . -name "package.json" -type f | xargs -I {} -- bash -c 'echo -e "{}\n" && grep -rn "@babel/core" {}' ``` Which gives (as a partial result): ``` ./examples/expo-example/package.json 55: "@babel/core": "^7.26.0", ``` ## Does any other package use the babel family of dependencies, and therefore may also have this issue? Yes: `./packages/expo/package.json` and `./packages/cli/package.json`; however expo-example satisfies the dependency, and so does not have this issue. Found by running ``` find . -name "package.json" -type f | xargs -I {} -- bash -c 'echo -e "{}\n" && grep -rn "@babel" {}' ``` Which gives (as a partial result): ``` ./examples/expo-example/package.json 55: "@babel/core": "^7.26.0", 56: "@babel/preset-env": "^7.26.0", 57: "@babel/runtime": "^7.26.0", ./packages/cli/package.json 33: "@babel/preset-react": "^7.26.3", 34: "@babel/preset-typescript": "^7.26.0", ``` ## Which version of babel core is required by existing dependencies? This one: `^7.0.0` Determined by: Cloning https://github.com/babel/babel and running: ``` find . -name package.json -type f | xargs -I {} -- grep -r "\"@babel/core" "{}" | grep -v workspace | sort | uniq -c ``` Shows that versions in use by the latest main are: ``` 17 "@babel/core": "^7.0.0" 106 "@babel/core": "^7.0.0-0" 1 "@babel/core": ">=7.11.0", 1 "@babel/core": "^7.11.0", 2 "@babel/core": "^7.12.0" 1 "@babel/core-7.12": "npm:@babel/core@7.12.9", 2 "@babel/core": "^7.13.0" 1 "@babel/core": "^7.17.0" 3 "@babel/core": "^7.22.0" 1 "@babel/core": "^7.22.5" 1 "@babel/core": "8.0.0-alpha.16", ``` Using the commands: ``` find . -name package.json -type f | xargs -I {} -- bash -c 'grep -rn "\"@babel/core\": \"^7.1" "{}" && echo "{}"' find . -name package.json -type f | xargs -I {} -- bash -c 'grep -rn "\"@babel/core\": \"^7.2" "{}" && echo "{}"' ``` We see that the non-7.0.0 dependencies are from packages (note, package follows version): ``` 37: "@babel/core": "^7.11.0", ./eslint/babel-eslint-parser/package.json 33: "@babel/core": "^7.13.0" ./packages/babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining/package.json 32: "@babel/core": "^7.12.0" ./packages/babel-plugin-proposal-record-and-tuple/package.json 30: "@babel/core": "^7.12.0" ./packages/babel-plugin-transform-class-static-block/package.json 24: "@babel/core": "^7.17.0" ./packages/babel-plugin-proposal-destructuring-private/package.json 30: "@babel/core": "^7.13.0" ./packages/babel-plugin-proposal-async-do-expressions/package.json ``` and ``` 40: "@babel/core": "^7.22.0" ./packages/babel-plugin-proposal-import-wasm-source/package.json 36: "@babel/core": "^7.22.0" ./packages/babel-plugin-proposal-import-attributes-to-assertions/package.json 40: "@babel/core": "^7.22.0" ./packages/babel-plugin-transform-json-modules/package.json 26: "@babel/core": "^7.22.5" ./packages/babel-plugin-proposal-optional-chaining-assign/package.json ``` By inspection the latest version of `@babel/core` is `7.27.4`. Running `yarn why -R --peers @babel/core` in the local project with `@better-auth/cli` installed and the packageExtension applied, shows: ``` └─ @better-auth/cli@npm:1.2.8 (via npm:^1.2.8) ├─ @babel/core@npm:7.27.4 (via npm:*) │ └─ @babel/helper-module-transforms@npm:7.27.3 [801e5] (via npm:^7.27.3 [801e5]) │ └─ @babel/core@npm:7.27.4 (via npm:*) ├─ @babel/preset-react@npm:7.27.1 [3f43d] (via npm:^7.26.3 [3f43d]) │ ├─ @babel/core@npm:7.27.4 (via npm:*) │ ├─ @babel/plugin-transform-react-display-name@npm:7.27.1 [072ea] (via npm:^7.27.1 [072ea]) │ │ └─ @babel/core@npm:7.27.4 (via npm:*) │ ├─ @babel/plugin-transform-react-jsx@npm:7.27.1 [072ea] (via npm:^7.27.1 [072ea]) │ │ ├─ @babel/core@npm:7.27.4 (via npm:*) │ │ └─ @babel/plugin-syntax-jsx@npm:7.27.1 [7c871] (via npm:^7.27.1 [7c871]) │ │ └─ @babel/core@npm:7.27.4 (via npm:*) │ ├─ @babel/plugin-transform-react-jsx-development@npm:7.27.1 [072ea] (via npm:^7.27.1 [072ea]) │ │ ├─ @babel/core@npm:7.27.4 (via npm:*) │ │ └─ @babel/plugin-transform-react-jsx@npm:7.27.1 [072ea] (via npm:^7.27.1 [b849c]) │ └─ @babel/plugin-transform-react-pure-annotations@npm:7.27.1 [072ea] (via npm:^7.27.1 [072ea]) │ └─ @babel/core@npm:7.27.4 (via npm:*) └─ @babel/preset-typescript@npm:7.27.1 [3f43d] (via npm:^7.26.0 [3f43d]) ├─ @babel/core@npm:7.27.4 (via npm:*) ├─ @babel/plugin-syntax-jsx@npm:7.27.1 [7c871] (via npm:^7.27.1 [00769]) ├─ @babel/plugin-transform-modules-commonjs@npm:7.27.1 [00769] (via npm:^7.27.1 [00769]) │ ├─ @babel/core@npm:7.27.4 (via npm:*) │ └─ @babel/helper-module-transforms@npm:7.27.3 [801e5] (via npm:^7.27.1 [c6bc4]) └─ @babel/plugin-transform-typescript@npm:7.27.1 [00769] (via npm:^7.27.1 [00769]) ├─ @babel/core@npm:7.27.4 (via npm:*) ├─ @babel/helper-create-class-features-plugin@npm:7.27.1 [868db] (via npm:^7.27.1 [868db]) │ ├─ @babel/core@npm:7.27.4 (via npm:*) │ └─ @babel/helper-replace-supers@npm:7.27.1 [9d8cf] (via npm:^7.27.1 [9d8cf]) │ └─ @babel/core@npm:7.27.4 (via npm:*) └─ @babel/plugin-syntax-typescript@npm:7.27.1 [868db] (via npm:^7.27.1 [868db]) └─ @babel/core@npm:7.27.4 (via npm:*) ``` Overall, any `^7.0.0` dependency will suffice, giving maximum compatibility with modules in use by end users. If some specific babel modules were to be added to better-auth the minimum versoin may need to be increased. Note, that if `@babel/core` isn't already installed, the standard behaviour of most (all?) package managers is to install the latest version that satisfies the range. ## Should it be a propagated peer dependency or a direct dependency? It should be a direct dependency. If added as a peer dependency, it will be unlikely to work with `npx` / `yarn dlx` unless the user already has `@babel/core@^7.0.0` installed. # Conclusion The `@better-auth/cli` package should have `@babel/core@^7.0.0` added as a dependency. No other changes need made. # Notes for retrospective Package managers, including pnpm which is used by this repo, often warn about missing / unsatisfied peer-dependencies. It is likely that this warning was missed because of the large number of react peer-dependency warnings. React peer dependency warnings cannot often be trivially resolved without fixes to third party packages (many of which are in progress) due to the scale of the ecosystem and the high compatiblity between react versions.
GiteaMirror added the locked label 2026-04-17 17:22:01 -05:00
GiteaMirror commented 2026-04-17 17:22:02 -05:00
Author
Owner
Copy Link

@NormalGaussian commented on GitHub (Jun 4, 2025):

@Bekacru - I note that you closed both the other presentations of this issue in late March; its a type of issue I often see closed like this (particularly as maintainers are trying to prioritise their time and avoid wasting time on broken user configurations). Its only an easy one for me as I'm using yarn in pnp mode (see a comparison of installation methods here) which specifically detects these issues at runtime.

<!-- gh-comment-id:2941253897 --> @NormalGaussian commented on GitHub (Jun 4, 2025): @Bekacru - I note that you closed both the other presentations of this issue in late March; its a type of issue I often see closed like this (particularly as maintainers are trying to prioritise their time and avoid wasting time on broken user configurations). Its only an easy one for me as I'm using yarn in pnp mode (see a comparison of installation methods [here](https://yarnpkg.com/features/linkers#nodelinker-pnpm)) which specifically detects these issues at runtime.
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#26714
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?