Skip to content

Add support for Expo SDK 55 and new package versioning scheme #8189

@gabrieleolmi

Description

@gabrieleolmi

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or improvementlockedLocked conversations after being closed for 7 days

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions