@symbiote-native/navigation 2.0.0 → 2.0.1

package/build/register.js

@@ -1,58 +0,0 @@
-// Side-effect: register RNSScreen/RNSScreenStack/RNSScreenStackHeaderConfig/
-// RNSScreenStackHeaderSubview/RNSSearchBar/RNSScreenContentWrapper's ViewConfigs in RN's
-// ReactNativeViewConfigRegistry. Evaluating each codegen native-component spec
-// (codegenNativeComponent('RNSScreen', ...) etc.) registers the getter the engine reads via
-// setNativeViewConfigSource, so events + color processors derive on first commit. We import the
-// codegen SPECS, never react-native-screens' React components (ScreenStack.tsx et al - hooks,
-// crashes a non-React adapter) - these modules have no hooks, so they are framework-agnostic and
-// shared by every adapter entry. Each adapter barrel imports this; the component modules and
-// their headless tests stay free of it. See CLAUDE.md <third_party_rn_packages_are_react_only>.
-//
-// RNSSearchBar (headerSearchBarOptions' native leaf, nested by render-stack.ts's
-// renderHeaderConfig) was missing from this list - its ViewConfig was never registered, so Fabric
-// had no component descriptor for 'RNSSearchBar' and crashed on mount the moment a screen set
-// headerSearchBarOptions. That is the root cause of the search-bar crash, not a deeper
-// Fabric-interop gap.
-//
-// RNSScreenStackHeaderSubview (the wrapper renderHeaderConfig nests the search bar leaf inside,
-// per RNSScreenStackHeaderConfig.mm's mountChildComponentView requiring every header child to be
-// one) needs the same registration, or the same class of mount crash follows.
-//
-// RNSScreenContentWrapper (the RNS_SCREEN_CONTENT_WRAPPER_VIEW_NAME wrapper stack.ts wraps every
-// screen's content in - see its comment in core/constants.ts) additionally needs a NATIVE-side
-// registration: this file alone is not enough. The native iOS registry
-// (RCTThirdPartyComponentsProvider.mm, generated by codegen from THIS package's own
-// package.json#codegenConfig.ios.componentProvider map, NOT from react-native-screens') has no
-// entry for 'RNSScreenContentWrapper' by default, so without it Fabric falls back to its
-// "Unimplemented component" placeholder view regardless of this file's import. Both registries
-// are independently required for a never-before-used react-native-screens view: this file (JS
-// ViewConfig, read by @symbiote-native/engine's registry.ts) and package.json's componentProvider
-// map (native ComponentDescriptor, read by codegen at `pod install` time).
-//
-// RNSModalScreen's gap on both registries isn't a mount crash but a silent mispositioning bug.
-// react-native-screens' own Screen.tsx picks
-// ModalScreenNativeComponent ('RNSModalScreen') instead of ScreenNativeComponent ('RNSScreen')
-// whenever stackPresentation isn't push/containedModal/containedTransparentModal, because
-// RNSScreen.mm's updateLayoutMetrics: checks `[self isKindOfClass:RNSModalScreen.class]` and, for
-// that class, DELIBERATELY skips applying Yoga's computed frame (its own comment: "the available
-// space is most likely restricted & differs from what Yoga resolves during first layout - we want
-// to rely on native layout here"). Emitting a plain 'RNSScreen' for a formSheet/modal presentation
-// (as resolveScreenViewName below used to do unconditionally) means that check never matches, so
-// Yoga's frame - computed as if the screen were still a normal flexed sibling in its outer
-// RNSScreenStack's push-oriented column layout - gets applied verbatim and never corrected,
-// visually shifting the whole modal down by one full screen's height. Fixed in
-// core/render-stack.ts's resolveScreenViewName, which now mirrors Screen.tsx's own
-// shouldUseModalScreenComponent condition exactly.
-//
-// Unlike @symbiote-native/slider (which deep-imports @react-native-community/slider's compiled
-// `dist/`), react-native-screens declares `"react-native": "src/index"` in its package.json -
-// Metro's resolverMainFields prioritizes that field, so it resolves the library straight to raw
-// TypeScript source and transforms it like first-party code. The deep import below targets that
-// same `src/fabric/` tree rather than a compiled output.
-import 'react-native-screens/src/fabric/ScreenNativeComponent';
-import 'react-native-screens/src/fabric/ModalScreenNativeComponent';
-import 'react-native-screens/src/fabric/ScreenStackNativeComponent';
-import 'react-native-screens/src/fabric/ScreenStackHeaderConfigNativeComponent';
-import 'react-native-screens/src/fabric/ScreenStackHeaderSubviewNativeComponent';
-import 'react-native-screens/src/fabric/SearchBarNativeComponent';
-import 'react-native-screens/src/fabric/ScreenContentWrapperNativeComponent';

