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

[GH-ISSUE #8189] Add support for Expo SDK 55 and new package versioning scheme #11019

New Issue
Closed
opened 2026-04-13 07:23:35 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 07:23:35 -05:00
Owner
Copy Link
Copy Source

Originally created by @gabrieleolmi on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/8189

Description

The current version of @better-auth/expo (v1.4.19) has peer dependency constraints that are incompatible with the newly released Expo SDK 55.

Starting from SDK 55, Expo has transitioned to a new versioning scheme where all Expo-branded packages (such as expo-network, expo-constants, and expo-web-browser) use a major version that matches the SDK version (e.g., 55.x.x).

Currently, @better-auth/expo expects older version ranges (like expo-network@^8.0.7), which triggers peer dependency conflicts in any project upgraded to or initialized with SDK 55.

Incompatibility Examples

During installation with pnpm or npm, the following conflicts occur:

expo-network: found 55.0.x, expected ^8.0.7

Important

Other potential peer dependencies like expo-constants or expo-web-browser may also be affected by this significant version jump.

Steps to Reproduce

  1. Create a new Expo project using SDK 55: 
    npx create-expo-app@latest --template default@sdk-55
  2. Attempt to install the plugin: 
    pnpm add @better-auth/expo
  3. Observe results: Note the unmet peer dependency warnings or terminal errors.

Proposed Solution

Update the peerDependencies in @better-auth/expo to include the 55.x.x range for all Expo-related packages. This will ensure official support for the latest SDK and prevent installation blocks.

Environment

Requirement Version
better-auth 1.4.19+
Expo SDK 55.x.x
Package Manager pnpm / npm
Originally created by @gabrieleolmi on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/better-auth/better-auth/issues/8189 ## Description The current version of `@better-auth/expo` (**v1.4.19**) has peer dependency constraints that are incompatible with the newly released **Expo SDK 55**. Starting from SDK 55, Expo has transitioned to a new versioning scheme where all Expo-branded packages (such as `expo-network`, `expo-constants`, and `expo-web-browser`) use a major version that matches the SDK version (e.g., `55.x.x`). Currently, `@better-auth/expo` expects older version ranges (like `expo-network@^8.0.7`), which triggers peer dependency conflicts in any project upgraded to or initialized with SDK 55. ## Incompatibility Examples During installation with `pnpm` or `npm`, the following conflicts occur: ```text expo-network: found 55.0.x, expected ^8.0.7 ``` > [!IMPORTANT] > Other potential peer dependencies like `expo-constants` or `expo-web-browser` may also be affected by this significant version jump. ## Steps to Reproduce 1. **Create a new Expo project** using SDK 55: ```bash npx create-expo-app@latest --template default@sdk-55 ``` 2. **Attempt to install the plugin**: ```bash pnpm add @better-auth/expo ``` 3. **Observe results**: Note the unmet peer dependency warnings or terminal errors. ## Proposed Solution Update the `peerDependencies` in `@better-auth/expo` to include the `55.x.x` range for all Expo-related packages. This will ensure official support for the latest SDK and prevent installation blocks. ## Environment | Requirement | Version | | :--- | :--- | | **better-auth** | `1.4.19+` | | **Expo SDK** | `55.x.x` | | **Package Manager** | `pnpm` / `npm` |
GiteaMirror added the enhancementlocked labels 2026-04-13 07:23:35 -05:00
GiteaMirror commented 2026-04-13 07:23:37 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 27, 2026):

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

Thanks for the detailed report! I found the current peer dependencies in packages/expo/package.json:

  • expo-network: ^8.0.7 ← This is the issue - the caret constraint doesn't allow the jump to 55.x.x
  • expo-constants: >=17.0.0 ✓ Should work with SDK 55
  • expo-web-browser: >=14.0.0 ✓ Should work with SDK 55

The good news is that expo-constants and expo-web-browser use minimum version constraints (>=) which should be forward-compatible with SDK 55. The problem is specifically expo-network's caret constraint (^8.0.7), which limits versions to 8.x.x.

A simple fix would be changing expo-network from ^8.0.7 to >=8.0.7 (or a broader range like >=8.0.7 || >=55.0.0) to accommodate the new versioning scheme. All three dependencies are already marked as optional, so this change should be straightforward.

There's been recent activity on these peer dependencies (making expo-network optional in January 2026), so this is an actively maintained area of the codebase.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

