fix(expo): Resolve Peer Dependency issue for Expo 54 users

[chriscanin]

Description

Currently React Native Expo users on Expo 54 who try to install clerk with npm install @clerk/clerk-expo fail unless they supply --legacy-peer-deps when using npm.
We have set in our pnpm-workspace.yaml:

 catalogs:
   peer-react:
     react: ^18.0.0 || ~19.0.3 || ~19.1.4 || ~19.2.3 || ~19.3.0-0
     react-dom: ^18.0.0 || ~19.0.3 || ~19.1.4 || ~19.2.3 || ~19.3.0-0

But Expo 54 expects react 19.1.0, and although you could change that, expo will then warn you to run npx expo install --fix, which will revert your react version to 19.1.0....

But React 19.1.0 is unsafe!! , Expo says, not for us:
https://expo.dev/changelog/mitigating-critical-security-vulnerability-in-react-server-components

I see two paths forward. We document well, and tell users it is safe to force legacy peer dependency resolution, or we can loosen the peer dependencies versions react-native. Not really sure if this is done in other places but possibly overriding that peer-react for react-native like:

 catalogs:
   peer-react:
     react: ^18.0.0 || ~19.0.3 || ~19.1.4 || ~19.2.3 || ~19.3.0-0
     react-dom: ^18.0.0 || ~19.0.3 || ~19.1.4 || ~19.2.3 || ~19.3.0-0
   peer-react-native:  # adjusted for client-only Expo apps
     react: ^18.0.0 || ~19.0.0 || ~19.1.0 || ~19.2.0 || ~19.3.0-0

Expo package then sets:

"peerDependencies": {
   "react": "catalog:peer-react-native",
   "react-dom": "catalog:peer-react-native",
   ...
 }

Checklist

• pnpm test runs as expected.
• pnpm build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Summary by CodeRabbit

• Chores
  • Broadened React compatibility to explicitly support React 18 and React 19 in the Expo package peer dependencies.
  • Added a patch changeset to document and release this compatibility update for the Expo package.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

🦋 Changeset detected

Latest commit: ff922a7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/expo	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jan 13, 2026 7:38pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The peer dependency declarations for react and react-dom in packages/expo/package.json were updated from catalog-based references (catalog:peer-react) to explicit version ranges. Both dependencies now specify compatibility with React 18 and multiple React 19 minor versions through the range ^18.0.0 || ~19.0.0 || ~19.1.0 || ~19.2.0 || ~19.3.0-0. This change replaces the previous resolver mechanism with direct version specifications.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately summarizes the main change: updating peer dependency version ranges for React to resolve installation issues for Expo 54 users.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@7579

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@7579

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@7579

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@7579

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@7579

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@7579

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@7579

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@7579

@clerk/express

npm i https://pkg.pr.new/@clerk/express@7579

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@7579

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@7579

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@7579

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@7579

@clerk/react

npm i https://pkg.pr.new/@clerk/react@7579

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@7579

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@7579

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@7579

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@7579

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@7579

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@7579

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@7579

commit: ff922a7

[tmilewski]

🙃 We're going to want to add a changeset for this.

[chriscanin]

Will do @jacekradko @tmilewski