You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(deps): widen react-native-get-random-values peer range to 1.x || 2.x (#1284)
Allow consumers on the New Architecture (RN 0.81+/Expo SDK 54+) to use
react-native-get-random-values 2.x, which is required for New-Arch iOS
builds, while keeping 1.x working for older React Native versions.
Changes:
- core: peerDependency 1.x -> "1.x || 2.x" (consumer picks the version
compatible with their RN; old RN keeps 1.x, RN >=0.81 can use 2.x)
- sovran: move react-native-get-random-values from a hard dependency to a
peerDependency ("1.x || 2.x"). sovran's source never imports it; the
hard dependency force-resolved a single version for every consumer,
which is what blocked New-Arch users from installing 2.x. It is already
a documented install step in the README, so a peer is the correct
declaration.
- root: add it as a devDependency (^1.11.0) so the monorepo build/test
still resolves it for core's uuid polyfill (mirrors how
@react-native-async-storage/async-storage is handled).
Unlike PR #1174, this does NOT raise the floor to 2.x, so it does not
break consumers (or the e2e-compat example) on RN < 0.81.
Fixes#1102
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments