@symbiote-native/navigation 2.0.0 → 2.0.1

package/build/core/tab-options.js

@@ -1,10 +0,0 @@
-// Per-tab agnostic options. Mirrors @react-navigation/bottom-tabs' `options` surface (title,
-// tabBarLabel, tabBarIcon, tabBarBadge, tint colors, tabBarStyle) minus anything that requires a
-// framework element: `tabBarIcon` there is a render prop returning a platform icon element, but
-// per <prop_types_split_agnostic_vs_per_adapter> a render-callback-returning-a-framework-element
-// field can't live in the shared agnostic type, so here it is EITHER a pre-built `IDescriptor`
-// (an adapter can bridge any host node it already resolved, image or vector icon) or a bare icon
-// NAME string the renderer paints as a label-style glyph - both framework-agnostic. An adapter
-// wanting a `(props) => ReactNode`-style callback resolves it to one of these two forms itself,
-// same split as IPressableProps's per-adapter children.
-export {};

package/build/core/tab-router-state/index.d.ts

@@ -1,19 +0,0 @@
-import type { IRoute } from '../navigator-state';
-export type { IRoute } from '../navigator-state';
-type IRouteEntry = IRoute<unknown>;
-export type ITabRouterState = Readonly<{
-    routes: readonly IRouteEntry[];
-    index: number;
-}>;
-export type ITabRouterAction = {
-    type: 'jumpTo';
-    name: string;
-    params?: unknown;
-} | {
-    type: 'setParams';
-    key: string;
-    params: unknown;
-};
-export declare function createInitialTabState(routes: readonly IRouteEntry[], initialRouteName?: string): ITabRouterState;
-export declare function tabRouterReducer(state: ITabRouterState, action: ITabRouterAction): ITabRouterState;
-export declare function isFocusedRoute(index: number, focusedIndex: number): boolean;

package/build/core/tab-router-state/index.js

@@ -1,51 +0,0 @@
-// TabRouter: the logic half (framework-agnostic, zero render). A pure reducer over a FOCUSED
-// INDEX into a fixed route list - jumpTo/setParams - mirroring what @react-navigation/routers'
-// TabRouter keeps, minus the React-specific action-creator/linking machinery. The key structural
-// difference from navigator-state's Stack: tabs never push/pop a route, they move a focused
-// index between a fixed set (mirrors TabRouter.getInitialState / getStateForAction for
-// JUMP_TO - see the tab-actions docs: jumpTo takes a route NAME, not a stack push). Route
-// identity (`key`) is generated by the CALLER, same convention as navigator-state.ts - reused
-// verbatim from there so Stack and Tabs share one route shape.
-import { mergeParams } from '../guards.js';
-const INITIAL_FOCUSED_INDEX = 0;
-export function createInitialTabState(routes, initialRouteName) {
-    if (initialRouteName === undefined)
-        return { routes, index: INITIAL_FOCUSED_INDEX };
-    const index = routes.findIndex(route => route.name === initialRouteName);
-    return { routes, index: index === -1 ? INITIAL_FOCUSED_INDEX : index };
-}
-// jumpTo moves the focused index to an existing route by name and optionally merges params
-// (navigation.jumpTo(name, params) - the tab-actions doc's own signature); it never adds,
-// removes, or reorders routes (mirrors TabRouter: JUMP_TO is a no-op when the target name isn't
-// registered, same as navigatorReducer's popTo bailing on an unknown key). setParams merges into
-// the target route's params by key (CommonActions.setParams semantics - a merge, not a replace).
-export function tabRouterReducer(state, action) {
-    switch (action.type) {
-        case 'jumpTo': {
-            const index = state.routes.findIndex(route => route.name === action.name);
-            if (index === -1)
-                return state;
-            if (action.params === undefined) {
-                return index === state.index ? state : { ...state, index };
-            }
-            const target = state.routes[index];
-            const routes = state.routes.slice();
-            routes[index] = { ...target, params: mergeParams(target.params, action.params) };
-            return { ...state, index, routes };
-        }
-        case 'setParams': {
-            const index = state.routes.findIndex(route => route.key === action.key);
-            if (index === -1)
-                return state;
-            const target = state.routes[index];
-            const routes = state.routes.slice();
-            routes[index] = { ...target, params: mergeParams(target.params, action.params) };
-            return { ...state, routes };
-        }
-        default:
-            return state;
-    }
-}
-export function isFocusedRoute(index, focusedIndex) {
-    return index === focusedIndex;
-}

package/build/react/collect-registry.d.ts

@@ -1,4 +0,0 @@
-import { type ReactElement, type ReactNode } from 'react';
-export declare function collectRegistry<TProps extends {
-    name: string;
-}>(children: ReactNode, isMarkerElement: (child: ReactNode) => child is ReactElement<TProps>): Map<string, Omit<TProps, 'name'>>;

package/build/react/collect-registry.js

@@ -1,15 +0,0 @@
-// Shared by stack.ts/tabs.ts/drawer.ts: each navigator registers its own Screen marker
-// component's props into a name -> entry map via React.Children, differing only in the marker
-// component (isMarkerElement) and the props shape (TProps). Stays in react/ rather than core/:
-// Children/isValidElement are React-only APIs (see CLAUDE.md <adapter_src_follows_framework_idioms>).
-import { Children } from 'react';
-export function collectRegistry(children, isMarkerElement) {
-    const registry = new Map();
-    Children.forEach(children, child => {
-        if (!isMarkerElement(child))
-            return;
-        const { name, ...entry } = child.props;
-        registry.set(name, entry);
-    });
-    return registry;
-}

package/build/react/drawer/index.d.ts

@@ -1,29 +0,0 @@
-import type { ReactNode } from 'react';
-import { type IStyleProp, type IViewStyle } from '@symbiote-native/engine';
-import type { IDrawerDescriptorMap, IDrawerNavigatorHandle, IDrawerOptions, IDrawerRouterState, IDrawerScreenOptions } from '../../core';
-import { DrawerScreen } from '../drawer-screen';
-export type { IDrawerNavigatorHandle, IDrawerDescriptorMap } from '../../core';
-export type IDrawerProps = IDrawerOptions & {
-    initialRouteName?: string;
-    screenOptions?: IDrawerScreenOptions;
-    drawerStyle?: IStyleProp<IViewStyle>;
-    renderDrawerContent?: (props: {
-        state: IDrawerRouterState;
-        descriptors: IDrawerDescriptorMap;
-        navigation: IDrawerNavigatorHandle;
-    }) => ReactNode;
-    children?: ReactNode;
-};
-export declare const Drawer: import("react").ForwardRefExoticComponent<IDrawerOptions & {
-    initialRouteName?: string;
-    screenOptions?: IDrawerScreenOptions;
-    drawerStyle?: IStyleProp<IViewStyle>;
-    renderDrawerContent?: (props: {
-        state: IDrawerRouterState;
-        descriptors: IDrawerDescriptorMap;
-        navigation: IDrawerNavigatorHandle;
-    }) => ReactNode;
-    children?: ReactNode;
-} & import("react").RefAttributes<IDrawerNavigatorHandle>> & {
-    Screen: typeof DrawerScreen;
-};

package/build/react/drawer/index.js

