@oxy.so/services 11.2.0-oxy-one.5 → 11.2.0-oxy-one.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oxy.so/services",
-  "version": "11.2.0-oxy-one.5",
+  "version": "11.2.0-oxy-one.7",
   "description": "OxyHQ Expo/React Native SDK — UI components, screens, and native features",
   "main": "lib/commonjs/index.js",
   "module": "lib/module/index.js",
@@ -211,10 +211,10 @@
     "typescript": "^5.9.2",
     "zustand": "^5.0.14"
   },
-  "//@oxy.so/bloom": "RE-RAISE THIS FLOOR ON EVERY BREAKING BLOOM RELEASE, in the same commit as the root package.json catalog entry and the code that requires it. The breaking position is the MAJOR, so `^3.0.1` means `>=3.0.1 <4.0.0`: 3.x minors are admitted on semver's additive promise, and Bloom 4.0.0 is refused until someone raises this deliberately. The CAP is the part that is load-bearing. An earlier revision of this key recorded the opposite trade -- an uncapped `>=` floor, accepted so that intentionally-breaking Bloom 0.x minors would not be blocked -- and that trade is closed by evidence rather than by preference: an unbounded range is exactly what let `bun install` pair this package with Bloom 1.0.0 and emit no warning at all, and 1.0.0 broke it four ways (a deleted provider, a renamed confirm option, a renamed Chip fill, and two REMOVED SUBPATHS that fail at bundle time, before any typecheck runs). A floor is a claim about what was measured; a cap is the claim that nothing beyond it was. RAISED TO 3.0.1 from `^2.1.0`. Bloom 3.0.0 breaks exactly two things -- `PageHeader` defaults to `presentation=\"floating\"` and stops hiding the title under `transparent`, and `Field disabled` now reaches the control that reads the field context -- and THIS PACKAGE IMPORTS NEITHER: it renders no `PageHeader` and no `Field`, and 3.0 removes no subpath (unlike 2.0.0, which is why that floor cost code changes and this one does not). Its six `transparent` occurrences are CSS colour values, not the PageHeader prop. The cap had to move rather than widen to a union, because leaving `^2.1.0` in place is what made `bun install` resolve a SECOND, nested Bloom 2.12.4 under this package for any app on Bloom 3 -- two copies of a library whose 3.0 contracts (`control-surface`, `TopEdgeProvider`, `ScrollOffsetProvider`) are React contexts, so a provider from one copy cannot be read by a consumer from the other. Mention's `oxyRuntimeCompatibility` test is what caught it; nothing in a typecheck can. RAISED AGAIN TO 3.2.0 from `^3.0.1`, for the same class of reason the 2.x note records, only in the other direction: 3.2.0 ADDS the per-glyph icon subpaths (`@oxy.so/bloom/icons/RiAtLine`) that this package's screens now import instead of the `@oxy.so/bloom/icons` barrel, and a missing subpath fails at bundle time, in the consumer's Metro, long after this package has typechecked and shipped. `^3.0.1` would have admitted Bloom 3.0.1 and 3.1.0, neither of which has those subpaths, so the floor is the only thing standing between a consumer and a red build. Nothing else about 3.1.0 or 3.2.0 is required here; the cap stays at the major. RAISED TO ^4.2.0: FollowButton now delegates its visuals to Bloom media-header FollowButton with loading, textStyle and large size; the new shared UI contracts require one Bloom4 context across Services and its consumer. RAISED TO ^4.31.0: the sign-in and account screens type one-time codes into `InputOtp` with `type=\"alphanumeric\"` (the long sign-in code and backup codes), which 4.31.0 adds; older 4.x drops the letters. RAISED TO ^4.35.0: every password field passes `revealable` to `TextFieldInput` (the eye button, 4.35.0); older 4.x drops the prop silently and the password cannot be shown. The provider also mounts `@oxy.so/bloom/locale` (4.32.0+). RAISED TO ^5.1.0 (services 9.0.0, a major because consumers must move to Bloom 5 with it): Bloom 5.0.0 types `Card`'s `style` without radius, border width or `overflow` (geometry goes through `radius`/`border`/`clipContent`) and stops clipping a Card's children by default, so `BenefitList`'s `overflow: 'visible'` became both a type error and unnecessary; it is removed. The cap MOVES rather than widening to a `^4 || ^5` union, for the reason the 3.0.1 note records: a union lets an app resolve a second, nested Bloom copy and split the React contexts. The floor is 5.1.0 because that is the version measured here (every package builds and tests against it); 5.0.0 was not measured. RAISED TO ^6.0.0 (services 10.0.0, a major because consumers must move to Bloom 6 with it, and because this package's own `FollowButton`/`FollowTargetButton` `size` moves with Bloom's vocabulary): Bloom 6.0.0 removes the duplicate spellings its 5.x types still admitted, and this package used four of them. The control `size` narrows to `xs|sm|md|lg`, so every `small`/`medium`/`large` handed to a Bloom control became `sm`/`md`/`lg`, and the Follow buttons' public `size` became `sm|md|lg` because it is passed straight through to Bloom's media-header `FollowButton`. `Switch` is controlled by `checked`/`onCheckedChange`, not `value`/`onValueChange`. `Button` has no `variant`: each call site names `appearance` and `tone` (the pair the 5.x recipe resolved the variant to, so nothing repaints), `LinkButton`'s colour is `linkTone`, and `PeableButton` renders `InverseButton`. `Card` takes `appearance=\"outline\"` for `variant=\"outlined\"`. The deprecated spellings Bloom 6 still accepts (`isInvalid`, Chip `color`/`variant`) are not breaks and are left alone. The cap MOVES rather than widening to a `^5 || ^6` union, for the reason the 3.0.1 note records: a union lets an app resolve a second, nested Bloom copy and split the React contexts. The floor is 6.0.0 because that is the version measured when this raise was made; the workspace catalog has since moved to ^6.2.0, which adds only the `cover-header` subpath this package does not import, so the floor stays. MAINTENANCE 6.2.1: floor >=6.2.1 and cap <6.3.0 deliberately admit only the reviewed patch line with native Back/X completion and SVG paint/resize fixes. Known 6.4.0 lacks these fixes; the exact root catalog pin prevents a caret from selecting it. A broader minor range requires forward-port and consumer acceptance. VERIFIED 7.1.2: the additional >=7.1.2 <7.2.0 line contains the reviewed native fixes. Services build/types and the website real browser provider/theme tests pass with one byte-verified Bloom copy at both the root and Services importer. The root catalog remains pinned to 6.2.1; consumers explicitly choose one supported line. Versions 6.3.x, 6.4.x and 7.1.0/7.1.1 remain excluded. VERIFIED 7.7.0: admit the progressive media-preview release as another explicit line, so consumers selecting it share one Bloom provider/theme/font context with Services. Existing supported lines and the workspace catalog stay unchanged; unreviewed 7.2-7.6 and 7.8+ remain excluded. VERIFIED 7.13.1: admit the accessible bottom-sheet dialog release so consumers selecting this line share Bloom surface, theme and overlay contexts with Services. Stable Services 11.1.1 validates the unchanged 11.1.0 source against 7.13.1 with 1040 tests, types and packed exports; the existing catalog and other supported peer lines stay unchanged. VERIFIED 7.14.0: the additive outlined Stepper release is covered by Services build, types and 1040 tests against the published package on the 11.1 maintenance branch. VERIFIED 7.15.0: additive Button focus, hover and keyboard events; the stable maintenance line passes types and all 1040 tests against the official package, preserving the existing peer lines. VERIFIED 7.16.1: the stable 11.1 maintenance line passes types and all 1040 tests against the official Accordion, rating and Dialog release; packed exports are verified. Preserve every existing peer line. VERIFIED 7.17.0: Services 11.1.5 maintenance types, 1040 tests, fresh build and packed exports pass against the official additive Carousel/Search and dialog-focus release. Preserve the existing catalog and peer lines on main. VERIFIED 7.18/7.19: the 11.1 maintenance line passed types and 1040 tests separately against both official releases; this main line passed types and all 1042 tests against 7.19.0 after building its workspace dependencies. The root catalog remains 6.2.1; apps choose one admitted line. VERIFIED 7.20.0: additive viewport observation, opt-in Meter/RatingBar reveal and Dialog minimum side gutter; Services types and all 1042 tests pass against the release candidate tarball. Existing peer lines and the workspace catalog remain unchanged. VERIFIED 7.21.0: configurable Dialog/BottomSheet backdrop and transition preserve defaults; this main line passes types and all 1042 tests against the byte-verified release candidate. Existing supported peer lines and the workspace catalog remain unchanged. VERIFIED 7.22.0: controlled Collapsible and rich RadioGroup composition preserve Services compatibility; maintenance Services types and all 1040 tests pass against the release candidate, with unchanged 11.1.0 runtime source. Mercaria validates the composed purchase panels in eight browser scenarios and all four client typechecks. VERIFIED 7.27.0: exact ColorScope roles, local mode and portal propagation preserve Services defaults. This main line passes types and all 114 suites / 1042 tests against the official 7.27.0 package with a single Bloom resolution. Stable 11.1.13 maintenance also passes types and all 113 suites / 1040 tests. Preserve the existing main catalog and earlier admitted peer lines. VERIFIED 7.28.0: types and all 114 suites / 1042 tests pass with the official CSS 3.1.0-rc.0 / NativeWind 5.0.0-rc.0 compiler pair. Maintenance also verifies Expo 56.0.23 and RN 0.85.3; no runtime source or framework peer changes are required. VERIFIED 7.29.0: TypeScript and all 114 suites / 1042 tests pass with the paired NativeWind 5.0.0-rc.0 and react-native-css 3.1.0-rc.0. Optional gallery lifecycle callback preserves existing surface behavior; runtime source unchanged. VERIFIED 7.30.0: TypeScript and all 114 suites / 1042 tests pass against the video-overlay release candidate with one Bloom runtime; existing framework catalog and runtime source stay unchanged. VERIFIED 7.31.0: TypeScript and all 114 suites / 1042 tests pass against the official 7.31.0 package with one Bloom runtime. It adds the `video-view` subpath (expo-video's VideoView with `playsInline` on, so web video plays inline on iPhone Safari) and routes MediaSurface through it; this package imports neither, and runtime source and framework catalog stay unchanged. VERIFIED 7.32.0 AND 7.33.0 (11.2.0-oxy-one.4): each official package installed as the one Bloom resolution; types and all 115 suites / 1050 tests pass against both (and against the 6.2.1 catalog). 7.32.0 adds the shared agent-avatar renderer and Clippo; 7.33.0 adds the lean `settings-modal/modal` and `settings-modal/fields` entries. Both are additive (no subpath removed, no peer or dependency changed) and this package imports neither family. The cap moves to <7.34.0 so a 7.33 patch (7.33.1 restores web TextField side padding) needs no services release. The root catalog stays 6.2.1. Same verification and fix as maintenance 11.1.18. VERIFIED 8.0.0 (11.2.0-oxy-one.4): types and all 115 suites / 1050 tests pass with 8.0.0 as the one Bloom resolution. Its only break is that `LinkPreviewCard` leaves the root barrel for `@oxy.so/bloom/link-preview` (its cover now loads through `expo-image`, which the root barrel must not link); this package imports neither. The 8.0 line is admitted beside 7.x, so an app moves to Bloom 8 without a services major. VERIFIED 8.1.1 AND 9.0.0 (11.2.0-oxy-one.5): each installed as the one Bloom resolution (8.1.1 from the registry, 9.0.0 from the packed release candidate); types and all 115 suites / 1050 tests pass against both, and against the 6.2.1 catalog. 8.1.x adds the unified agent-avatar renderer and changes nothing this package imports. 9.0.0 removes the `small` / `medium` / `large` spellings from control sizes (Chip, Badge, Sidebar, Rating and others), renames `AlertDialog` / `Command` `visible` + `onClose` to `open` + `onOpenChange`, replaces the composer's `listening` with `voiceState`, and swaps the glass material for blur and tint; this package used one of those, Chip `size=\"small\"` (three screens), now `sm`, which every admitted line accepts. The 8.1 minor joins the 8.0 line (one 8.x range) and the 9.0 line is admitted beside the earlier ones. The root catalog stays 6.2.1.",
+  "//@oxy.so/bloom": "RE-RAISE THIS FLOOR ON EVERY BREAKING BLOOM RELEASE, in the same commit as the root package.json catalog entry and the code that requires it. The breaking position is the MAJOR, so `^3.0.1` means `>=3.0.1 <4.0.0`: 3.x minors are admitted on semver's additive promise, and Bloom 4.0.0 is refused until someone raises this deliberately. The CAP is the part that is load-bearing. An earlier revision of this key recorded the opposite trade -- an uncapped `>=` floor, accepted so that intentionally-breaking Bloom 0.x minors would not be blocked -- and that trade is closed by evidence rather than by preference: an unbounded range is exactly what let `bun install` pair this package with Bloom 1.0.0 and emit no warning at all, and 1.0.0 broke it four ways (a deleted provider, a renamed confirm option, a renamed Chip fill, and two REMOVED SUBPATHS that fail at bundle time, before any typecheck runs). A floor is a claim about what was measured; a cap is the claim that nothing beyond it was. RAISED TO 3.0.1 from `^2.1.0`. Bloom 3.0.0 breaks exactly two things -- `PageHeader` defaults to `presentation=\"floating\"` and stops hiding the title under `transparent`, and `Field disabled` now reaches the control that reads the field context -- and THIS PACKAGE IMPORTS NEITHER: it renders no `PageHeader` and no `Field`, and 3.0 removes no subpath (unlike 2.0.0, which is why that floor cost code changes and this one does not). Its six `transparent` occurrences are CSS colour values, not the PageHeader prop. The cap had to move rather than widen to a union, because leaving `^2.1.0` in place is what made `bun install` resolve a SECOND, nested Bloom 2.12.4 under this package for any app on Bloom 3 -- two copies of a library whose 3.0 contracts (`control-surface`, `TopEdgeProvider`, `ScrollOffsetProvider`) are React contexts, so a provider from one copy cannot be read by a consumer from the other. Mention's `oxyRuntimeCompatibility` test is what caught it; nothing in a typecheck can. RAISED AGAIN TO 3.2.0 from `^3.0.1`, for the same class of reason the 2.x note records, only in the other direction: 3.2.0 ADDS the per-glyph icon subpaths (`@oxy.so/bloom/icons/RiAtLine`) that this package's screens now import instead of the `@oxy.so/bloom/icons` barrel, and a missing subpath fails at bundle time, in the consumer's Metro, long after this package has typechecked and shipped. `^3.0.1` would have admitted Bloom 3.0.1 and 3.1.0, neither of which has those subpaths, so the floor is the only thing standing between a consumer and a red build. Nothing else about 3.1.0 or 3.2.0 is required here; the cap stays at the major. RAISED TO ^4.2.0: FollowButton now delegates its visuals to Bloom media-header FollowButton with loading, textStyle and large size; the new shared UI contracts require one Bloom4 context across Services and its consumer. RAISED TO ^4.31.0: the sign-in and account screens type one-time codes into `InputOtp` with `type=\"alphanumeric\"` (the long sign-in code and backup codes), which 4.31.0 adds; older 4.x drops the letters. RAISED TO ^4.35.0: every password field passes `revealable` to `TextFieldInput` (the eye button, 4.35.0); older 4.x drops the prop silently and the password cannot be shown. The provider also mounts `@oxy.so/bloom/locale` (4.32.0+). RAISED TO ^5.1.0 (services 9.0.0, a major because consumers must move to Bloom 5 with it): Bloom 5.0.0 types `Card`'s `style` without radius, border width or `overflow` (geometry goes through `radius`/`border`/`clipContent`) and stops clipping a Card's children by default, so `BenefitList`'s `overflow: 'visible'` became both a type error and unnecessary; it is removed. The cap MOVES rather than widening to a `^4 || ^5` union, for the reason the 3.0.1 note records: a union lets an app resolve a second, nested Bloom copy and split the React contexts. The floor is 5.1.0 because that is the version measured here (every package builds and tests against it); 5.0.0 was not measured. RAISED TO ^6.0.0 (services 10.0.0, a major because consumers must move to Bloom 6 with it, and because this package's own `FollowButton`/`FollowTargetButton` `size` moves with Bloom's vocabulary): Bloom 6.0.0 removes the duplicate spellings its 5.x types still admitted, and this package used four of them. The control `size` narrows to `xs|sm|md|lg`, so every `small`/`medium`/`large` handed to a Bloom control became `sm`/`md`/`lg`, and the Follow buttons' public `size` became `sm|md|lg` because it is passed straight through to Bloom's media-header `FollowButton`. `Switch` is controlled by `checked`/`onCheckedChange`, not `value`/`onValueChange`. `Button` has no `variant`: each call site names `appearance` and `tone` (the pair the 5.x recipe resolved the variant to, so nothing repaints), `LinkButton`'s colour is `linkTone`, and `PeableButton` renders `InverseButton`. `Card` takes `appearance=\"outline\"` for `variant=\"outlined\"`. The deprecated spellings Bloom 6 still accepts (`isInvalid`, Chip `color`/`variant`) are not breaks and are left alone. The cap MOVES rather than widening to a `^5 || ^6` union, for the reason the 3.0.1 note records: a union lets an app resolve a second, nested Bloom copy and split the React contexts. The floor is 6.0.0 because that is the version measured when this raise was made; the workspace catalog has since moved to ^6.2.0, which adds only the `cover-header` subpath this package does not import, so the floor stays. MAINTENANCE 6.2.1: floor >=6.2.1 and cap <6.3.0 deliberately admit only the reviewed patch line with native Back/X completion and SVG paint/resize fixes. Known 6.4.0 lacks these fixes; the exact root catalog pin prevents a caret from selecting it. A broader minor range requires forward-port and consumer acceptance. VERIFIED 7.1.2: the additional >=7.1.2 <7.2.0 line contains the reviewed native fixes. Services build/types and the website real browser provider/theme tests pass with one byte-verified Bloom copy at both the root and Services importer. The root catalog remains pinned to 6.2.1; consumers explicitly choose one supported line. Versions 6.3.x, 6.4.x and 7.1.0/7.1.1 remain excluded. VERIFIED 7.7.0: admit the progressive media-preview release as another explicit line, so consumers selecting it share one Bloom provider/theme/font context with Services. Existing supported lines and the workspace catalog stay unchanged; unreviewed 7.2-7.6 and 7.8+ remain excluded. VERIFIED 7.13.1: admit the accessible bottom-sheet dialog release so consumers selecting this line share Bloom surface, theme and overlay contexts with Services. Stable Services 11.1.1 validates the unchanged 11.1.0 source against 7.13.1 with 1040 tests, types and packed exports; the existing catalog and other supported peer lines stay unchanged. VERIFIED 7.14.0: the additive outlined Stepper release is covered by Services build, types and 1040 tests against the published package on the 11.1 maintenance branch. VERIFIED 7.15.0: additive Button focus, hover and keyboard events; the stable maintenance line passes types and all 1040 tests against the official package, preserving the existing peer lines. VERIFIED 7.16.1: the stable 11.1 maintenance line passes types and all 1040 tests against the official Accordion, rating and Dialog release; packed exports are verified. Preserve every existing peer line. VERIFIED 7.17.0: Services 11.1.5 maintenance types, 1040 tests, fresh build and packed exports pass against the official additive Carousel/Search and dialog-focus release. Preserve the existing catalog and peer lines on main. VERIFIED 7.18/7.19: the 11.1 maintenance line passed types and 1040 tests separately against both official releases; this main line passed types and all 1042 tests against 7.19.0 after building its workspace dependencies. The root catalog remains 6.2.1; apps choose one admitted line. VERIFIED 7.20.0: additive viewport observation, opt-in Meter/RatingBar reveal and Dialog minimum side gutter; Services types and all 1042 tests pass against the release candidate tarball. Existing peer lines and the workspace catalog remain unchanged. VERIFIED 7.21.0: configurable Dialog/BottomSheet backdrop and transition preserve defaults; this main line passes types and all 1042 tests against the byte-verified release candidate. Existing supported peer lines and the workspace catalog remain unchanged. VERIFIED 7.22.0: controlled Collapsible and rich RadioGroup composition preserve Services compatibility; maintenance Services types and all 1040 tests pass against the release candidate, with unchanged 11.1.0 runtime source. Mercaria validates the composed purchase panels in eight browser scenarios and all four client typechecks. VERIFIED 7.27.0: exact ColorScope roles, local mode and portal propagation preserve Services defaults. This main line passes types and all 114 suites / 1042 tests against the official 7.27.0 package with a single Bloom resolution. Stable 11.1.13 maintenance also passes types and all 113 suites / 1040 tests. Preserve the existing main catalog and earlier admitted peer lines. VERIFIED 7.28.0: types and all 114 suites / 1042 tests pass with the official CSS 3.1.0-rc.0 / NativeWind 5.0.0-rc.0 compiler pair. Maintenance also verifies Expo 56.0.23 and RN 0.85.3; no runtime source or framework peer changes are required. VERIFIED 7.29.0: TypeScript and all 114 suites / 1042 tests pass with the paired NativeWind 5.0.0-rc.0 and react-native-css 3.1.0-rc.0. Optional gallery lifecycle callback preserves existing surface behavior; runtime source unchanged. VERIFIED 7.30.0: TypeScript and all 114 suites / 1042 tests pass against the video-overlay release candidate with one Bloom runtime; existing framework catalog and runtime source stay unchanged. VERIFIED 7.31.0: TypeScript and all 114 suites / 1042 tests pass against the official 7.31.0 package with one Bloom runtime. It adds the `video-view` subpath (expo-video's VideoView with `playsInline` on, so web video plays inline on iPhone Safari) and routes MediaSurface through it; this package imports neither, and runtime source and framework catalog stay unchanged. VERIFIED 7.32.0 AND 7.33.0 (11.2.0-oxy-one.4): each official package installed as the one Bloom resolution; types and all 115 suites / 1050 tests pass against both (and against the 6.2.1 catalog). 7.32.0 adds the shared agent-avatar renderer and Clippo; 7.33.0 adds the lean `settings-modal/modal` and `settings-modal/fields` entries. Both are additive (no subpath removed, no peer or dependency changed) and this package imports neither family. The cap moves to <7.34.0 so a 7.33 patch (7.33.1 restores web TextField side padding) needs no services release. The root catalog stays 6.2.1. Same verification and fix as maintenance 11.1.18. VERIFIED 8.0.0 (11.2.0-oxy-one.4): types and all 115 suites / 1050 tests pass with 8.0.0 as the one Bloom resolution. Its only break is that `LinkPreviewCard` leaves the root barrel for `@oxy.so/bloom/link-preview` (its cover now loads through `expo-image`, which the root barrel must not link); this package imports neither. The 8.0 line is admitted beside 7.x, so an app moves to Bloom 8 without a services major. VERIFIED 8.1.1 AND 9.0.0 (11.2.0-oxy-one.5): each installed as the one Bloom resolution (8.1.1 from the registry, 9.0.0 from the packed release candidate); types and all 115 suites / 1050 tests pass against both, and against the 6.2.1 catalog. 8.1.x adds the unified agent-avatar renderer and changes nothing this package imports. 9.0.0 removes the `small` / `medium` / `large` spellings from control sizes (Chip, Badge, Sidebar, Rating and others), renames `AlertDialog` / `Command` `visible` + `onClose` to `open` + `onOpenChange`, replaces the composer's `listening` with `voiceState`, and swaps the glass material for blur and tint; this package used one of those, Chip `size=\"small\"` (three screens), now `sm`, which every admitted line accepts. The 8.1 minor joins the 8.0 line (one 8.x range) and the 9.0 line is admitted beside the earlier ones. The root catalog stays 6.2.1. VERIFIED 10.0.0 (11.2.0-oxy-one.7): installed from the registry as the one Bloom resolution; types and all 115 suites / 1050 tests pass. 10.0.0 makes an avatar one flat `AvatarCharacter` and removes `AvatarConfig` with its constants from `@oxy.so/bloom/agent-avatar`; this package imports nothing from that family, so nothing here changes. The 10.0 line is admitted beside the earlier ones. The root catalog stays 6.2.1.",
   "peerDependencies": {
     "@expo/vector-icons": "^15.0.3",
-    "@oxy.so/bloom": ">=6.2.1 <6.3.0 || >=7.1.2 <7.2.0 || >=7.7.0 <7.8.0 || >=7.13.1 <7.34.0 || >=8.0.0 <8.2.0 || >=9.0.0 <9.1.0",
+    "@oxy.so/bloom": ">=6.2.1 <6.3.0 || >=7.1.2 <7.2.0 || >=7.7.0 <7.8.0 || >=7.13.1 <7.34.0 || >=8.0.0 <8.2.0 || >=9.0.0 <9.1.0 || >=10.0.0",
     "@oxy.so/core": "4.5.0-oxy-one.1",
     "@react-native-async-storage/async-storage": "^2.0.0",
     "@react-native-community/netinfo": ">=11.4.1 <13.0.0",