<!-- gh-comment-id:3974123431 --> @dosubot[bot] commented on GitHub (Feb 27, 2026): <!-- Greeting --> Hi @gabrieleolmi! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the better-auth team. <!-- Answer --> Thanks for the detailed report! I found the current peer dependencies in [`packages/expo/package.json`](https://github.com/better-auth/better-auth/blob/074478e928624ca038a579817b47174ac15ef56a/packages/expo/package.json): - `expo-network`: `^8.0.7` ← **This is the issue** - the caret constraint doesn't allow the jump to `55.x.x` - `expo-constants`: `>=17.0.0` ✓ Should work with SDK 55 - `expo-web-browser`: `>=14.0.0` ✓ Should work with SDK 55 The good news is that `expo-constants` and `expo-web-browser` use minimum version constraints (`>=`) which should be forward-compatible with SDK 55. The problem is specifically `expo-network`'s caret constraint (`^8.0.7`), which limits versions to `8.x.x`. A simple fix would be changing `expo-network` from `^8.0.7` to `>=8.0.7` (or a broader range like `>=8.0.7 || >=55.0.0`) to accommodate the new versioning scheme. All three dependencies are already marked as optional, so this change should be straightforward. There's been [recent activity on these peer dependencies](https://github.com/better-auth/better-auth/pull/7655) (making `expo-network` optional in January 2026), so this is an actively maintained area of the codebase. <!-- 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/a0f5d3ba-6056-4f1b-8fe0-ab8c5070a090?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a0f5d3ba-6056-4f1b-8fe0-ab8c5070a090?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a0f5d3ba-6056-4f1b-8fe0-ab8c5070a090?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a0f5d3ba-6056-4f1b-8fe0-ab8c5070a090?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a0f5d3ba-6056-4f1b-8fe0-ab8c5070a090?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a0f5d3ba-6056-4f1b-8fe0-ab8c5070a090?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a0f5d3ba-6056-4f1b-8fe0-ab8c5070a090?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Thanks%20for%20the%20detailed%20report%21%20I%20found%20the%20current%20peer%20dependencies%20in%20%5B%60packages/expo/package.json%60%5D%28https%3A//github.com/better-auth/better-auth/blob/074478e928624ca038a579817b47174ac15ef56a/packages/expo/package.json%29%3A%0A%0A-%20%60expo-network%60%3A%20%60%5E8.0.7%60%20%E2%86%90%20%2A%2AThis%20is%20the%20issue%2A%2A%20-%20the%20caret%20constraint%20doesn%27t%20allow%20the%20jump%20to%20%6055.x.x%60%0A-%20%60expo-constants%60%3A%20%60%3E%3D17.0.0%60%20%E2%9C%93%20Should%20work%20with%20SDK%2055%0A-%20%60expo-web-browser%60%3A%20%60%3E%3D14.0.0%60%20%E2%9C%93%20Should%20work%20with%20SDK%2055%0A%0AThe%20good%20news%20is%20that%20%60expo-constants%60%20and%20%60expo-web-browser%60%20use%20minimum%20version%20constraints%20%28%60%3E%3D%60%29%20which%20should%20be%20forward-compatible%20with%20SDK%2055.%20The%20problem%20is%20specifically%20%60expo-network%60%27s%20caret%20constraint%20%28%60%5E8.0.7%60%29%2C%20which%20limits%20versions%20to%20%608.x.x%60.%0A%0AA%20simple%20fix%20would%20be%20changing%20%60expo-network%60%20from%20%60%5E8.0.7%60%20to%20%60%3E%3D8.0.7%60%20%28or%20a%20broader%20range%20like%20%60%3E%3D8.0.7%20%7C%7C%20%3E%3D55.0.0%60%29%20to%20accommodate%20the%20new%20versioning%20scheme.%20All%20three%20dependencies%20are%20already%20marked%20as%20optional%2C%20so%20this%20change%20should%20be%20straightforward.%0A%0AThere%27s%20been%20%5Brecent%20activity%20on%20these%20peer%20dependencies%5D%28https%3A//github.com/better-auth/better-auth/pull/7655%29%20%28making%20%60expo-network%60%20optional%20in%20January%202026%29%2C%20so%20this%20is%20an%20actively%20maintained%20area%20of%20the%20codebase.)&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/8189)
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 labels enhancement locked
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#11019