@@ -1,277 +0,0 @@
-// Drawer, the React lifecycle half. The open/closed + focused-route router (drawer-router-state)
-// and the pure swipe/geometry math (drawer-options) live in @symbiote-native/navigation core,
-// shared verbatim with the Vue/Angular adapters; here React supplies the lifecycle - useReducer
-// for the router, a PanResponder for the swipe gesture (RN's own idiom: build it ONCE via
-// useRef, let its callbacks read current values off refs rather than rebuilding it every render),
-// an Animated.Value driving the slide/opacity transforms, and useImperativeHandle for the
-// open/close/toggle/jumpTo handle - mirroring react/tabs.ts's shape (Tab is the closer sibling:
-// both are fixed-route-list, no-react-native-screens navigators; Stack's push/pop + native-screen
-// bridging don't apply here).
-//
-// FEASIBILITY NOTE (see the drawer skill / PR description for the full writeup): the REAL
-// @react-navigation/drawer is built on react-native-gesture-handler + react-native-reanimated,
-// neither of which this codebase depends on. What's built here reaches the same swipe-to-open/
-// close + front/back/slide/permanent behavior using only PanResponder + Animated (both already in
-// @symbiote-native/engine), which is sufficient for a solid drawer but NOT byte-for-byte parity -
-// see the explicit gap list at the bottom of this file.
-import { createElement, forwardRef, isValidElement, useCallback, useContext, useEffect, useId, useImperativeHandle, useMemo, useReducer, useRef, } from 'react';
-import { Animated, PanResponder, useWindowDimensions } from '@symbiote-native/react';
-import { dlog } from '@symbiote-native/engine';
-import { DRAWER_DEFAULT_OVERLAY_COLOR, NAVIGATION_EVENT_BLUR, NAVIGATION_EVENT_FOCUS, createInitialDrawerRouterState, createNavigationEmitter, drawerChildOrder, drawerRouterReducer, isDrawerAnimated, renderDrawer, resolveDragProgress, resolveDrawerGeometry, resolveDrawerSlotInterpolation, resolveSwipeIntent, shouldClaimDrawerSwipe, } from '../../core/index.js';
-import { collectRegistry } from '../collect-registry.js';
-import { NavigationContext } from '../navigation-context.js';
-import { DrawerScreen } from '../drawer-screen.js';
-function isDrawerScreenElement(child) {
-    return isValidElement(child) && child.type === DrawerScreen;
-}
-function resolveDrawerScreenOptions(entry, optionsArgs, screenOptions) {
-    const own = typeof entry.options === 'function' ? entry.options(optionsArgs) : entry.options;
-    return { ...screenOptions, ...own };
-}
-const DRAWER_SNAP_DURATION = 250;
-const DrawerImpl = forwardRef((props, forwardedRef) => {
-    // Read BEFORE establishing this Drawer's own Context value below - becomes the `parent` link a
-    // nested screen's useNavigation().getParent() walks (e.g. this Drawer rendered as a Stack
-    // screen's content reaches that Stack via this value). undefined when this Drawer is the
-    // nesting root.
-    const ambientContext = useContext(NavigationContext);
-    const { initialRouteName, screenOptions, renderDrawerContent, children, drawerStyle, drawerType, drawerPosition, drawerWidth, overlayColor, swipeEnabled, swipeEdgeWidth, swipeMinDistance, swipeMinVelocity, } = props;
-    const options = {
-        drawerType,
-        drawerPosition,
-        drawerWidth,
-        overlayColor,
-        swipeEnabled,
-        swipeEdgeWidth,
-        swipeMinDistance,
-        swipeMinVelocity,
-    };
-    const registry = useMemo(() => collectRegistry(children, isDrawerScreenElement), [children]);
-    const routeIdPrefix = useId();
-    const routes = useMemo(() => Array.from(registry.entries()).map(([name, entry]) => ({
-        key: `${routeIdPrefix}-${name}`,
-        name,
-        params: entry.initialParams,
-    })), [registry, routeIdPrefix]);
-    const [state, dispatch] = useReducer(drawerRouterReducer, undefined, () => createInitialDrawerRouterState(routes, initialRouteName));
-    if (routes.length === 0)
-        dlog('Drawer: no <Drawer.Screen> children registered');
-    const { width: screenWidth } = useWindowDimensions();
-    // progress: 0 closed -> 1 open, the single Animated.Value every slide/opacity transform below
-    // interpolates from.
-    const progress = useRef(new Animated.Value(state.isOpen ? 1 : 0)).current;
-    // Where a drag STARTS from, in progress units. Always exactly 0 or 1: a gesture only ever
-    // begins at rest, since terminate/release always snap the value back to a resting state before
-    // another grant can fire.
-    const dragStartProgress = useRef(0);
-    // Refs so the PanResponder's callbacks - built ONCE below, RN's own idiom - always read the
-    // CURRENT render's values without forcing a new PanResponder identity on every state/prop
-    // change (recreating panHandlers mid-gesture would drop the in-flight touch).
-    const optionsRef = useRef(options);
-    optionsRef.current = options;
-    const screenWidthRef = useRef(screenWidth);
-    screenWidthRef.current = screenWidth;
-    const isOpenRef = useRef(state.isOpen);
-    isOpenRef.current = state.isOpen;
-    const animateProgressTo = useCallback((open) => {
-        // Investigation instrumentation (Drawer openDrawer-no-op / toggleDrawer-no-animation bug):
-        // every imperative caller (openDrawer/closeDrawer/toggleDrawer/jumpTo) funnels through here,
-        // so this single seam proves whether Animated.timing is actually being started at all, and
-        // with what toValue - a live-only failure (e.g. a stale progress ref, or Animated.timing
-        // silently short-circuiting) would show up as this log firing with no visible motion. Kept
-        // behind DEBUG per <keep_logs_gate_behind_DEBUG>, never removed.
-        dlog(`Drawer: animateProgressTo(open=${open}) starting at t=${Date.now()}`);
-        Animated.timing(progress, {
-            toValue: open ? 1 : 0,
-            duration: DRAWER_SNAP_DURATION,
-            // Native-driver wiring (the AnimatedComponent passthrough opt-in ADR 0017 defines) is
-            // deferred for v1 - see this file's header feasibility note. The JS timing loop still
-            // drives every frame, same as any other non-native-driven Animated.timing in this codebase.
-            useNativeDriver: false,
-        }).start();
-    }, [progress]);
-    const handle = useMemo(() => ({
-        openDrawer: () => {
-            dlog(`Drawer: openDrawer() called, isOpen=${isOpenRef.current} at t=${Date.now()}`);
-            animateProgressTo(true);
-            dispatch({ type: 'openDrawer' });
-        },
-        closeDrawer: () => {
-            dlog(`Drawer: closeDrawer() called, isOpen=${isOpenRef.current} at t=${Date.now()}`);
-            animateProgressTo(false);
-            dispatch({ type: 'closeDrawer' });
-        },
-        toggleDrawer: () => {
-            dlog(`Drawer: toggleDrawer() called, isOpen=${isOpenRef.current} at t=${Date.now()}`);
-            animateProgressTo(!isOpenRef.current);
-            dispatch({ type: 'toggleDrawer' });
-        },
-        jumpTo: (name) => {
-            dispatch({ type: 'jumpTo', name });
-            if (isOpenRef.current)
-                animateProgressTo(false);
-        },
-    }), [animateProgressTo]);
-    useImperativeHandle(forwardedRef, () => handle, [handle]);
-    const panResponder = useRef(PanResponder.create({
-        onStartShouldSetPanResponder: (event, gestureState) => shouldClaimDrawerSwipe(event, gestureState, screenWidthRef.current, isOpenRef.current, optionsRef.current, 'start'),
-        onMoveShouldSetPanResponder: (event, gestureState) => shouldClaimDrawerSwipe(event, gestureState, screenWidthRef.current, isOpenRef.current, optionsRef.current, 'move'),
-        onPanResponderGrant: () => {
-            dlog('Drawer: gesture grant');
-            dragStartProgress.current = isOpenRef.current ? 1 : 0;
-        },
-        onPanResponderMove: (_event, gestureState) => {
-            const nextProgress = resolveDragProgress(gestureState, dragStartProgress.current, optionsRef.current);
-            progress.setValue(nextProgress);
-        },
-        onPanResponderRelease: (_event, gestureState) => {
-            const intent = resolveSwipeIntent(gestureState, isOpenRef.current, optionsRef.current);
-            const open = intent === 'open';
-            dlog(`Drawer: gesture release -> ${open ? 'open' : 'close'}`);
-            animateProgressTo(open);
-            dispatch(open ? { type: 'openDrawer' } : { type: 'closeDrawer' });
-        },
-        onPanResponderTerminate: () => {
-            dlog('Drawer: gesture terminated, snapping back');
-            animateProgressTo(isOpenRef.current);
-        },
-    })).current;
-    const animated = isDrawerAnimated(options);
-    const geometry = useMemo(() => resolveDrawerGeometry(options), [options.drawerType, options.drawerPosition, options.drawerWidth]);
-    const panelSlot = animated ? resolveDrawerSlotInterpolation(geometry, 'panel') : undefined;
-    const contentSlot = animated ? resolveDrawerSlotInterpolation(geometry, 'content') : undefined;
-    const overlaySlot = animated ? resolveDrawerSlotInterpolation(geometry, 'overlay') : undefined;
-    const panelTranslateX = panelSlot ? progress.interpolate(panelSlot.translateX) : undefined;
-    const contentTranslateX = contentSlot ? progress.interpolate(contentSlot.translateX) : undefined;
-    const overlayOpacity = overlaySlot ? progress.interpolate(overlaySlot.opacity) : undefined;
-    // The overlay is a full-screen absolutely-positioned sibling BELOW content in paint order
-    // (see render-drawer.ts's drawerChildOrder) - for 'front' that's fine since content never moves,
-    // but for 'slide' content itself translates away by contentTranslateX, and without following it
-    // the overlay stays pinned full-screen, dimming (and touch-capturing) the now-revealed panel
-    // underneath instead of just the content sliver it's meant to dim. Tying overlay to the SAME
-    // translateX as content keeps it registered exactly under content, wherever content actually is
-    // (resolveDrawerSlotInterpolation's 'overlay' overload returns that same content delta).
-    const overlayTranslateX = overlaySlot ? progress.interpolate(overlaySlot.translateX) : undefined;
-    const focusedRoute = state.routes[state.index];
-    const focusedEntry = focusedRoute ? registry.get(focusedRoute.name) : undefined;
-    if (focusedRoute && !focusedEntry) {
-        dlog(`Drawer: no screen registered for route name "${focusedRoute.name}"`);
-    }
-    // Only the focused route's screen is ever mounted (like Tab, unlike Stack which keeps every
-    // pushed route alive), so a fresh emitter per focus change is sufficient - see tabs.ts's
-    // matching comment for why no per-route emitter map is needed. Keyed on the route KEY, not the
-    // route object, so a jumpTo-with-no-params re-focus of the ALREADY-focused route (a no-op in
-    // drawerRouterReducer) and any future params merge don't spuriously re-fire focus/blur.
-    const focusedRouteKey = focusedRoute?.key;
-    const routeEmitter = useMemo(() => createNavigationEmitter(), [focusedRouteKey]);
-    // Drawer paints its own panel in pure JS - there is no native onAppear/onDisappear to hook
-    // (unlike Stack's RNSScreen), so focus/blur is synthesized here: mount = focus, cleanup = blur,
-    // exactly what an effect keyed on focusedRouteKey already encodes - no diffFocusedRoute
-    // indirection needed (unlike Vue/Angular, which diff real prev/next keys inside an imperative
-    // watch/CD callback that has no mount/cleanup pairing of its own).
-    useEffect(() => {
-        if (focusedRouteKey === undefined)
-            return undefined;
-        dlog(`Drawer: route "${focusedRoute?.name}" focused`);
-        routeEmitter.emit(NAVIGATION_EVENT_FOCUS);
-        return () => {
-            dlog(`Drawer: route "${focusedRoute?.name}" blurred`);
-            routeEmitter.emit(NAVIGATION_EVENT_BLUR);
-        };
-        // focusedRoute omitted deliberately: only its .key (tracked via focusedRouteKey) should
-        // re-run this effect - see the comment above on focusedRouteKey.
-        // eslint-disable-next-line react-hooks/exhaustive-deps
-    }, [routeEmitter, focusedRouteKey]);
-    const content = focusedEntry && focusedRoute
-        ? createElement(NavigationContext.Provider, {
-            value: {
-                route: focusedRoute,
-                navigation: handle,
-                emitter: routeEmitter,
-                parent: ambientContext,
-            },
-        }, createElement(focusedEntry.component))
-        : null;
-    const descriptors = {};
-    for (const route of state.routes) {
-        const entry = registry.get(route.name);
-        if (entry === undefined)
-            continue;
-        descriptors[route.key] = {
-            options: resolveDrawerScreenOptions(entry, { route, navigation: handle }, screenOptions),
-            navigation: handle,
-        };
-    }
-    const drawerContent = renderDrawerContent?.({ state, descriptors, navigation: handle }) ?? null;
-    const root = renderDrawer({
-        overlayColor: overlayColor ?? DRAWER_DEFAULT_OVERLAY_COLOR,
-        drawerStyle,
-        contentPassthrough: {},
-        overlayPassthrough: animated
-            ? {
-                pointerEvents: state.isOpen ? 'auto' : 'none',
-                onStartShouldSetResponder: () => true,
-                onResponderRelease: () => {
-                    animateProgressTo(false);
-                    dispatch({ type: 'closeDrawer' });
-                },
-            }
-            : {},
-        panelPassthrough: {},
-    }, options);
-    const order = drawerChildOrder(options);
-    const slots = new Map();
-    order.forEach((slot, index) => {
-        const descriptor = root.children[index];
-        if (typeof descriptor !== 'string')
-            slots.set(slot, descriptor);
-    });
-    const slotChildren = {
-        content,
-        overlay: null,
-        panel: drawerContent,
-    };
-    // Each animated style holds an AnimatedInterpolation node, not a plain number/color - it feeds
-    // only Animated.View's deliberately permissive `style?: unknown` (see create-animated-component.tsx),
-    // never the plain-IViewStyle branch below, so this stays untyped rather than widening IViewStyle.
-    const slotAnimatedStyle = {
-        content: contentTranslateX === undefined
-            ? undefined
-            : { transform: [{ translateX: contentTranslateX }] },
-        overlay: overlayOpacity === undefined
-            ? undefined
-            : { opacity: overlayOpacity, transform: [{ translateX: overlayTranslateX }] },
-        panel: panelTranslateX === undefined ? undefined : { transform: [{ translateX: panelTranslateX }] },
-    };
-    function renderSlot(slot) {
-        const descriptor = slots.get(slot);
-        if (descriptor === undefined)
-            return null;
-        const animatedStyle = slotAnimatedStyle[slot];
-        if (animatedStyle === undefined) {
-            return createElement(descriptor.type, { key: descriptor.key, ...descriptor.props }, slotChildren[slot]);
-        }
-        const style = [descriptor.props.style, animatedStyle];
-        return createElement(Animated.View, { key: descriptor.key, ...descriptor.props, style }, slotChildren[slot]);
-    }
-    const drawerChildren = order
-        .map(renderSlot)
-        .filter((element) => element !== null);
-    return createElement('symbiote-view', { style: root.props.style, ...panResponder.panHandlers }, ...drawerChildren);
-});
-export const Drawer = Object.assign(DrawerImpl, { Screen: DrawerScreen });
-// --- Explicit gap list vs the real react-native-gesture-handler + react-native-reanimated
-// @react-navigation/drawer (confirmed against its current docs) ---
-// 1. `configureGestureHandler` - a raw react-native-gesture-handler `Gesture` object escape
-//    hatch. No PanResponder equivalent exists; not ported.
-// 2. Simultaneous/failure gesture RELATIONSHIPS (gesture-handler's declarative composition vs a
-//    nested ScrollView, another PanResponder, etc.) - PanResponder only offers negotiation via the
-//    should-set boolean gates used here (edge-start + dominant-axis), which is more prone to an
-//    accidental hijack of a nested horizontal ScrollView/Swiper than gesture-handler's system.
-// 3. `useDrawerProgress` - a Reanimated SharedValue read on the UI thread. `progress` here is a
-//    JS-thread AnimatedValue; interpolating it for consumer-facing content animation works, but
-//    without native-driver wiring (gap noted above) it does not carry the same synchronous
-//    UI-thread guarantee under JS-thread load.
-// 4. `hideStatusBarOnOpen` / `keyboardDismissMode` / `statusBarAnimation` / `overlayStyle` - not
-//    wired in this pass; straightforward additions once StatusBar/Keyboard module wiring is
-//    needed here (not a PanResponder/Animated limitation, just unscoped for v1).