package/build/vue/composables/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/vue/composables/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.js';

package/build/vue/composables/use-drawer-navigation.d.ts

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

package/build/vue/composables/use-drawer-navigation.js

@@ -1,15 +0,0 @@
-// Twin of use-stack-navigation.ts, narrowing to a Drawer handle instead.
-import { computed } from '@vue/runtime-core';
-import { isDrawerNavigatorHandle } from '../../core/index.js';
-import { useNavigation } from './use-navigation.js';
-export function useDrawerNavigation() {
-    const navigation = useNavigation();
-    return computed(() => {
-        const value = navigation.value;
-        if (!isDrawerNavigatorHandle(value)) {
-            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 value;
-    });
-}

package/build/vue/composables/use-focus-effect.d.ts

@@ -1 +0,0 @@
-export declare function useFocusEffect(effect: () => (() => void) | void): void;

package/build/vue/composables/use-focus-effect.js

@@ -1,31 +0,0 @@
-// Mirrors @react-navigation's useFocusEffect; Vue twin of react/hooks/use-focus-effect.ts.
-// React's version requires memoizing `effect` (useCallback) since a new identity re-subscribes
-// it like any other useEffect dependency. That doesn't apply here: Vue's setup() runs once, so
-// `effect` is read once at composable-call time and closed over directly by onMounted/onUnmounted -
-// there's no dependency array to go stale.
-import { onMounted, onUnmounted } from '@vue/runtime-core';
-import { NAVIGATION_EVENT_BLUR, NAVIGATION_EVENT_FOCUS } from '../../core/index.js';
-import { requireNavigationScope } from '../navigation-context.js';
-export function useFocusEffect(effect) {
-    const scope = requireNavigationScope('useFocusEffect');
-    let cleanup;
-    let unsubscribeFocus;
-    let unsubscribeBlur;
-    const runEffect = () => {
-        cleanup = effect();
-    };
-    const runCleanup = () => {
-        cleanup?.();
-        cleanup = undefined;
-    };
-    onMounted(() => {
-        const { emitter } = scope.value;
-        unsubscribeFocus = emitter.addListener(NAVIGATION_EVENT_FOCUS, runEffect);
-        unsubscribeBlur = emitter.addListener(NAVIGATION_EVENT_BLUR, runCleanup);
-    });
-    onUnmounted(() => {
-        unsubscribeFocus?.();
-        unsubscribeBlur?.();
-        runCleanup();
-    });
-}

package/build/vue/composables/use-is-focused.d.ts

@@ -1,2 +0,0 @@
-import type { Ref } from '@vue/runtime-core';
-export declare function useIsFocused(): Ref<boolean>;

package/build/vue/composables/use-is-focused.js

@@ -1,28 +0,0 @@
-// Mirrors @react-navigation's useIsFocused; Vue twin of react/hooks/use-is-focused.ts.
-// Starts `false` rather than guessing from stack position: the route's emitter only fires 'focus'
-// once RNSScreen's native onAppear lands (stack.ts) or the screen mounts focused (tabs.ts/drawer.ts) -
-// a screen genuinely isn't focused at the instant it mounts, the same async gap real native
-// transitions have.
-import { onMounted, onUnmounted, ref } from '@vue/runtime-core';
-import { NAVIGATION_EVENT_BLUR, NAVIGATION_EVENT_FOCUS } from '../../core/index.js';
-import { requireNavigationScope } from '../navigation-context.js';
-export function useIsFocused() {
-    const scope = requireNavigationScope('useIsFocused');
-    const isFocused = ref(false);
-    let unsubscribeFocus;
-    let unsubscribeBlur;
-    onMounted(() => {
-        const { emitter } = scope.value;
-        unsubscribeFocus = emitter.addListener(NAVIGATION_EVENT_FOCUS, () => {
-            isFocused.value = true;
-        });
-        unsubscribeBlur = emitter.addListener(NAVIGATION_EVENT_BLUR, () => {
-            isFocused.value = false;
-        });
-    });
-    onUnmounted(() => {
-        unsubscribeFocus?.();
-        unsubscribeBlur?.();
-    });
-    return isFocused;
-}

package/build/vue/composables/use-navigation-state.d.ts

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

package/build/vue/composables/use-navigation-state.js

@@ -1,29 +0,0 @@
-// Mirrors @react-navigation's useNavigationState; Vue twin of react/hooks/use-navigation-state.ts.
-// The reducer/dispatch machinery lives in core/navigator-state.ts (tab-router-state.ts /
-// drawer-router-state.ts for the other two navigators) - this composable only wires the
-// subscription to the `state` broadcast each render loop re-emits after commit.
-//
-// Seeded from a single-route snapshot ({ routes: [route] }) rather than left undefined: the real
-// broadcast lands after mount (Stack's render loop; tabs.ts/drawer.ts emit on focus), so a
-// selector reading e.g. `state.routes.at(-1)?.name` still resolves correctly on first paint for
-// the common single-route case - the same async gap useIsFocused documents.
-import { onMounted, onUnmounted, shallowRef } from '@vue/runtime-core';
-import { NAVIGATION_EVENT_STATE, isRecord } from '../../core/index.js';
-import { requireNavigationScope } from '../navigation-context.js';
-function isNavigatorState(value) {
-    return isRecord(value) && Array.isArray(value.routes);
-}
-export function useNavigationState(selector) {
-    const scope = requireNavigationScope('useNavigationState');
-    const result = shallowRef(selector({ routes: [scope.value.route] }));
-    let unsubscribe;
-    onMounted(() => {
-        unsubscribe = scope.value.emitter.addListener(NAVIGATION_EVENT_STATE, (state) => {
-            if (!isNavigatorState(state))
-                return;
-            result.value = selector(state);
-        });
-    });
-    onUnmounted(() => unsubscribe?.());
-    return result;
-}

package/build/vue/composables/use-navigation.d.ts

@@ -1,8 +0,0 @@
-import type { ComputedRef } from '@vue/runtime-core';
-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(): ComputedRef<INavigationHandle>;

package/build/vue/composables/use-navigation.js

@@ -1,13 +0,0 @@
-// Mirrors @react-navigation's `navigation.addListener('focus', cb)` surface; Vue twin of
-// react/hooks/use-navigation.ts (returns a ComputedRef, Vue's reactive-primitive convention,
-// instead of a plain value). All pub/sub logic lives in ../../core/navigation-events - this
-// composable only reads the injected navigation scope and binds identity.
-import { computed } from '@vue/runtime-core';
-import { requireNavigationScope } from '../navigation-context.js';
-export function useNavigation() {
-    const scope = requireNavigationScope('useNavigation');
-    return computed(() => {
-        const { navigation, emitter, parent } = scope.value;
-        return { ...navigation, addListener: emitter.addListener, getParent: () => parent?.navigation };
-    });
-}

package/build/vue/composables/use-route.d.ts

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

package/build/vue/composables/use-route.js

@@ -1,9 +0,0 @@
-// Mirrors @react-navigation's useRoute; Vue twin of react/hooks/use-route.ts (returns a
-// ComputedRef instead of a plain value). Zero logic of its own - the route object itself is built
-// by stack.ts's/tabs.ts's/drawer.ts's render loop from the shared core reducer's state.
-import { computed } from '@vue/runtime-core';
-import { requireNavigationScope } from '../navigation-context.js';
-export function useRoute() {
-    const scope = requireNavigationScope('useRoute');
-    return computed(() => scope.value.route);
-}

package/build/vue/composables/use-stack-navigation.d.ts

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

package/build/vue/composables/use-stack-navigation.js

@@ -1,18 +0,0 @@
-// useNavigation() returns a union (IAnyNavigatorHandle) since it doesn't know which navigator
-// mounted the calling component. When a component genuinely knows it only ever renders under a
-// Stack, this composable narrows that union ONCE, here, so call sites never write their own
-// 'push' in navigation check. Vue twin of react/hooks/use-stack-navigation.ts.
-import { computed } from '@vue/runtime-core';
-import { isStackNavigatorHandle } from '../../core/index.js';
-import { useNavigation } from './use-navigation.js';
-export function useStackNavigation() {
-    const navigation = useNavigation();
-    return computed(() => {
-        const value = navigation.value;
-        if (!isStackNavigatorHandle(value)) {
-            throw new Error('useStackNavigation() was called from a component whose nearest navigator is not a Stack. ' +
-                'Use useNavigation() instead if this component can render under more than one navigator kind.');
-        }
-        return value;
-    });
-}

package/build/vue/composables/use-tab-navigation.d.ts

@@ -1,5 +0,0 @@
-import type { ComputedRef } from '@vue/runtime-core';
-import type { ITabNavigatorHandle } from '../../core';
-import type { INavigationHandle } from './use-navigation';
-export type ITabNavigationHandle = ITabNavigatorHandle & Pick<INavigationHandle, 'addListener' | 'getParent'>;
-export declare function useTabNavigation(): ComputedRef<ITabNavigationHandle>;

package/build/vue/composables/use-tab-navigation.js

@@ -1,15 +0,0 @@
-// Twin of use-stack-navigation.ts, narrowing to a Tab handle instead.
-import { computed } from '@vue/runtime-core';
-import { isTabNavigatorHandle } from '../../core/index.js';
-import { useNavigation } from './use-navigation.js';
-export function useTabNavigation() {
-    const navigation = useNavigation();
-    return computed(() => {
-        const value = navigation.value;
-        if (!isTabNavigatorHandle(value)) {
-            throw new Error('useTabNavigation() was called from a component whose nearest navigator is not a Tab. ' +
-                'Use useNavigation() instead if this component can render under more than one navigator kind.');
-        }
-        return value;
-    });
-}

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

@@ -1,19 +0,0 @@
-import type { IStyleProp, IViewStyle } from '@symbiote-native/engine';
-import type { IDrawerDescriptorMap, IDrawerNavigatorHandle, IDrawerOptions, IDrawerRouterState } from '../../core';
-import type { IDrawerScreenProps } from '../drawer-screen';
-export type { IDrawerNavigatorHandle, IDrawerDescriptorMap } from '../../core';
-export type IDrawerContentSlotProps = {
-    state: IDrawerRouterState;
-    descriptors: IDrawerDescriptorMap;
-    navigation: IDrawerNavigatorHandle;
-};
-export type IDrawerProps = IDrawerOptions & {
-    initialRouteName?: string;
-    drawerStyle?: IStyleProp<IViewStyle>;
-};
-export declare const Drawer: import("vue").DefineSetupFnComponent<IDrawerProps, {}, {}, IDrawerOptions & {
-    initialRouteName?: string;
-    drawerStyle?: IStyleProp<IViewStyle>;
-} & {}, import("vue").PublicProps> & {
-    Screen: import("vue").DefineSetupFnComponent<IDrawerScreenProps, {}, {}, IDrawerScreenProps & {}, import("vue").PublicProps>;
-};