Summary
@coinbase/cds-mobile currently pins react-native: ~0.81.5 across all v9 releases (9.0.0–9.4.1). Apps on React Native 0.83.x cannot install CDS without --legacy-peer-deps, which is a hard blocker for projects following strict peer resolution.
Current peer requirement
Requested change
Widen the peer range to include 0.83.x, e.g.:
or upgrade the baseline to target Expo SDK 55/56 when that's available.
Context
React Native 0.83 ships with React 19.2 and has no user-facing breaking changes from 0.81. The React peer conflict that existed in CDS 8 is resolved in v9 — the remaining blocker is solely the react-native peer range.
Other peer deps that would also need revisiting for a 0.83 baseline: react-native-reanimated, react-native-gesture-handler, react-native-safe-area-context.
Impact
Any project on RN 0.83 / Expo SDK 55+ that wants to adopt CDS is blocked at install. This prevents adoption for teams keeping up with the RN release cadence.
Summary
@coinbase/cds-mobilecurrently pinsreact-native: ~0.81.5across all v9 releases (9.0.0–9.4.1). Apps on React Native 0.83.x cannot install CDS without--legacy-peer-deps, which is a hard blocker for projects following strict peer resolution.Current peer requirement
Requested change
Widen the peer range to include 0.83.x, e.g.:
or upgrade the baseline to target Expo SDK 55/56 when that's available.
Context
React Native 0.83 ships with React 19.2 and has no user-facing breaking changes from 0.81. The React peer conflict that existed in CDS 8 is resolved in v9 — the remaining blocker is solely the
react-nativepeer range.Other peer deps that would also need revisiting for a 0.83 baseline:
react-native-reanimated,react-native-gesture-handler,react-native-safe-area-context.Impact
Any project on RN 0.83 / Expo SDK 55+ that wants to adopt CDS is blocked at install. This prevents adoption for teams keeping up with the RN release cadence.