package/build/react/drawer-screen.d.ts

@@ -1,14 +0,0 @@
-import type { FC, ReactElement } from 'react';
-import type { IDrawerNavigatorHandle, IDrawerScreenOptions, IRoute } from '../core';
-export type IDrawerScreenOptionsArgs = {
-    route: IRoute<unknown>;
-    navigation: IDrawerNavigatorHandle;
-};
-export type IDrawerScreenOptionsResolver = (args: IDrawerScreenOptionsArgs) => IDrawerScreenOptions;
-export type IDrawerScreenProps = {
-    name: string;
-    component: FC;
-    options?: IDrawerScreenOptions | IDrawerScreenOptionsResolver;
-    initialParams?: unknown;
-};
-export declare function DrawerScreen(_props: IDrawerScreenProps): ReactElement | null;

package/build/react/drawer-screen.js

@@ -1,8 +0,0 @@
-// Drawer.Screen: a declarative marker, never rendered on its own - Drawer reads its props via
-// React.Children to build the static name -> {component, options} registry, then mounts the
-// FOCUSED route's component. Mirrors react/tab-screen.ts (Tab's twin - the closer sibling, both
-// are fixed-route-list/no-push navigators) and react/screen.ts (Stack's twin); see CLAUDE.md
-// <third_party_rn_packages_are_react_only> - this and Drawer import nothing from react-native.
-export function DrawerScreen(_props) {
-    return null;
-}

