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 #6468] Cannot upgrade to 1.4.4 from 1.4 beta because 1.4.4 requires next 15 #27847

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

Originally created by @realtebo on GitHub (Dec 2, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6468

Currently I'm using

"better-auth": "^1.4.0-beta.20",
...
"next": "16.0.1",

I tried upgrade to 1.4.4 but I looks like I cannot due to requirements for next 14 || 15, but not allowed on next 16

% npm i better-auth
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: better-auth@1.4.4
npm error Found: next@16.0.1
npm error node_modules/next
npm error   next@"16.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional next@"^14.0.0 || ^15.0.0" from better-auth@1.4.4
npm error node_modules/better-auth
npm error   better-auth@"^1.4.0-beta.20" from the root project
npm error
npm error Conflicting peer dependency: next@15.5.6
npm error node_modules/next
npm error   peerOptional next@"^14.0.0 || ^15.0.0" from better-auth@1.4.4
npm error   node_modules/better-auth
npm error     better-auth@"^1.4.0-beta.20" from the root project
Originally created by @realtebo on GitHub (Dec 2, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6468 Currently I'm using ``` "better-auth": "^1.4.0-beta.20", ... "next": "16.0.1", ``` I tried upgrade to 1.4.4 but I looks like I cannot due to requirements for next 14 || 15, but not allowed on next 16 ``` % npm i better-auth npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: better-auth@1.4.4 npm error Found: next@16.0.1 npm error node_modules/next npm error next@"16.0.1" from the root project npm error npm error Could not resolve dependency: npm error peerOptional next@"^14.0.0 || ^15.0.0" from better-auth@1.4.4 npm error node_modules/better-auth npm error better-auth@"^1.4.0-beta.20" from the root project npm error npm error Conflicting peer dependency: next@15.5.6 npm error node_modules/next npm error peerOptional next@"^14.0.0 || ^15.0.0" from better-auth@1.4.4 npm error node_modules/better-auth npm error better-auth@"^1.4.0-beta.20" from the root project ```
GiteaMirror added the locked label 2026-04-17 19:04:49 -05:00
GiteaMirror commented 2026-04-17 19:04:50 -05:00
Author
Owner
Copy Link

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

Hi there! It looks like the upgrade error occurs because the latest stable release (v1.4.4) explicitly requires Next.js versions within the range 14 or 15, while your project is using Next.js 16. This peer dependency constraint is causing the installation to fail.

To resolve the issue you have a few options:
• Downgrade Next.js to a supported version (15.x) so that the peer dependency matches.
• Wait for an upcoming release of Better Auth that expands its peer dependency support to Next.js 16.
• If you’re comfortable with it, you might force the installation (using npm’s legacy peer dependency resolution flag or similar), but be aware this could lead to unpredictable behavior.

Are you leaning toward downgrading Next.js, or would you like to discuss alternative approaches? Tag @better-auth-agent if you would like an answer from the Agent.

If you need more help, tag @Skyvern in a comment so I can respond.

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3600919876 --> @better-auth-agent[bot] commented on GitHub (Dec 2, 2025): Hi there! It looks like the upgrade error occurs because the latest stable release (v1.4.4) explicitly requires Next.js versions within the range 14 or 15, while your project is using Next.js 16. This peer dependency constraint is causing the installation to fail. To resolve the issue you have a few options: • Downgrade Next.js to a supported version (15.x) so that the peer dependency matches. • Wait for an upcoming release of Better Auth that expands its peer dependency support to Next.js 16. • If you’re comfortable with it, you might force the installation (using npm’s legacy peer dependency resolution flag or similar), but be aware this could lead to unpredictable behavior. Are you leaning toward downgrading Next.js, or would you like to discuss alternative approaches? Tag @better-auth-agent if you would like an answer from the Agent. _If you need more help, tag @Skyvern 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:04:51 -05:00
Author
Owner
Copy Link

@jslno commented on GitHub (Dec 2, 2025):

duplicate #6439

<!-- gh-comment-id:3603573948 --> @jslno commented on GitHub (Dec 2, 2025): duplicate #6439
GiteaMirror commented 2026-04-17 19:04:52 -05:00
Author
Owner
Copy Link

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

Please try v1.4.5-beta.1

<!-- gh-comment-id:3603712880 --> @himself65 commented on GitHub (Dec 2, 2025): Please try v1.4.5-beta.1
GiteaMirror commented 2026-04-17 19:04:52 -05:00
Author
Owner
Copy Link

@realtebo commented on GitHub (Dec 3, 2025):

Fixed in 1.4.5 stable

<!-- gh-comment-id:3606924618 --> @realtebo commented on GitHub (Dec 3, 2025): Fixed in 1.4.5 stable
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#27847
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?