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

[GH-ISSUE #6918] better-call@1.1.5 peer dependency issue #27994

New Issue
Closed
opened 2026-04-17 19:18:55 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-17 19:18:55 -05:00
Owner
Copy Link

Originally created by @documedicgp on GitHub (Dec 21, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6918

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

At an existing project upgrade to v1.4.8-beta.5 and run npm i or run:

npm uninstall better-auth

and then

npm i better-auth@1.4.8-beta.5

Current vs. Expected behavior

Current behavior

You get the following warnings:

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @better-auth/core@1.4.8-beta.4
npm warn Found: better-call@1.1.7
npm warn node_modules/better-auth/node_modules/better-call
npm warn   better-call@"1.1.7" from better-auth@1.4.8-beta.5
npm warn   node_modules/better-auth
npm warn     better-auth@"^1.4.8-beta.5" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer better-call@"1.1.5" from @better-auth/core@1.4.8-beta.4
npm warn node_modules/better-auth/node_modules/@better-auth/core
npm warn   @better-auth/core@"1.4.8-beta.4" from better-auth@1.4.8-beta.5
npm warn   node_modules/better-auth
npm warn   1 more (@better-auth/telemetry)
npm warn
npm warn Conflicting peer dependency: better-call@1.1.5
npm warn node_modules/better-call
npm warn   peer better-call@"1.1.5" from @better-auth/core@1.4.8-beta.4
npm warn   node_modules/better-auth/node_modules/@better-auth/core
npm warn     @better-auth/core@"1.4.8-beta.4" from better-auth@1.4.8-beta.5
npm warn     node_modules/better-auth
npm warn     1 more (@better-auth/telemetry)

Expected behavior

No warnings

What version of Better Auth are you using?

1.4.8-beta.5

System info

npm: 10.9.4
node: 22.21.1

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

Package

Auth config (if applicable)

Additional context

npm list better-call gives the following:

documedic-app@1.2.1 /Users/documedic/documedic-app
└─┬ better-auth@1.4.8-beta.5
  ├─┬ @better-auth/core@1.4.8-beta.4
  │ └── better-call@1.1.7 deduped invalid: "1.1.5" from node_modules/better-auth/node_modules/@better-auth/core
  └── better-call@1.1.7 invalid: "1.1.5" from node_modules/better-auth/node_modules/@better-auth/core

npm error code ELSPROBLEMS
npm error invalid: better-call@1.1.7 /Users/documedic/documedic-app/node_modules/better-auth/node_modules/better-call
npm error A complete log of this run can be found in: /Users/documedic/.npm/_logs/2025-12-21T08_41_12_030Z-debug-0.log
Originally created by @documedicgp on GitHub (Dec 21, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6918 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce At an existing project upgrade to `v1.4.8-beta.5` and run `npm i` or run: `npm uninstall better-auth` and then `npm i better-auth@1.4.8-beta.5` ### Current vs. Expected behavior **Current behavior** You get the following warnings: ```shell npm warn ERESOLVE overriding peer dependency npm warn While resolving: @better-auth/core@1.4.8-beta.4 npm warn Found: better-call@1.1.7 npm warn node_modules/better-auth/node_modules/better-call npm warn better-call@"1.1.7" from better-auth@1.4.8-beta.5 npm warn node_modules/better-auth npm warn better-auth@"^1.4.8-beta.5" from the root project npm warn npm warn Could not resolve dependency: npm warn peer better-call@"1.1.5" from @better-auth/core@1.4.8-beta.4 npm warn node_modules/better-auth/node_modules/@better-auth/core npm warn @better-auth/core@"1.4.8-beta.4" from better-auth@1.4.8-beta.5 npm warn node_modules/better-auth npm warn 1 more (@better-auth/telemetry) npm warn npm warn Conflicting peer dependency: better-call@1.1.5 npm warn node_modules/better-call npm warn peer better-call@"1.1.5" from @better-auth/core@1.4.8-beta.4 npm warn node_modules/better-auth/node_modules/@better-auth/core npm warn @better-auth/core@"1.4.8-beta.4" from better-auth@1.4.8-beta.5 npm warn node_modules/better-auth npm warn 1 more (@better-auth/telemetry) ``` **Expected behavior** No warnings ### What version of Better Auth are you using? 1.4.8-beta.5 ### System info ```bash npm: 10.9.4 node: 22.21.1 ``` ### Which area(s) are affected? (Select all that apply) Package ### Auth config (if applicable) ```typescript ``` ### Additional context `npm list better-call` gives the following: ```shell documedic-app@1.2.1 /Users/documedic/documedic-app └─┬ better-auth@1.4.8-beta.5 ├─┬ @better-auth/core@1.4.8-beta.4 │ └── better-call@1.1.7 deduped invalid: "1.1.5" from node_modules/better-auth/node_modules/@better-auth/core └── better-call@1.1.7 invalid: "1.1.5" from node_modules/better-auth/node_modules/@better-auth/core npm error code ELSPROBLEMS npm error invalid: better-call@1.1.7 /Users/documedic/documedic-app/node_modules/better-auth/node_modules/better-call npm error A complete log of this run can be found in: /Users/documedic/.npm/_logs/2025-12-21T08_41_12_030Z-debug-0.log ```
GiteaMirror added the locked label 2026-04-17 19:18:55 -05:00
GiteaMirror commented 2026-04-17 19:18:57 -05:00
Author
Owner
Copy Link

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

To address the peer dependency issue you're experiencing with better-call@1.1.5 when upgrading to better-auth@1.4.8-beta.5, it appears that the warnings you're encountering are due to version conflicts between better-call and @better-auth/core. Specifically, @better-auth/core@1.4.8-beta.4 requires better-call@1.1.5, but your project has better-call@1.1.7 installed.

To resolve this issue, you can consider the following steps:

  1. Downgrade better-call: You could downgrade better-call to match the required version by running:

    npm install better-call@1.1.5

  2. Use --legacy-peer-deps: Alternatively, you can run the installation command with the --legacy-peer-deps option, which tells npm to ignore peer dependencies:

    npm install better-auth@1.4.8-beta.5 --legacy-peer-deps

  3. Check for updates: Ensure that you are using the latest compatible versions of both better-auth and better-call, as newer releases may have resolved these dependency conflicts.

  4. Monitor GitHub issues: Keep an eye on relevant GitHub issues regarding dependency conflicts for potential resolutions and updates from the maintainers.

Would you like more information on handling npm peer dependency issues or anything else related to Better Auth?

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:3678603139 --> @better-auth-agent[bot] commented on GitHub (Dec 21, 2025): To address the peer dependency issue you're experiencing with `better-call@1.1.5` when upgrading to `better-auth@1.4.8-beta.5`, it appears that the warnings you're encountering are due to version conflicts between `better-call` and `@better-auth/core`. Specifically, `@better-auth/core@1.4.8-beta.4` requires `better-call@1.1.5`, but your project has `better-call@1.1.7` installed. To resolve this issue, you can consider the following steps: 1. **Downgrade `better-call`**: You could downgrade `better-call` to match the required version by running: ```bash npm install better-call@1.1.5 ``` 2. **Use `--legacy-peer-deps`**: Alternatively, you can run the installation command with the `--legacy-peer-deps` option, which tells npm to ignore peer dependencies: ```bash npm install better-auth@1.4.8-beta.5 --legacy-peer-deps ``` 3. **Check for updates**: Ensure that you are using the latest compatible versions of both `better-auth` and `better-call`, as newer releases may have resolved these dependency conflicts. 4. **Monitor GitHub issues**: Keep an eye on relevant GitHub issues regarding dependency conflicts for potential resolutions and updates from the maintainers. Would you like more information on handling npm peer dependency issues or anything else related to Better Auth? _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-17 19:19:00 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Dec 22, 2025):

I think this is a release issue; we don't have the core module beta.5 but we have better-auth beta.5

<!-- gh-comment-id:3680568020 --> @himself65 commented on GitHub (Dec 22, 2025): I think this is a release issue; we don't have the core module beta.5 but we have better-auth beta.5
GiteaMirror commented 2026-04-17 19:19:02 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Dec 22, 2025):

I just released 1.4.8-beta.6. It should be fixed now

<!-- gh-comment-id:3680575565 --> @himself65 commented on GitHub (Dec 22, 2025): I just released 1.4.8-beta.6. It should be fixed now
GiteaMirror commented 2026-04-17 19:19:03 -05:00
Author
Owner
Copy Link

@documedicgp commented on GitHub (Dec 22, 2025):

Thank you @himself65. Issue fixed!

<!-- gh-comment-id:3680979648 --> @documedicgp commented on GitHub (Dec 22, 2025): Thank you @himself65. Issue fixed!
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#27994
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?