package/build/react/hooks/index.d.ts

@@ -1,12 +0,0 @@
-export { useNavigation } from './use-navigation';
-export type { INavigationHandle } from './use-navigation';
-export { useStackNavigation } from './use-stack-navigation';
-export type { IStackNavigationHandle } from './use-stack-navigation';
-export { useTabNavigation } from './use-tab-navigation';
-export type { ITabNavigationHandle } from './use-tab-navigation';
-export { useDrawerNavigation } from './use-drawer-navigation';
-export type { IDrawerNavigationHandle } from './use-drawer-navigation';
-export { useRoute } from './use-route';
-export { useIsFocused } from './use-is-focused';
-export { useFocusEffect } from './use-focus-effect';
-export { useNavigationState } from './use-navigation-state';

package/build/react/hooks/index.js

@@ -1,8 +0,0 @@
-export { useNavigation } from './use-navigation.js';
-export { useStackNavigation } from './use-stack-navigation.js';
-export { useTabNavigation } from './use-tab-navigation.js';
-export { useDrawerNavigation } from './use-drawer-navigation.js';
-export { useRoute } from './use-route.js';
-export { useIsFocused } from './use-is-focused.js';
-export { useFocusEffect } from './use-focus-effect.js';
-export { useNavigationState } from './use-navigation-state/index.js';

package/build/react/hooks/use-drawer-navigation.d.ts

@@ -1,4 +0,0 @@
-import type { IDrawerNavigatorHandle } from '../../core';
-import type { INavigationHandle } from './use-navigation';
-export type IDrawerNavigationHandle = IDrawerNavigatorHandle & Pick<INavigationHandle, 'addListener' | 'getParent'>;
-export declare function useDrawerNavigation(): IDrawerNavigationHandle;

package/build/react/hooks/use-drawer-navigation.js

@@ -1,12 +0,0 @@
-// Twin of use-stack-navigation.ts, narrowing to a Drawer handle instead. See that file's header
-// for why this exists: it hides the union-narrowing guard inside the library instead of every call site.
-import { isDrawerNavigatorHandle } from '../../core/index.js';
-import { useNavigation } from './use-navigation.js';
-export function useDrawerNavigation() {
-    const navigation = useNavigation();
-    if (!isDrawerNavigatorHandle(navigation)) {
-        throw new Error('useDrawerNavigation() was called from a component whose nearest navigator is not a Drawer. ' +
-            'Use useNavigation() instead if this component can render under more than one navigator kind.');
-    }
-    return navigation;
-}

package/build/react/hooks/use-focus-effect.d.ts

@@ -1,2 +0,0 @@
-import type { EffectCallback } from 'react';
-export declare function useFocusEffect(effect: EffectCallback): void;

