Skip to content

refactor(rn): bump expo SDK to 57 - #69

Open
simeng-li wants to merge 1 commit into
masterfrom
simeng-refactor-bump-expo-sdk-to-57
Open

refactor(rn): bump expo SDK to 57#69
simeng-li wants to merge 1 commit into
masterfrom
simeng-refactor-bump-expo-sdk-to-57

Conversation

@simeng-li

Copy link
Copy Markdown
Contributor

Summary

Relates to #68.

@logto/rn@1.2.0 caps the expo-crypto / expo-secure-store / expo-web-browser peer ranges at <57, so anyone on Expo SDK 57 gets invalid-peer warnings on install. Widen the caps to <58 and move the dev deps and the sample app onto Expo SDK 57 (RN 0.86.2, React 19.2.3) so the widened range is actually exercised.

No source changes — the SDK code is unaffected by the Expo 57 bump.

  • packages/rn/package.json: peer caps <57<58; dev deps to expo-*@57 and react-native@^0.86.2; version 1.2.01.3.0.
  • packages/rn-sample/package.json: Expo SDK 56 → 57 (expo, @expo/metro-runtime, expo-status-bar, expo-crypto, expo-secure-store, expo-web-browser, react/react-dom 19.2.3, react-native ~0.86.2), matching Expo 57's bundledNativeModules.

Testing

Tested locally

Checklist

  • .changeset
  • unit tests
  • integration tests
  • necessary TSDoc comments

Widen the expo-crypto / expo-secure-store / expo-web-browser peer caps to
<58 so Expo SDK 57 installs without invalid peer warnings. Bump the dev deps
and the sample app to Expo SDK 57 (RN 0.86, React 19.2.3).
@simeng-li
simeng-li requested review from a team, charIeszhao and wangsijie and removed request for a team August 31, 2026 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant