@oxyhq/bloom 0.79.0 → 0.79.1

package/src/scroll/store.ts

@@ -3,16 +3,12 @@
  *
  * This file deliberately contains NO React and NO DOM/native imports so the
  * logic can be unit-tested in isolation and shared verbatim by the web and
- * native barrels. The web barrel drives it with real scroll offsets; the
- * native barrel never instantiates it (native-stack already restores scroll).
+ * native barrels.
  */
-
 /**
- * Separator between the navigation route key and an optional caller-supplied
- * sub-key. A route may host more than one independently-scrolling list (e.g.
- * a tabbed profile screen), so each list contributes its own sub-key.
+ * Separator between the two components of a storage key.
  *
- * `\0` (NUL) can never appear in a React Navigation route key or in a
+ * `\0` (NUL) can never appear in a router-derived content id or in a
  * developer-authored sub-key, so it is collision-free as a delimiter. It is
  * written as an escape sequence (not a literal byte) so the source stays
  * text-diffable.
@@ -20,31 +16,51 @@
 const COMPOSITE_KEY_SEPARATOR = '\0';
 
 /**
- * Derive the storage key for a scrollable from its owning route key and an
- * optional caller sub-key.
+ * Derive the storage key for a scrollable from WHAT its screen is showing plus
+ * an optional caller sub-key.
+ *
+ * The key is CONTENT identity, deliberately not the navigation entry. An offset
+ * belongs to what the user was looking at, so returning to it restores however
+ * they got there — browser Back or Forward, a tab press, an in-app link — and
+ * only content never seen this session opens at the top. Keying on the entry
+ * would defeat that: a tab press and `router.replace` both mint a fresh entry,
+ * so both would open at the top even though the user has been there.
+ *
+ * The trade, chosen rather than overlooked: the same content occupying two LIVE
+ * entries now shares one offset. Pushing `/@alice` on top of `/@alice` in a
+ * native stack restores the first one's position instead of opening at the top,
+ * and while both are mounted each writes to the same key. That is the price of
+ * a tab press restoring, which is the behaviour that was asked for.
  *
- * - `routeKey` is React Navigation's stable per-route `route.key`.
- * - `subKey` distinguishes multiple scrollables that share a single route.
+ * The key is always the same two-field composite, with an absent sub-key
+ * written as empty, so two different identities can never collapse onto one key
+ * by omission.
  *
- * Returns `null` when there is no route key to anchor against (the scrollable
- * is not inside a navigator), which the caller treats as "do not persist".
+ * Returns `null` when there is no content id to anchor against (the scrollable
+ * is not inside a navigator, or the adapter cannot answer), which every caller
+ * treats as "do not persist and do not restore".
  */
 export function deriveScrollKey(
-  routeKey: string | undefined,
+  contentId: string | null,
   subKey?: string,
 ): string | null {
-  if (!routeKey) return null;
-  if (subKey === undefined || subKey === '') return routeKey;
-  return `${routeKey}${COMPOSITE_KEY_SEPARATOR}${subKey}`;
+  if (!contentId) return null;
+  return [contentId, subKey ?? ''].join(COMPOSITE_KEY_SEPARATOR);
 }
 
 /**
  * In-memory map of `scrollKey -> last-known scroll offset`.
  *
- * Mirrors the semantics of Bluesky's `Map<screenKey, scrollY>`: offsets live
- * only for the lifetime of the document/session. We never persist them — a
- * full reload should start at the top — and we never auto-evict, because a
- * route can be revisited via browser Forward/Back long after it blurred.
+ * Offsets live only for the lifetime of the document/session. We never persist
+ * them — a full reload should start at the top — and we never auto-evict,
+ * because an entry can be revisited via browser Forward/Back long after it
+ * blurred.
+ *
+ * Deliberately an instance held in React context rather than a module-level
+ * singleton: a dependency tree can legitimately contain two copies of Bloom
+ * (a hoisted one plus a nested one under another Oxy package), and a
+ * module-global would then exist twice with no way for either half to see the
+ * other's offsets.
  */
 export class ScrollOffsetStore {
   private readonly offsets = new Map<string, number>();
@@ -55,19 +71,25 @@ export class ScrollOffsetStore {
   }
 
   /**
-   * Read the saved offset for a key. Returns `0` when nothing was saved, so
-   * callers can restore unconditionally (an unseen list restores to the top).
+   * Read the saved offset for a key. Returns `0` when nothing was saved, which
+   * is the same value a caller writes when {@link has} is false — an unseen
+   * list restores to the top.
    */
   read(key: string): number {
     return this.offsets.get(key) ?? 0;
   }
 
-  /** Whether an offset was ever saved for this key. */
+  /**
+   * Whether an offset was ever saved for this key. This — not `read() > 0` —
+   * is what separates "restore" from "reset": a key that was never seen and a
+   * key deliberately saved at the top both read 0, and only the store knows
+   * which is which.
+   */
   has(key: string): boolean {
     return this.offsets.has(key);
   }
 
-  /** Drop a saved offset (e.g. when a route is permanently removed). */
+  /** Drop a saved offset (e.g. when an entry is permanently removed). */
   forget(key: string): void {
     this.offsets.delete(key);
   }

package/src/scroll/types.ts

@@ -1,21 +1,25 @@
 import type { ReactNode, RefObject } from 'react';
+import type { NativeScrollEvent, NativeSyntheticEvent } from 'react-native';
 
 /**
  * Anything `useScrollRestoration` knows how to read/write a vertical scroll
  * offset from. The hook accepts a ref to one of these:
  *
- * - a React Native `ScrollView` / `FlatList` ref (which on web is backed by a
- *   DOM node and exposes `getScrollableNode()`),
+ * - a React Native `ScrollView` / `FlatList` / `FlashList` ref (which on web is
+ *   backed by a DOM node and exposes `getScrollableNode()`),
  * - a raw DOM element ref (when a component renders its own scroll container),
- * - the literal `'window'` sentinel, for the rare layout where the list IS the
- *   window scroller (matches Bluesky's default).
+ * - the literal `'window'` sentinel, for the layout where the list IS the
+ *   document scroller.
  *
- * Native never reads any of these — the native hook is a no-op — so the type is
- * intentionally permissive rather than coupled to a specific RN class.
+ * The two imperative methods are the native write path; web writes `scrollTop`
+ * on the resolved DOM node instead. Both are optional because a given ref only
+ * ever exposes one of them (list vs. scroll view).
  */
 export interface ScrollableHandle {
-  /** Imperative scroll API exposed by RN scrollables. */
+  /** `ScrollView`'s imperative scroll API. */
   scrollTo?: (options: { x?: number; y?: number; animated?: boolean }) => void;
+  /** `FlatList`/`FlashList`'s imperative scroll API. */
+  scrollToOffset?: (options: { offset: number; animated?: boolean }) => void;
   /** Web/RNW path: returns the underlying DOM node. */
   getScrollableNode?: () => unknown;
 }
@@ -28,21 +32,87 @@ export type ScrollRestorationTarget =
   | RefObject<unknown>
   | 'window';
 
+/** The effect shape `useScreenFocusEffect` runs — mirrors `useEffect`'s. */
+export type ScreenFocusEffect = () => (() => void) | void;
+
+/**
+ * The router bindings the scroll core needs, and the ONLY thing it knows about
+ * routing. Keeping this to two hooks is what lets the core ship without a
+ * router import, so a Vite/SPA consumer can supply its own adapter (or none).
+ *
+ * Both members are HOOKS: the core calls them from `useScrollRestoration`, so
+ * the adapter value must be referentially stable for the lifetime of the
+ * provider (a module-level constant, which is what every adapter Bloom ships
+ * is). Swapping in a different adapter at runtime would change the hook order
+ * of every consumer below it.
+ */
+export interface ScrollRouterAdapter {
+  /**
+   * Identify WHAT the calling screen is showing — its route and params, not the
+   * history slot it occupies. Offsets are remembered per content, so returning
+   * to something already seen restores it however the user got there.
+   *
+   * It must describe the screen the CALLER is rendered inside, never the
+   * globally focused one: a background screen has to keep reporting its own
+   * content, or it would save its offset under the foreground screen's key.
+   *
+   * `null` when the adapter cannot answer (a scrollable rendered outside any
+   * navigator), which makes the hook inert rather than guessing.
+   */
+  useScreenContentId(): string | null;
+  /**
+   * Run `effect` while the calling screen is focused, and its cleanup on blur.
+   * Re-runs when `effect`'s identity changes AND the screen is focused — that
+   * is what makes an in-screen key change (a tab or folder swap) visible to a
+   * hook that never blurred.
+   */
+  useScreenFocusEffect(effect: ScreenFocusEffect): void;
+}
+
 export interface UseScrollRestorationOptions {
   /**
-   * Sub-key to disambiguate multiple scrollables that live on the same route
-   * (e.g. the tabs of a profile screen). Combined with the active route key to
-   * form the storage key. Omit when a route has a single scrollable.
+   * Sub-key distinguishing scrollables that share one screen AND one content
+   * id — the tabs of a profile, the folders of a saved-items screen. Changing
+   * it while the screen stays focused saves the outgoing list's offset and
+   * restores (or resets) the incoming one.
    */
   key?: string;
   /**
-   * When `false`, the hook is inert (saves and restores are skipped). Useful to
-   * gate restoration behind a feature flag without changing call sites.
+   * When `false` the hook is completely inert: no save, no restore, no reset.
+   *
+   * On NATIVE this is load-bearing rather than a feature flag. Restoring into a
+   * list whose rows have not been laid out yet lands at the wrong place (or is
+   * clamped away), and native has no equivalent of the web path's re-apply
+   * loop — so the caller gates on its own content being present, e.g.
+   * `enabled: rows.length > 0`. Flipping it from `false` to `true` is what
+   * triggers the restore.
+   *
    * Defaults to `true`.
    */
   enabled?: boolean;
 }
 
+/**
+ * What `useScrollRestoration` hands back. Identical on both platforms so call
+ * sites are written once.
+ */
+export interface ScrollRestorationBinding {
+  /**
+   * Wire onto the list being restored: `<FlashList onScroll={scroll.onScroll}>`.
+   *
+   * Native has no way to observe a list's offset from outside it, so this is
+   * how offsets are recorded there. On web it is a stable no-op — the web path
+   * subscribes to the resolved DOM node's own `scroll` event, which needs
+   * nothing from the caller — and passing it costs nothing.
+   */
+  onScroll: (event: NativeSyntheticEvent<NativeScrollEvent>) => void;
+}
+
 export interface ScrollRestorationProviderProps {
   children: ReactNode;
+  /**
+   * Binds the store to a router. Must be referentially stable — see
+   * {@link ScrollRouterAdapter}.
+   */
+  adapter: ScrollRouterAdapter;
 }

package/src/theme/__tests__/__fixtures__/golden-resolved-tokens.json

@@ -366,7 +366,7 @@
     "--surface-foreground": "rgb(36 26 14)",
     "--popover": "rgb(255 234 215)",
     "--popover-foreground": "rgb(36 26 14)",
-    "--primary": "rgb(157 99 0)",
+    "--primary": "rgb(150 94 0)",
     "--primary-foreground": "rgb(255 255 255)",
     "--secondary": "rgb(0 117 141)",
     "--secondary-foreground": "rgb(255 255 255)",
@@ -486,8 +486,8 @@
     "--surface-foreground": "rgb(33 27 13)",
     "--popover": "rgb(250 236 213)",
     "--popover-foreground": "rgb(33 27 13)",
-    "--primary": "rgb(255 195 0)",
-    "--primary-foreground": "rgb(0 0 0)",
+    "--primary": "rgb(135 102 0)",
+    "--primary-foreground": "rgb(255 255 255)",
     "--secondary": "rgb(0 114 158)",
     "--secondary-foreground": "rgb(255 255 255)",
     "--tertiary": "rgb(117 66 250)",
@@ -1446,8 +1446,8 @@
     "--surface-foreground": "rgb(24 29 18)",
     "--popover": "rgb(234 240 222)",
     "--popover-foreground": "rgb(24 29 18)",
-    "--primary": "rgb(139 255 0)",
-    "--primary-foreground": "rgb(0 0 0)",
+    "--primary": "rgb(63 120 0)",
+    "--primary-foreground": "rgb(255 255 255)",
     "--secondary": "rgb(79 79 255)",
     "--secondary-foreground": "rgb(255 255 255)",
     "--tertiary": "rgb(190 36 152)",

package/src/theme/__tests__/__snapshots__/visual-gallery.test.tsx.snap

@@ -47,14 +47,14 @@ exports[`theme.colors snapshot for all presets (catches unintended palette shift
     "contrast50": "rgb(249 229 209)",
     "error": "rgb(203 41 46)",
     "icon": "rgb(84 68 50)",
-    "iconActive": "rgb(157 99 0)",
+    "iconActive": "rgb(150 94 0)",
     "info": "rgb(5 102 217)",
     "negative": "rgb(186 26 26)",
     "negativeForeground": "rgb(255 255 255)",
     "negativeSubtle": "rgba(239, 68, 68, 0.13)",
     "negativeSubtleForeground": "rgb(167 55 53)",
     "overlay": "rgba(0, 0, 0, 0.5)",
-    "primary": "rgb(157 99 0)",
+    "primary": "rgb(150 94 0)",
     "primaryDark": "rgb(255 241 229)",
     "primaryForeground": "rgb(255 255 255)",
     "primaryLight": "rgb(255 241 229)",
@@ -69,7 +69,7 @@ exports[`theme.colors snapshot for all presets (catches unintended palette shift
     "text": "rgb(36 26 14)",
     "textSecondary": "rgb(84 68 50)",
     "textTertiary": "rgb(135 116 96)",
-    "tint": "rgb(157 99 0)",
+    "tint": "rgb(150 94 0)",
     "warning": "rgb(150 94 0)",
   },
   "blue/dark": {
@@ -187,16 +187,16 @@ exports[`theme.colors snapshot for all presets (catches unintended palette shift
     "contrast50": "rgb(228 235 216)",
     "error": "rgb(203 41 46)",
     "icon": "rgb(65 73 57)",
-    "iconActive": "rgb(139 255 0)",
+    "iconActive": "rgb(63 120 0)",
     "info": "rgb(5 102 217)",
     "negative": "rgb(186 26 26)",
     "negativeForeground": "rgb(255 255 255)",
     "negativeSubtle": "rgba(239, 68, 68, 0.13)",
     "negativeSubtleForeground": "rgb(167 55 53)",
     "overlay": "rgba(0, 0, 0, 0.5)",
-    "primary": "rgb(139 255 0)",
+    "primary": "rgb(63 120 0)",
     "primaryDark": "rgb(240 246 227)",
-    "primaryForeground": "rgb(0 0 0)",
+    "primaryForeground": "rgb(255 255 255)",
     "primaryLight": "rgb(240 246 227)",
     "primarySubtle": "rgba(87, 163, 0, 0.13)",
     "primarySubtleForeground": "rgb(40 80 0)",
@@ -209,7 +209,7 @@ exports[`theme.colors snapshot for all presets (catches unintended palette shift
     "text": "rgb(24 29 18)",
     "textSecondary": "rgb(65 73 57)",
     "textTertiary": "rgb(114 122 103)",
-    "tint": "rgb(139 255 0)",
+    "tint": "rgb(63 120 0)",
     "warning": "rgb(150 94 0)",
   },
   "green/dark": {
@@ -887,16 +887,16 @@ exports[`theme.colors snapshot for all presets (catches unintended palette shift
     "contrast50": "rgb(244 231 208)",
     "error": "rgb(203 41 46)",
     "icon": "rgb(79 70 49)",
-    "iconActive": "rgb(255 195 0)",
+    "iconActive": "rgb(135 102 0)",
     "info": "rgb(5 102 217)",
     "negative": "rgb(186 26 26)",
     "negativeForeground": "rgb(255 255 255)",
     "negativeSubtle": "rgba(239, 68, 68, 0.13)",
     "negativeSubtleForeground": "rgb(167 55 53)",
     "overlay": "rgba(0, 0, 0, 0.5)",
-    "primary": "rgb(255 195 0)",
+    "primary": "rgb(135 102 0)",
     "primaryDark": "rgb(255 242 221)",
-    "primaryForeground": "rgb(0 0 0)",
+    "primaryForeground": "rgb(255 255 255)",
     "primaryLight": "rgb(255 242 221)",
     "primarySubtle": "rgba(182, 138, 0, 0.13)",
     "primarySubtleForeground": "rgb(90 67 0)",
@@ -909,7 +909,7 @@ exports[`theme.colors snapshot for all presets (catches unintended palette shift
     "text": "rgb(33 27 13)",
     "textSecondary": "rgb(79 70 49)",
     "textTertiary": "rgb(130 118 95)",
-    "tint": "rgb(255 195 0)",
+    "tint": "rgb(135 102 0)",
     "warning": "rgb(150 94 0)",
   },
 }

package/src/theme/__tests__/policy-legibility.test.ts

@@ -117,11 +117,12 @@ describe('colour policy legibility', () => {
   });
 
 
-  // The budget must apply to BOTH modes. Exempting dark so the fill could stay on
-  // the brand hex left every Follow button, avatar and chat bubble with a black
-  // label there while light had eleven white ones — an asymmetry nobody chose,
-  // and invisible to the suite because each half was individually legible.
-  it('the brand fill carries the same label pattern in both modes', () => {
+  // The two modes want opposite things and the suite has to say which. Applying
+  // the budget in LIGHT let a light seed keep its own tone there, so faircoin
+  // rendered the same pale lime in both modes — no theme at all. Skipping it in
+  // DARK left every Follow button, avatar and chat bubble with a black label.
+  // Each half was individually legible, so nothing else could catch either.
+  it('the brand fill keeps light exemption-free and dark budgeted', () => {
     const white = { light: 0, dark: 0 };
     for (const preset of APP_COLOR_NAMES) {
       for (const mode of ['light', 'dark'] as const) {
@@ -130,7 +131,9 @@ describe('colour policy legibility', () => {
         }
       }
     }
-    expect(white.dark).toBe(white.light);
-    expect(white.light).toBeGreaterThan(0);
+    // Light admits no exemption, so every preset carries white there. Dark keeps
+    // the budget, so the seeds that are already light keep their colour instead.
+    expect(white.light).toBe(APP_COLOR_NAMES.length);
+    expect(white.dark).toBeGreaterThan(APP_COLOR_NAMES.length - 4);
   });
 });

package/src/theme/color-policy.ts

@@ -214,18 +214,19 @@ function vividHueNear(hue: number): number {
  * why 11 of the 13 presets carry white and exactly the two light ones do not.
  */
 function whiteLabelTone(palette: TonalPalette, seedTone: number, isDark: boolean): number {
-  // ONE rule, both modes. The fill comes down to the tone a white label needs,
-  // unless the descent costs more than the budget and destroys the colour — then
-  // it keeps its own tone and takes a black label. Exempting dark, so the fill
-  // could stay on the brand hex, is what left every Follow button, avatar and
-  // chat bubble with a black label there while light had eleven white ones: an
-  // asymmetry nobody chose, visible in every component at once because they all
-  // read the same token.
-  const target = isDark ? DARK_FILL_TONE : LIGHT_FILL_TONE;
-  const candidate = Math.max(target, seedTone - TONE_BUDGET);
+  // LIGHT: every fill comes down, no exemption. On a near-white page a bright
+  // colour has nothing to read against — a lime at its own tone 90 is a pale
+  // smear there, indistinguishable from the same colour in dark, which is not a
+  // theme at all. Coming down is what makes faircoin a deep green in light and a
+  // bright lime in dark.
+  if (!isDark) return LIGHT_FILL_TONE;
+  // DARK: the budget applies. Most brands come down to where white fits, but a
+  // seed that is already light cannot without ceasing to be itself, so it keeps
+  // its own tone and takes a black label. That is the eleven-and-two pattern.
+  const candidate = Math.max(DARK_FILL_TONE, seedTone - TONE_BUDGET);
   return contrastOf(palette.tone(candidate), true) >= AA
     ? candidate
-    : Math.max(seedTone, isDark ? DARK_SEED_FLOOR : 0);
+    : Math.max(seedTone, DARK_SEED_FLOOR);
 }
 
 /**

package/lib/commonjs/provider/scroll-provider.js

@@ -1,13 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-Object.defineProperty(exports, "ScrollRestorationProvider", {
-  enumerable: true,
-  get: function () {
-    return _index.ScrollRestorationProvider;
-  }
-});
-var _index = require("../scroll/index.js");
-//# sourceMappingURL=scroll-provider.js.map

package/lib/commonjs/provider/scroll-provider.js.map

@@ -1 +0,0 @@
-{"version":3,"names":["_index","require"],"sourceRoot":"../../../src","sources":["provider/scroll-provider.ts"],"mappings":";;;;;;;;;;;AAYA,IAAAA,MAAA,GAAAC,OAAA","ignoreList":[]}

package/lib/commonjs/provider/scroll-provider.web.js

@@ -1,13 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-Object.defineProperty(exports, "ScrollRestorationProvider", {
-  enumerable: true,
-  get: function () {
-    return _indexWeb.ScrollRestorationProvider;
-  }
-});
-var _indexWeb = require("../scroll/index.web.js");
-//# sourceMappingURL=scroll-provider.web.js.map

package/lib/commonjs/provider/scroll-provider.web.js.map

@@ -1 +0,0 @@
-{"version":3,"names":["_indexWeb","require"],"sourceRoot":"../../../src","sources":["provider/scroll-provider.web.ts"],"mappings":";;;;;;;;;;;AACA,IAAAA,SAAA,GAAAC,OAAA","ignoreList":[]}

package/lib/module/provider/scroll-provider.js

@@ -1,16 +0,0 @@
-"use strict";
-
-/**
- * Native/default binding for the scroll-restoration provider used by
- * {@link BloomProvider}.
- *
- * `@oxyhq/bloom/scroll` is web-forked, so its `browser` export condition hands
- * web consumers the real implementation while native gets the no-op. A compiled
- * `lib/module/provider/index.js` cannot benefit from that condition (it imports
- * a relative path, not the package subpath), so the platform choice is made
- * here by FILENAME instead: Metro picks `scroll-provider.web.ts` on web, and
- * every web bundler that resolves `.web.js` picks the compiled sibling. Same
- * mechanism the toast engine uses for `ToastHost.native.tsx`.
- */
-export { ScrollRestorationProvider } from "../scroll/index.js";
-//# sourceMappingURL=scroll-provider.js.map

package/lib/module/provider/scroll-provider.js.map

@@ -1 +0,0 @@
-{"version":3,"names":["ScrollRestorationProvider"],"sourceRoot":"../../../src","sources":["provider/scroll-provider.ts"],"mappings":";;AAAA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA,SAASA,yBAAyB,QAAQ,oBAAW","ignoreList":[]}

package/lib/module/provider/scroll-provider.web.js

@@ -1,5 +0,0 @@
-"use strict";
-
-/** Web binding for {@link BloomProvider}'s scroll-restoration provider — see `./scroll-provider.ts`. */
-export { ScrollRestorationProvider } from "../scroll/index.web.js";
-//# sourceMappingURL=scroll-provider.web.js.map

package/lib/module/provider/scroll-provider.web.js.map

@@ -1 +0,0 @@
-{"version":3,"names":["ScrollRestorationProvider"],"sourceRoot":"../../../src","sources":["provider/scroll-provider.web.ts"],"mappings":";;AAAA;AACA,SAASA,yBAAyB,QAAQ,wBAAqB","ignoreList":[]}

package/lib/typescript/commonjs/provider/scroll-provider.d.ts

@@ -1,14 +0,0 @@
-/**
- * Native/default binding for the scroll-restoration provider used by
- * {@link BloomProvider}.
- *
- * `@oxyhq/bloom/scroll` is web-forked, so its `browser` export condition hands
- * web consumers the real implementation while native gets the no-op. A compiled
- * `lib/module/provider/index.js` cannot benefit from that condition (it imports
- * a relative path, not the package subpath), so the platform choice is made
- * here by FILENAME instead: Metro picks `scroll-provider.web.ts` on web, and
- * every web bundler that resolves `.web.js` picks the compiled sibling. Same
- * mechanism the toast engine uses for `ToastHost.native.tsx`.
- */
-export { ScrollRestorationProvider } from '../scroll';
-//# sourceMappingURL=scroll-provider.d.ts.map

package/lib/typescript/commonjs/provider/scroll-provider.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"scroll-provider.d.ts","sourceRoot":"","sources":["../../../../src/provider/scroll-provider.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,OAAO,EAAE,yBAAyB,EAAE,MAAM,WAAW,CAAC"}

package/lib/typescript/commonjs/provider/scroll-provider.web.d.ts

@@ -1,3 +0,0 @@
-/** Web binding for {@link BloomProvider}'s scroll-restoration provider — see `./scroll-provider.ts`. */
-export { ScrollRestorationProvider } from '../scroll/index.web';
-//# sourceMappingURL=scroll-provider.web.d.ts.map

package/lib/typescript/commonjs/provider/scroll-provider.web.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"scroll-provider.web.d.ts","sourceRoot":"","sources":["../../../../src/provider/scroll-provider.web.ts"],"names":[],"mappings":"AAAA,wGAAwG;AACxG,OAAO,EAAE,yBAAyB,EAAE,MAAM,qBAAqB,CAAC"}

package/lib/typescript/module/provider/scroll-provider.d.ts

@@ -1,14 +0,0 @@
-/**
- * Native/default binding for the scroll-restoration provider used by
- * {@link BloomProvider}.
- *
- * `@oxyhq/bloom/scroll` is web-forked, so its `browser` export condition hands
- * web consumers the real implementation while native gets the no-op. A compiled
- * `lib/module/provider/index.js` cannot benefit from that condition (it imports
- * a relative path, not the package subpath), so the platform choice is made
- * here by FILENAME instead: Metro picks `scroll-provider.web.ts` on web, and
- * every web bundler that resolves `.web.js` picks the compiled sibling. Same
- * mechanism the toast engine uses for `ToastHost.native.tsx`.
- */
-export { ScrollRestorationProvider } from '../scroll';
-//# sourceMappingURL=scroll-provider.d.ts.map

package/lib/typescript/module/provider/scroll-provider.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"scroll-provider.d.ts","sourceRoot":"","sources":["../../../../src/provider/scroll-provider.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,OAAO,EAAE,yBAAyB,EAAE,MAAM,WAAW,CAAC"}

package/lib/typescript/module/provider/scroll-provider.web.d.ts

@@ -1,3 +0,0 @@
-/** Web binding for {@link BloomProvider}'s scroll-restoration provider — see `./scroll-provider.ts`. */
-export { ScrollRestorationProvider } from '../scroll/index.web';
-//# sourceMappingURL=scroll-provider.web.d.ts.map

package/lib/typescript/module/provider/scroll-provider.web.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"scroll-provider.web.d.ts","sourceRoot":"","sources":["../../../../src/provider/scroll-provider.web.ts"],"names":[],"mappings":"AAAA,wGAAwG;AACxG,OAAO,EAAE,yBAAyB,EAAE,MAAM,qBAAqB,CAAC"}

package/src/__tests__/scroll-native.test.ts

@@ -1,25 +0,0 @@
-import {
-  ScrollRestorationProvider,
-  useScrollRestoration,
-} from '../scroll/index';
-
-// The native barrel is a deliberate no-op: native-stack already preserves
-// scroll. These tests pin that contract so a future refactor can't silently
-// turn the native path into something that touches the DOM or throws.
-
-describe('native scroll-restoration barrel', () => {
-  it('ScrollRestorationProvider renders its children unchanged', () => {
-    const child = { sentinel: true } as unknown as React.ReactElement;
-    expect(ScrollRestorationProvider({ children: child })).toBe(child);
-  });
-
-  it('useScrollRestoration is a no-op for any target/options', () => {
-    const ref = { current: null };
-    expect(() => useScrollRestoration(ref)).not.toThrow();
-    expect(() => useScrollRestoration('window')).not.toThrow();
-    expect(() =>
-      useScrollRestoration(ref, { key: 'feed', enabled: true }),
-    ).not.toThrow();
-    expect(useScrollRestoration(ref)).toBeUndefined();
-  });
-});

package/src/provider/scroll-provider.ts

@@ -1,13 +0,0 @@
-/**
- * Native/default binding for the scroll-restoration provider used by
- * {@link BloomProvider}.
- *
- * `@oxyhq/bloom/scroll` is web-forked, so its `browser` export condition hands
- * web consumers the real implementation while native gets the no-op. A compiled
- * `lib/module/provider/index.js` cannot benefit from that condition (it imports
- * a relative path, not the package subpath), so the platform choice is made
- * here by FILENAME instead: Metro picks `scroll-provider.web.ts` on web, and
- * every web bundler that resolves `.web.js` picks the compiled sibling. Same
- * mechanism the toast engine uses for `ToastHost.native.tsx`.
- */
-export { ScrollRestorationProvider } from '../scroll';

package/src/provider/scroll-provider.web.ts

@@ -1,2 +0,0 @@
-/** Web binding for {@link BloomProvider}'s scroll-restoration provider — see `./scroll-provider.ts`. */
-export { ScrollRestorationProvider } from '../scroll/index.web';