package/build/react/hooks/use-focus-effect.js

@@ -1,29 +0,0 @@
-// Thin useEffect wrapper: runs `effect` while the route is focused and runs its own returned
-// cleanup on blur - exactly React.useEffect's contract, just re-armed on every focus/blur pair
-// instead of once on mount - mirrors @react-navigation's useFocusEffect. Callers should memoize
-// `effect` (React.useCallback), same requirement the upstream hook documents, since a new
-// `effect` identity re-subscribes here like any other useEffect dependency change.
-import { useEffect } from 'react';
-import { NAVIGATION_EVENT_BLUR, NAVIGATION_EVENT_FOCUS } from '../../core/index.js';
-import { useRequiredNavigationContext } from '../navigation-context.js';
-export function useFocusEffect(effect) {
-    const context = useRequiredNavigationContext('useFocusEffect');
-    const { emitter } = context;
-    useEffect(() => {
-        let cleanup;
-        const runEffect = () => {
-            cleanup = effect();
-        };
-        const runCleanup = () => {
-            cleanup?.();
-            cleanup = undefined;
-        };
-        const unsubscribeFocus = emitter.addListener(NAVIGATION_EVENT_FOCUS, runEffect);
-        const unsubscribeBlur = emitter.addListener(NAVIGATION_EVENT_BLUR, runCleanup);
-        return () => {
-            unsubscribeFocus();
-            unsubscribeBlur();
-            runCleanup();
-        };
-    }, [emitter, effect]);
-}

package/build/react/hooks/use-is-focused.d.ts

@@ -1 +0,0 @@
-export declare function useIsFocused(): boolean;

package/build/react/hooks/use-is-focused.js

@@ -1,22 +0,0 @@
-// Thin useEffect wrapper: subscribes to the route's focus/blur pair and returns whether it's
-// currently focused, re-rendering on change - mirrors @react-navigation's useIsFocused. Starts
-// `false` rather than guessing from stack position: the route's emitter only fires 'focus' once
-// RNSScreen's native onAppear actually lands (stack.ts), so a screen genuinely isn't focused yet
-// at the instant it mounts - same async gap real native transitions have.
-import { useEffect, useState } from 'react';
-import { NAVIGATION_EVENT_BLUR, NAVIGATION_EVENT_FOCUS } from '../../core/index.js';
-import { useRequiredNavigationContext } from '../navigation-context.js';
-export function useIsFocused() {
-    const context = useRequiredNavigationContext('useIsFocused');
-    const { emitter } = context;
-    const [isFocused, setIsFocused] = useState(false);
-    useEffect(() => {
-        const unsubscribeFocus = emitter.addListener(NAVIGATION_EVENT_FOCUS, () => setIsFocused(true));
-        const unsubscribeBlur = emitter.addListener(NAVIGATION_EVENT_BLUR, () => setIsFocused(false));
-        return () => {
-            unsubscribeFocus();
-            unsubscribeBlur();
-        };
-    }, [emitter]);
-    return isFocused;
-}

package/build/react/hooks/use-navigation-state/index.d.ts

@@ -1,2 +0,0 @@
-import type { INavigatorState } from '../../../core';
-export declare function useNavigationState<TResult>(selector: (state: INavigatorState) => TResult): TResult;

package/build/react/hooks/use-navigation-state/index.js

