-
Notifications
You must be signed in to change notification settings - Fork 424
fix(expo): Resolve Peer Dependency issue for Expo 54 users #7579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(expo): Resolve Peer Dependency issue for Expo 54 users #7579
Conversation
🦋 Changeset detectedLatest commit: ff922a7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThe peer dependency declarations for 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ 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. Comment |
@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
tmilewski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙃 We're going to want to add a changeset for this.
chriscanin
commented
Jan 13, 2026
Will do @jacekradko @tmilewski
...-clerkclerk-expo-requires-legacy
Uh oh!
There was an error while loading. Please reload this page.
Description
Currently React Native Expo users on Expo 54 who try to install clerk with
npm install @clerk/clerk-expofail unless they supply --legacy-peer-deps when using npm.We have set in our
pnpm-workspace.yaml: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:
Expo package then sets:
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.