@@ -1,39 +0,0 @@
-// Thin selector wrapper: subscribes to the router's `state` broadcast (stack.ts's render loop
-// re-emits the full INavigatorState to every route's emitter after each commit) and returns
-// `selector(state)`, re-rendering only when the emitted state changes - mirrors
-// @react-navigation's useNavigationState. The reducer/dispatch machinery it selects over lives in
-// core/navigator-state.ts; this hook only wires the subscription + local re-render.
-//
-// Seeded from a single-route snapshot ({ routes: [route] }) rather than left undefined: the real
-// broadcast lands a tick later (post-commit useEffect), so a selector reading e.g.
-// `state.routes.at(-1)?.name` still resolves correctly on first paint for the common single-route
-// case, closing the same async gap useIsFocused documents.
-//
-// Live updates currently only arrive under <Stack> - it's the only navigator that emits
-// NAVIGATION_EVENT_STATE (its post-commit useEffect in stack.ts); <Tab>/<Drawer> don't broadcast
-// it, so under those this hook silently stays on its initial snapshot.
-import { useEffect, useRef, useState } from 'react';
-import { NAVIGATION_EVENT_STATE, isRecord } from '../../../core/index.js';
-import { useRequiredNavigationContext } from '../../navigation-context.js';
-export function useNavigationState(selector) {
-    const context = useRequiredNavigationContext('useNavigationState');
-    const { route, emitter } = context;
-    const [result, setResult] = useState(() => selector({ routes: [route] }));
-    // selector is typically an inline arrow at the call site (`useNavigationState(s => ...)`), a
-    // fresh identity every render - read through a ref so the effect below doesn't need `selector`
-    // in its deps, and doesn't unsubscribe/resubscribe on every render because of it (the same trap
-    // useFocusEffect's own comment documents for its `effect` argument).
-    const selectorRef = useRef(selector);
-    selectorRef.current = selector;
-    useEffect(() => {
-        return emitter.addListener(NAVIGATION_EVENT_STATE, (state) => {
-            if (!isNavigatorState(state))
-                return;
-            setResult(selectorRef.current(state));
-        });
-    }, [emitter]);
-    return result;
-}
-function isNavigatorState(value) {
-    return isRecord(value) && Array.isArray(value.routes);
-}

package/build/react/hooks/use-navigation.d.ts

@@ -1,7 +0,0 @@
-import type { INavigationEventListener, INavigationEventName } from '../../core';
-import type { IAnyNavigatorHandle } from '../navigation-context';
-export type INavigationHandle = IAnyNavigatorHandle & {
-    addListener: (event: INavigationEventName, listener: INavigationEventListener) => () => void;
-    getParent: () => IAnyNavigatorHandle | undefined;
-};
-export declare function useNavigation(): INavigationHandle;

package/build/react/hooks/use-navigation.js

@@ -1,16 +0,0 @@
-// Thin lifecycle wrapper: returns the current screen's navigator handle (push/pop/replace/... for a
-// Stack screen, jumpTo/setParams for a Tab screen, openDrawer/... for a Drawer screen) plus
-// addListener bound to that route's own emitter - mirrors @react-navigation's
-// `navigation.addListener('focus', cb)` surface. All pub/sub logic lives in
-// ../../core/navigation-events; this hook only reads NavigationContext and binds identity.
-import { useMemo } from 'react';
-import { useRequiredNavigationContext } from '../navigation-context.js';
-export function useNavigation() {
-    const context = useRequiredNavigationContext('useNavigation');
-    const { navigation, emitter, parent } = context;
-    return useMemo(() => ({
-        ...navigation,
-        addListener: emitter.addListener,
-        getParent: () => parent?.navigation,
-    }), [navigation, emitter, parent]);
-}

package/build/react/hooks/use-route.d.ts

@@ -1,2 +0,0 @@
-import type { IRoute } from '../../core';
-export declare function useRoute(): IRoute<unknown>;

package/build/react/hooks/use-route.js

@@ -1,8 +0,0 @@
-// Thin lifecycle wrapper: returns the current screen's IRoute from NavigationContext - mirrors
-// @react-navigation's useRoute. Zero logic of its own; the route object itself is built by
-// stack.ts's render loop from the core reducer's state.
-import { useRequiredNavigationContext } from '../navigation-context.js';
-export function useRoute() {
-    const context = useRequiredNavigationContext('useRoute');
-    return context.route;
-}

package/build/react/hooks/use-stack-navigation.d.ts

@@ -1,4 +0,0 @@
-import type { INavigatorHandle } from '../../core';
-import type { INavigationHandle } from './use-navigation';
-export type IStackNavigationHandle = INavigatorHandle & Pick<INavigationHandle, 'addListener' | 'getParent'>;
-export declare function useStackNavigation(): IStackNavigationHandle;