@symbiote-native/react 0.2.7 → 0.3.0

package/build/create-tunnel/index.js

@@ -1,26 +1,20 @@
 import { jsx as _jsx } from "react/jsx-runtime";
-// createTunnel — the cross-surface answer to createPortal's same-surface-only scope.
-// Prior art: pmndrs/tunnel-rat exists precisely because a real
-// createPortal cannot reach across two genuinely separate reconciler roots — see
-// github.com/facebook/react/issues/17147 ("react-reconciler & portals: missing root
-// instance"). The fix is the one the ecosystem already settled on: don't reach into a
-// foreign surface's commit machinery — let that surface commit ITSELF, normally, by reading
+// createTunnel - the cross-surface answer to createPortal's same-surface-only scope. A real
+// createPortal cannot reach across two separate reconciler roots (see
+// github.com/facebook/react/issues/17147); the fix, same as pmndrs/tunnel-rat, is to not
+// reach into a foreign surface's commit machinery - let that surface commit itself, reading
 // from a store it's already subscribed to.
 //
-// Both In and Out are COMPONENTS (the Vue twin's shape, and the same pattern as
-// Context.Provider/Context.Consumer) — NOT hooks. This isn't just nicer call-site ergonomics:
-// it's what makes the cascade in the first place structurally impossible. An earlier
-// hook-based version (`useTunnelIn`/`useTunnelOut`, called directly inside one component)
-// produced a genuine infinite render loop — a silent white screen on device, no thrown error
-// — because notify() forces a re-render of whichever component's useSyncExternalStore call
-// subscribed, and when THAT was the SAME component that also called useTunnelIn, its own
-// effect re-ran and notified again, forever (this custom renderer's synchronous commit loop
-// has no "Maximum update depth exceeded" guard to catch it). As separate components, notify()
-// only forces Out's OWN render scope — never In's, even when both are children of the same
-// parent — so the update has nowhere to bounce back to. `Out` lives inside whichever surface
-// should PAINT the content (e.g. a persistent overlay-host surface); `In` lives ANYWHERE, same
-// surface or a totally different one, and never touches a Fabric node directly, so there is
-// no "target must already be mounted" guard to satisfy at all.
+// In and Out are COMPONENTS (Context.Provider/Consumer shape), never hooks - this is
+// load-bearing, not just ergonomics. An earlier hook-based version caused a real infinite
+// render loop on device (silent white screen, no thrown error): notify() re-renders
+// whichever component's useSyncExternalStore subscription fired, and when that was the same
+// component calling useTunnelIn, its own effect re-notified itself forever - this custom
+// renderer's synchronous commit loop has no "Maximum update depth exceeded" guard. As
+// separate components, notify() only forces Out's own render scope, so the update has
+// nowhere to bounce back to. `Out` lives in whichever surface should PAINT the content; `In`
+// lives anywhere - same surface or a different one - and never touches a Fabric node
+// directly, so there's no "target must already be mounted" guard to satisfy.
 import { Fragment, useEffect, useId, useSyncExternalStore } from 'react';
 export function createTunnel() {
     const items = new Map();

package/build/hooks/use-color-scheme.d.ts

@@ -1,2 +1,2 @@
-import { type IColorSchemeName } from '../modules/appearance';
+import { type IColorSchemeName } from '@symbiote-native/engine';
 export declare function useColorScheme(): IColorSchemeName | null;

package/build/hooks/use-color-scheme.js

@@ -2,7 +2,7 @@
 // on change. Mirrors RN's Libraries/Utilities/useColorScheme.js: a thin
 // useSyncExternalStore over Appearance's change event + current scheme read.
 import { useSyncExternalStore } from 'react';
-import { Appearance } from '../modules/appearance.js';
+import { Appearance } from '@symbiote-native/engine';
 const subscribe = (onStoreChange) => {
     const subscription = Appearance.addChangeListener(onStoreChange);
     return () => subscription.remove();

package/build/hooks/use-window-dimensions.d.ts

@@ -1,2 +1,2 @@
-import { type IDisplayMetrics } from '../modules/dimensions';
+import { type IDisplayMetrics } from '@symbiote-native/engine';
 export declare function useWindowDimensions(): IDisplayMetrics;

package/build/hooks/use-window-dimensions.js

@@ -4,7 +4,7 @@
 // subscribing to close the gap between the render-time get and the effect-time
 // listener. Only the window metrics changing triggers a re-render.
 import { useEffect, useState } from 'react';
-import { Dimensions } from '../modules/dimensions.js';
+import { Dimensions } from '@symbiote-native/engine';
 export function useWindowDimensions() {
     const [dimensions, setDimensions] = useState(() => Dimensions.get('window'));
     useEffect(() => {

package/build/host-instance.js

@@ -1,9 +1,8 @@
-// The public instance a host ref hands back and the ref -> tag lookup. toPublicInstance and
-// IHostInstance now live in @symbiote-native/engine (they depend only on engine internals, so every
-// adapter inherits the SAME public instance); this module re-exports them so the React surface
-// (`@symbiote-native/react` exports findNodeHandle + IHostInstance, host-config grafts via
-// toPublicInstance) is unchanged. findNodeHandle stays here: it is the React-shaped "ref ->
-// native tag" lookup over the engine's getNativeTag.
+// The public instance a host ref hands back, and the ref -> tag lookup. toPublicInstance and
+// IHostInstance live in @symbiote-native/engine (every adapter inherits the same public instance);
+// this module re-exports them so the React surface (findNodeHandle + IHostInstance, host-config's
+// toPublicInstance graft) is unchanged. findNodeHandle stays React-specific: it is the
+// RN-shaped "ref -> native tag" lookup over the engine's getNativeTag.
 import { getNativeTag, isSymbioteNode, toPublicInstance, } from '@symbiote-native/engine';
 export { toPublicInstance };
 // The committed native tag of a host ref (or a bare tag, idempotent). RN's

package/build/index.d.ts

@@ -12,8 +12,6 @@ export { TextInput } from './components/text-input';
 export type { ITextInputProps, ITextInputHandle } from './components/text-input';
 export { InputAccessoryView } from './components/input-accessory-view';
 export type { IInputAccessoryViewProps } from './components/input-accessory-view';
-export { Keyboard, KEYBOARD_EVENT } from './modules/keyboard';
-export type { IKeyboardEventName } from './modules/keyboard';
 export { KeyboardAvoidingView } from './components/keyboard-avoiding-view';
 export type { IKeyboardAvoidingViewProps, IKeyboardAvoidingBehavior, } from './components/keyboard-avoiding-view';
 export { StatusBar } from './modules/status-bar';
@@ -55,44 +53,21 @@ export { Animated, createAnimatedComponent } from './modules/animated';
 export { Platform, StyleSheet } from '@symbiote-native/engine';
 export { PlatformColor, DynamicColorIOS, processColor } from '@symbiote-native/engine';
 export type { IColorValue, IOpaqueColorValue, IDynamicColorIOSTuple, } from '@symbiote-native/engine';
-export { setNativeViewConfigSource } from '@symbiote-native/engine';
+export { setNativeViewConfigSource, setColorProcessor, setDeviceEventSource, } from '@symbiote-native/engine';
+export { dlog, isDebug } from '@symbiote-native/engine';
 export type { INativeViewConfig, INativeViewConfigSource } from '@symbiote-native/engine';
 export type { IPlatformStatic, IPlatformOSType, IPlatformConstantsIOS, IPlatformConstantsAndroid, IPlatformSelectSpec, } from '@symbiote-native/engine';
-export { Dimensions } from './modules/dimensions';
-export type { IDisplayMetrics, IDisplayMetricsAndroid, IDimensionsPayload, IDimensionsSet, IDimensionsKey, IDimensionsChangeListener, IDimensionsStatic, } from './modules/dimensions';
-export { PixelRatio } from '@symbiote-native/engine';
-export type { IPixelRatioStatic } from '@symbiote-native/engine';
+export { Alert, Share, ActionSheetIOS, Linking, Vibration, ToastAndroid, Settings, I18nManager, Dimensions, Appearance, AppState, Keyboard, KEYBOARD_EVENT, BackHandler, PermissionsAndroid, PERMISSIONS, RESULTS, LayoutAnimation, PixelRatio, } from '@symbiote-native/engine';
+export type { IAlertType, IAlertButtonStyle, IAlertButton, IAlertButtons, IAlertOptions, IShareContent, IShareOptions, IShareAction, IActionSheetIOSOptions, IShareActionSheetIOSOptions, IShareActionSheetError, IUrlEvent, II18nManagerConstants, IDisplayMetrics, IDisplayMetricsAndroid, IDimensionsPayload, IDimensionsSet, IDimensionsKey, IDimensionsChangeListener, IDimensionsStatic, IColorSchemeName, IColorSchemePreference, IAppStateStatus, IAppStateEvent, IKeyboardEventName, IKeyboardEvent, IKeyboardMetrics, IBackPressEventName, IBackPressHandler, IPermission, IPermissionStatus, IRationale, ILayoutAnimationType, ILayoutAnimationProperty, ILayoutAnimationConfig, ILayoutAnimationAnim, IPixelRatioStatic, } from '@symbiote-native/engine';
 export { useWindowDimensions } from './hooks/use-window-dimensions';
-export { Appearance } from './modules/appearance';
-export type { IColorSchemeName, IColorSchemePreference } from './modules/appearance';
 export { useColorScheme } from './hooks/use-color-scheme';
-export { AppState } from './modules/app-state';
-export type { IAppStateStatus, IAppStateEvent } from './modules/app-state';
-export { Alert } from './modules/alert';
-export type { IAlertType, IAlertButtonStyle, IAlertButton, IAlertButtons, IAlertOptions, } from './modules/alert';
-export { ActionSheetIOS } from './modules/action-sheet-ios';
-export type { IActionSheetIOSOptions, IShareActionSheetIOSOptions, IShareActionSheetError, } from './modules/action-sheet-ios';
-export { Linking } from './modules/linking';
-export type { IUrlEvent } from './modules/linking';
-export { Vibration } from './modules/vibration';
-export { Share } from './modules/share';
-export type { IShareContent, IShareOptions, IShareAction } from './modules/share';
 export { AccessibilityInfo } from './modules/accessibility-info';
 export type { IAccessibilityChangeEvent, IAccessibilityChangeEventName, IAccessibilityChangeEventHandler, IAccessibilityAnnouncementFinishedEvent, IAnnounceForAccessibilityOptions, IAccessibilityEventType, } from './modules/accessibility-info';
-export { I18nManager } from './modules/i18n-manager';
-export type { II18nManagerConstants } from './modules/i18n-manager';
-export { Settings } from './modules/settings';
 export { PanResponder } from '@symbiote-native/engine';
 export type { IPanResponderGestureState, IPanResponderCallbacks, IGestureResponderHandlers, IPanResponderInstance, } from '@symbiote-native/engine';
-export { LayoutAnimation } from './modules/layout-animation';
-export type { ILayoutAnimationType, ILayoutAnimationProperty, ILayoutAnimationConfig, ILayoutAnimationAnim, } from './modules/layout-animation';
 export { InteractionManager } from '@symbiote-native/engine';
 export type { IInteractionEvent, ISimpleTask, IPromiseTask, ITask, IHandle, } from '@symbiote-native/engine';
-export { BackHandler } from './modules/back-handler';
-export type { IBackPressEventName, IBackPressHandler } from './modules/back-handler';
-export { ToastAndroid } from './modules/toast-android';
-export { PermissionsAndroid, PERMISSIONS, RESULTS } from './modules/permissions-android';
-export type { IPermission, IPermissionStatus, IRationale } from './modules/permissions-android';
 export { TouchableNativeFeedback } from './components/touchable-native-feedback';
 export type { ITouchableNativeFeedbackProps, INativeFeedbackBackground, IThemeAttrBackground, IRippleBackground, } from './components/touchable-native-feedback';
-export type { ISymbioteEvent } from '@symbiote-native/engine';
+export type { ISymbioteEvent, ISymbioteNode, IRootTag } from '@symbiote-native/engine';
+export type { ICellLayout, ISeparatorProps, ISeparators, IModalOrientationChangeEvent, IPressableAndroidRippleConfig, IEnterKeyHint, IInputMode, ISubmitBehavior, ITextInputSelection, IImageStatics, } from '@symbiote-native/components';

package/build/index.js

@@ -7,7 +7,6 @@ export { ImageBackground } from './components/image-background/index.js';
 export { ScrollView } from './components/scroll-view';
 export { TextInput } from './components/text-input/index.js';
 export { InputAccessoryView } from './components/input-accessory-view/index.js';
-export { Keyboard, KEYBOARD_EVENT } from './modules/keyboard.js';
 export { KeyboardAvoidingView } from './components/keyboard-avoiding-view/index.js';
 export { StatusBar } from './modules/status-bar';
 export { Switch } from './components/switch';
@@ -51,37 +50,28 @@ export { Platform, StyleSheet } from '@symbiote-native/engine';
 // processColor runs a color through the injected platform processor. All pure /
 // seam-backed, so they live in shared and the adapter re-exports them.
 export { PlatformColor, DynamicColorIOS, processColor } from '@symbiote-native/engine';
-// Wired once by the app entry on a real host (like setColorProcessor): hands shared
-// RN's ViewConfig registry so third-party Fabric views auto-derive their metadata:
+// The three app-entry seams, wired once on a real host, so the barrel exposes them together.
+// setNativeViewConfigSource hands the engine RN's ViewConfig registry, which is how third-party
+// Fabric views auto-derive their metadata:
 //   setNativeViewConfigSource(name => ReactNativeViewConfigRegistry.get(name))
-export { setNativeViewConfigSource } from '@symbiote-native/engine';
-// Runtime modules: native-bridge consumers, same shape as Keyboard/StatusBar:
-// thin JS over getNativeModule + device events, no Fabric component of their own.
-export { Dimensions } from './modules/dimensions.js';
-export { PixelRatio } from '@symbiote-native/engine';
+export { setNativeViewConfigSource, setColorProcessor, setDeviceEventSource, } from '@symbiote-native/engine';
+// Diagnostics, gated by DEBUG (<keep_logs_gate_behind_DEBUG>): app code logs through the same
+// seam the engine does instead of a bare console.log.
+export { dlog, isDebug } from '@symbiote-native/engine';
+// Imperative runtime modules: the SAME module every adapter shares, re-exported straight from
+// @symbiote-native/engine so app code names only @symbiote-native/react (RN's single import
+// root). Thin JS over getNativeModule + device events, no Fabric component of their own.
+export { Alert, Share, ActionSheetIOS, Linking, Vibration, ToastAndroid, Settings, I18nManager, Dimensions, Appearance, AppState, Keyboard, KEYBOARD_EVENT, BackHandler, PermissionsAndroid, PERMISSIONS, RESULTS, LayoutAnimation, PixelRatio, } from '@symbiote-native/engine';
+// React lifecycle over those core device-state modules.
 export { useWindowDimensions } from './hooks/use-window-dimensions.js';
-export { Appearance } from './modules/appearance.js';
 export { useColorScheme } from './hooks/use-color-scheme.js';
-export { AppState } from './modules/app-state.js';
-export { Alert } from './modules/alert.js';
-export { ActionSheetIOS } from './modules/action-sheet-ios.js';
-export { Linking } from './modules/linking.js';
-export { Vibration } from './modules/vibration.js';
-export { Share } from './modules/share.js';
 export { AccessibilityInfo } from './modules/accessibility-info';
-export { I18nManager } from './modules/i18n-manager.js';
-export { Settings } from './modules/settings.js';
 // Interaction subsystems: gestures, deferred work, and layout transitions.
 export { PanResponder } from '@symbiote-native/engine';
-export { LayoutAnimation } from './modules/layout-animation.js';
 // InteractionManager is pure JS, so it lives in shared; re-exported here so app code
 // names only @symbiote-native/react (RN's single import root).
 export { InteractionManager } from '@symbiote-native/engine';
-// Android-only surface (the second-platform pass). Each is a thin JS shim over an
-// Android native module / Fabric view, inert on iOS (no module → graceful no-op,
-// no native view → degrade to a plain container). Native module name correctness
-// can only be confirmed on a real device/simulator, not headless tests.
-export { BackHandler } from './modules/back-handler.js';
-export { ToastAndroid } from './modules/toast-android.js';
-export { PermissionsAndroid, PERMISSIONS, RESULTS } from './modules/permissions-android.js';
+// Android-only surface (the second-platform pass): a thin JS shim over an Android Fabric view,
+// inert on iOS (no native view -> degrades to a plain container). The Android-only MODULES
+// (ToastAndroid, PermissionsAndroid, BackHandler) sit in the engine block above.
 export { TouchableNativeFeedback } from './components/touchable-native-feedback/index.js';

package/build/modules/animated/create-animated-component.js

@@ -13,8 +13,8 @@
 // and detaches on unmount / when the leaf identity changes. The per-frame path is
 // then: value.setValue / animation -> flushValue -> AnimatedProps.update() ->
 // setNativeProps(node, partial).
-import { createElement, useEffect, useMemo, useRef, } from 'react';
-import { AnimatedProps, attachNativeEventHandler, isNativeAnimatedAvailable, reduceProps, readPassthroughStyle, resolveHostNode, } from '@symbiote-native/engine';
+import { createElement, useEffect, useRef, } from 'react';
+import { createAnimatedLeafLifecycle, isSymbioteNode, isNativeAnimatedAvailable, reduceProps, readPassthroughStyle, resolveHostNode, } from '@symbiote-native/engine';
 // A ref can be a function or a `.current` object; assign through both forms without
 // casting so a forwarded ref from the caller still receives the instance. Framework-
 // ref-specific, so it stays per-adapter (the rest of the wrap helpers are shared).
@@ -33,77 +33,36 @@ export function createAnimatedComponent(Component) {
         // Native driving is opt-in per the passthrough prop AND requires a real native module;
         // headless / unsupported hosts keep the JS flush path (and the existing JS smokes green).
         const wantsNative = passthrough != null && isNativeAnimatedAvailable();
-        // One AnimatedProps leaf per distinct props object. Rebuilt when props change,
-        // so a newly-added animated value joins the graph; the effect below swaps the
-        // graph attachment to match.
-        const animatedProps = useMemo(() => new AnimatedProps(rest), [rest]);
-        // The leaf currently wired into the value graph. Tracked across renders so a swap
-        // can attach the new leaf BEFORE detaching the old one.
-        const attached = useRef(null);
-        // The committed host node, captured by the ref below. Needed in the event-attach
-        // effect (a native event binds to the node's tag, not the AnimatedProps leaf).
+        // The leaf lifecycle - build/swap/bind/detach, native event rebinding, and the
+        // rebuild-vs-skip decision - is the engine's, shared by every adapter
+        // (core/engine/src/animated/leaf-lifecycle.ts). React owns only WHEN to run it.
+        //
+        // This used to be `useMemo(() => new AnimatedProps(rest), [rest])`, which reads like the same
+        // guard but never was one: `rest` comes out of a rest-destructure, so it is a fresh object on
+        // every render and the memo's dependency always differed. The real content check now lives in
+        // the shared lifecycle.
+        const lifecycleRef = useRef(null);
+        lifecycleRef.current ??= createAnimatedLeafLifecycle('react');
+        const lifecycle = lifecycleRef.current;
+        // The committed host node, captured by the ref below - a native event binds to the node's
+        // tag, not the AnimatedProps leaf.
         const nodeRef = useRef(null);
-        // Swap the graph attachment to the current leaf, attaching the new one FIRST and
-        // detaching the previous one SECOND. Order is load-bearing: a shared Value node
-        // self-detaches (and drops its native animation node) the instant its child count
-        // hits zero, so detaching the old leaf before the new one is attached would kill a
-        // running native-driven animation on any unrelated re-render. Detaching here (not
-        // in a cleanup, which React runs BEFORE the next setup) keeps the new-before-old
-        // order, mirroring RN's AnimatedComponent._attachProps.
+        // Reconcile after every commit. No dependency array on purpose: the props object is rebuilt
+        // by every render anyway, so a dependency list could only ever say "always" - the real
+        // rebuild-vs-skip decision is the lifecycle's, and it compares CONTENT by key identity.
         useEffect(() => {
-            animatedProps.__attach();
-            const previous = attached.current;
-            attached.current = animatedProps;
-            if (previous !== null && previous !== animatedProps) {
-                previous.__detach();
-            }
-        }, [animatedProps]);
-        // Native-driver trigger. Runs after attach: push the leaf -> style -> transform
-        // -> interpolation -> value chain native so the props animate on the UI thread (no JS lag).
-        // Cascades down to the source value; the scroll event attaches to that same value
-        // (idempotent). __makeNative is idempotent, so re-firing on a leaf swap is safe.
+            lifecycle.reconcile(rest, isSymbioteNode(nodeRef.current) ? nodeRef.current : null, wantsNative);
+        });
+        // Final teardown: detach the last-attached leaf and any native event bindings on unmount.
         useEffect(() => {
-            if (wantsNative)
-                animatedProps.__makeNative();
-        }, [animatedProps, wantsNative]);
-        // Final teardown: detach the last-attached leaf when the component unmounts.
-        useEffect(() => {
-            return () => {
-                if (attached.current !== null) {
-                    attached.current.__detach();
-                    attached.current = null;
-                }
-            };
-        }, []);
-        // Native-attach any Animated.event prop, e.g. onScroll={Animated.event(…,
-        // {useNativeDriver:true})}, to the committed node, so the event drives its values on
-        // the UI thread. attachNativeEventHandler no-ops (returns undefined) unless the prop is
-        // a native event handler with a committed tag, so the JS path stays the fallback. The
-        // __makeNative cascade then carries the bound interpolations/props native too. Keyed on
-        // animatedProps (rebuilt with rest) so a new inline event re-attaches; cleanup detaches.
-        useEffect(() => {
-            const node = nodeRef.current;
-            if (node === null)
-                return;
-            const detachers = [];
-            for (const key of Object.keys(rest)) {
-                const attachment = attachNativeEventHandler(node, key, rest[key]);
-                if (attachment !== undefined)
-                    detachers.push(attachment.detach);
-            }
-            return () => {
-                for (const detach of detachers)
-                    detach();
-            };
-        }, [animatedProps]);
+            return () => lifecycle.teardown();
+        }, [lifecycle]);
         // Callback ref: when the base component mounts, capture its public instance, resolve
         // it to the underlying host node (unwrapping a scroll-container handle), record THAT
         // for the event-attach effect and bind it to the leaf, but forward the ORIGINAL
         // instance to the caller, who expects the component's public handle (scrollTo, …).
         const captureRef = (instance) => {
-            const node = resolveHostNode(instance);
-            nodeRef.current = node;
-            animatedProps.setNativeView(node);
+            nodeRef.current = resolveHostNode(instance);
             assignRef(forwardedRef, instance);
         };
         // Reduced props are P-shaped (animated nodes already replaced by values); add the

package/build/render.js

@@ -1,15 +1,37 @@
 // Mount a React element tree onto a Fabric surface. The native host hands us a
 // rootTag (via AppRegistry.registerRunnable); we create a surface for it and let
 // the reconciler drive shared, which commits into nativeFabricUIManager.
-import { createSurface, disposeRoot, setEventDispatcher, dlog, } from '@symbiote-native/engine';
+import { createSurface, disposeRoot, setEventDispatcher, dlog, reportUncaughtError, } from '@symbiote-native/engine';
 import reconciler, { withDiscretePriority } from './host-config.js';
 import { LegacyRoot } from './reconciler-constants.js';
 const noop = () => { };
+function errorReporter(origin) {
+    return (error, info) => {
+        reportUncaughtError(error, { origin, componentStack: info.componentStack });
+    };
+}
+const onUncaughtError = errorReporter('react render (no error boundary)');
+// A boundary handled it, and it is still reported - the boundary decides what the USER sees, not
+// whether the developer hears about it. Upstream's nativeOnCaughtError calls the same
+// showErrorDialog as the uncaught path.
+const onCaughtError = errorReporter('react render (caught by error boundary)');
+// React recovered on its own (a concurrent render retried and succeeded), so this is not fatal -
+// but it is still a real error the app swallowed a first render over. RN keeps React's
+// defaultOnRecoverableError here, which reports it globally.
+const onRecoverableError = errorReporter('react render (recovered)');
 // A native event runs the listener (which may call setState) outside React's
 // loop. Run it at discrete priority so the update takes the sync lane, then
 // flush that work synchronously to paint the result.
+//
+// Diagnostic seam (gated, perf investigation): every native event forces its own
+// synchronous flush here, with no continuous-vs-discrete split (unlike DOM React,
+// which lets high-frequency continuous events like drag/scroll coalesce). This
+// dlog counts how many forced flushes one gesture (e.g. a Slider drag) produces,
+// to compare against Vue/Angular's microtask-coalesced requestCommit(). Kept
+// behind DEBUG per <keep_logs_gate_behind_DEBUG>, never removed.
 setEventDispatcher(run => {
     withDiscretePriority(run);
+    dlog('react event-dispatch: forced flushSyncWork');
     // @ts-expect-error flushSyncWork exists at runtime in react-reconciler 0.33
     reconciler.flushSyncWork();
 });
@@ -33,7 +55,11 @@ export function mount(rootTag, element) {
     // first) starts clean. Otherwise the stale container double-drives the surface.
     teardown(rootTag);
     const surface = createSurface(rootTag);
-    const container = reconciler.createContainer(surface, LegacyRoot, null, false, null, 'symbiote', noop, noop, noop, noop, null);
+    const container = reconciler.createContainer(surface, LegacyRoot, null, false, null, 'symbiote', onUncaughtError, onCaughtError, onRecoverableError, 
+    // onDefaultTransitionIndicator - the ONE that is genuinely a no-op. RN's own renderer says
+    // so in as many words: "Native doesn't have a default indicator" (ReactFabric.js's
+    // nativeOnDefaultTransitionIndicator).
+    noop, null);
     containers.set(rootTag, container);
     // react-reconciler 0.33 exposes updateContainerSync + flushSyncWork for an
     // immediate render/commit; @types 0.32 still lists the older updateContainer /

package/metro-css-parser.cjs

@@ -1,13 +1,8 @@
-// Re-exports @symbiote-native/css-parser verbatim from INSIDE this package, so a consuming app's own
-// require('@symbiote-native/react/metro-css-parser') resolves css-parser relative to THIS file's
-// location (adapters/react/node_modules, where css-parser IS a real dependency — see
-// package.json), not relative to the app's own node_modules, which does not and should not
-// need to declare @symbiote-native/css-parser itself. Node resolves each require() relative to the
-// requiring FILE's own location, so this indirection is what actually removes the extra install
-// step, not pnpm hoisting (which does not propagate this transitively across workspace packages
-// the way a flat classic node_modules would). .cjs, not .js: this package is "type": "module",
-// and Metro's babelTransformerPath loading expects a require()-able module.
-// createCssMetroTransformer is a factory, not a ready transformer — Metro's
-// babelTransformerPath needs the actual {transform, getCacheKey} object it returns,
-// not the css-parser package barrel.
+// Re-exported from THIS file's own location so a consuming app's
+// require('@symbiote-native/react/metro-css-parser') resolves css-parser as a dependency of THIS
+// package, not the app's node_modules (Node resolves require() relative to the requiring file,
+// not via pnpm hoisting) — the app never needs to declare @symbiote-native/css-parser itself.
+// .cjs, not .js: this package is "type": "module", but Metro's babelTransformerPath loading needs
+// a require()-able file. createCssMetroTransformer() is a factory — Metro needs the actual
+// {transform, getCacheKey} object it returns, not the css-parser package barrel.
 module.exports = require('@symbiote-native/css-parser').createCssMetroTransformer();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@symbiote-native/react",
-  "version": "0.2.7",
+  "version": "0.3.0",
   "description": "SymbioteNative's React adapter — a react-reconciler host config (mutation mode) driving real native iOS/Android views through stock React Native Fabric.",
   "license": "MIT",
   "repository": {
@@ -37,8 +37,8 @@
   },
   "dependencies": {
     "react-reconciler": "^0.33.0",
-    "@symbiote-native/components": "0.2.6",
-    "@symbiote-native/css-parser": "0.2.3"
+    "@symbiote-native/components": "0.4.0",
+    "@symbiote-native/css-parser": "0.3.0"
   },
   "peerDependencies": {
     "@symbiote-native/engine": ">=0.1.7",
@@ -49,7 +49,7 @@
     "@types/react": "^19.2.0",
     "@types/react-reconciler": "^0.32.2",
     "react": "19.2.3",
-    "@symbiote-native/engine": "0.1.7",
+    "@symbiote-native/engine": "0.2.0",
     "@symbiote-native/test-utils": "0.1.6"
   },
   "scripts": {

package/build/modules/action-sheet-ios.d.ts

@@ -1,2 +0,0 @@
-export { ActionSheetIOS } from '@symbiote-native/engine';
-export type { IActionSheetIOSOptions, IShareActionSheetIOSOptions, IShareActionSheetError, } from '@symbiote-native/engine';

package/build/modules/action-sheet-ios.js

@@ -1,4 +0,0 @@
-// ActionSheetIOS lives framework-agnostic in @symbiote-native/engine (imperative
-// native-bridge module, no visual, no lifecycle). The React adapter re-exports it
-// verbatim so the public surface is unchanged.
-export { ActionSheetIOS } from '@symbiote-native/engine';

package/build/modules/alert.d.ts

@@ -1,2 +0,0 @@
-export { Alert } from '@symbiote-native/engine';
-export type { IAlertType, IAlertButtonStyle, IAlertButton, IAlertButtons, IAlertOptions, } from '@symbiote-native/engine';

package/build/modules/alert.js

@@ -1,5 +0,0 @@
-// Alert lives framework-agnostic in @symbiote-native/engine (imperative native-bridge
-// module, no visual, no lifecycle). The React adapter re-exports it verbatim so the
-// public surface is unchanged; the platform split (alert.ios/alert.android) lives
-// inside engine.
-export { Alert } from '@symbiote-native/engine';

package/build/modules/app-state.d.ts

@@ -1,2 +0,0 @@
-export { AppState } from '@symbiote-native/engine';
-export type { IAppStateStatus, IAppStateEvent } from '@symbiote-native/engine';

package/build/modules/app-state.js

@@ -1,3 +0,0 @@
-// AppState moved to @symbiote-native/engine (a framework-agnostic device-state module re-exported
-// by every adapter). This thin re-export keeps @symbiote-native/react's public surface identical.
-export { AppState } from '@symbiote-native/engine';

package/build/modules/appearance.d.ts

@@ -1,2 +0,0 @@
-export { Appearance } from '@symbiote-native/engine';
-export type { IColorSchemeName, IColorSchemePreference } from '@symbiote-native/engine';

package/build/modules/appearance.js

@@ -1,3 +0,0 @@
-// Appearance moved to @symbiote-native/engine (a framework-agnostic device-state module re-exported
-// by every adapter). This thin re-export keeps @symbiote-native/react's public surface identical.
-export { Appearance } from '@symbiote-native/engine';

package/build/modules/back-handler.d.ts

@@ -1,2 +0,0 @@
-export { BackHandler } from '@symbiote-native/engine';
-export type { IBackPressEventName, IBackPressHandler } from '@symbiote-native/engine';

package/build/modules/back-handler.js

@@ -1,3 +0,0 @@
-// BackHandler moved to @symbiote-native/engine (a framework-agnostic device-state module re-exported
-// by every adapter). This thin re-export keeps @symbiote-native/react's public surface identical.
-export { BackHandler } from '@symbiote-native/engine';

package/build/modules/dimensions.d.ts

@@ -1,2 +0,0 @@
-export { Dimensions } from '@symbiote-native/engine';
-export type { IDisplayMetrics, IDisplayMetricsAndroid, IDimensionsPayload, IDimensionsSet, IDimensionsKey, IDimensionsChangeListener, IDimensionsStatic, } from '@symbiote-native/engine';

package/build/modules/dimensions.js

@@ -1,3 +0,0 @@
-// Dimensions moved to @symbiote-native/engine (a framework-agnostic device-state module re-exported
-// by every adapter). This thin re-export keeps @symbiote-native/react's public surface identical.
-export { Dimensions } from '@symbiote-native/engine';

package/build/modules/i18n-manager.d.ts

@@ -1,2 +0,0 @@
-export { I18nManager } from '@symbiote-native/engine';
-export type { II18nManagerConstants } from '@symbiote-native/engine';

package/build/modules/i18n-manager.js

@@ -1,4 +0,0 @@
-// I18nManager now lives framework-agnostic in @symbiote-native/engine (imperative
-// native-bridge module, no visual, no lifecycle). The React adapter re-exports it
-// verbatim so the public surface is unchanged.
-export { I18nManager } from '@symbiote-native/engine';

package/build/modules/keyboard.d.ts

@@ -1,2 +0,0 @@
-export { Keyboard, KEYBOARD_EVENT } from '@symbiote-native/engine';
-export type { IKeyboardEventName, IKeyboardEvent, IKeyboardMetrics } from '@symbiote-native/engine';

package/build/modules/keyboard.js

@@ -1,3 +0,0 @@
-// Keyboard moved to @symbiote-native/engine (a framework-agnostic device-state module re-exported
-// by every adapter). This thin re-export keeps @symbiote-native/react's public surface identical.
-export { Keyboard, KEYBOARD_EVENT } from '@symbiote-native/engine';

package/build/modules/layout-animation.d.ts

@@ -1,2 +0,0 @@
-export { LayoutAnimation } from '@symbiote-native/engine';
-export type { ILayoutAnimationType, ILayoutAnimationProperty, ILayoutAnimationConfig, ILayoutAnimationAnim, ILayoutAnimationTypes, ILayoutAnimationProperties, } from '@symbiote-native/engine';

package/build/modules/layout-animation.js

@@ -1,3 +0,0 @@
-// LayoutAnimation moved to @symbiote-native/engine (a framework-agnostic native-bridge consumer
-// re-exported by every adapter). This thin re-export keeps @symbiote-native/react's surface identical.
-export { LayoutAnimation } from '@symbiote-native/engine';

package/build/modules/linking.d.ts

@@ -1,2 +0,0 @@
-export { Linking } from '@symbiote-native/engine';
-export type { IUrlEvent } from '@symbiote-native/engine';

package/build/modules/linking.js

@@ -1,4 +0,0 @@
-// Linking now lives framework-agnostic in @symbiote-native/engine (imperative native-bridge
-// module, no visual, no lifecycle). The React adapter re-exports it verbatim; the
-// platform split (linking.ios/linking.android) lives inside engine.
-export { Linking } from '@symbiote-native/engine';

package/build/modules/permissions-android.d.ts

@@ -1,2 +0,0 @@
-export { PermissionsAndroid, PERMISSIONS, RESULTS } from '@symbiote-native/engine';
-export type { IPermission, IPermissionStatus, IRationale } from '@symbiote-native/engine';

package/build/modules/permissions-android.js

@@ -1,3 +0,0 @@
-// PermissionsAndroid moved to @symbiote-native/engine (a framework-agnostic device-state module
-// re-exported by every adapter). This thin re-export keeps @symbiote-native/react's surface identical.
-export { PermissionsAndroid, PERMISSIONS, RESULTS } from '@symbiote-native/engine';

package/build/modules/settings.d.ts

@@ -1 +0,0 @@
-export { Settings } from '@symbiote-native/engine';

package/build/modules/settings.js

@@ -1,4 +0,0 @@
-// Settings now lives framework-agnostic in @symbiote-native/engine (imperative native-bridge
-// module, no visual, no lifecycle). The React adapter re-exports it verbatim so the
-// public surface is unchanged.
-export { Settings } from '@symbiote-native/engine';

package/build/modules/share.d.ts

@@ -1,2 +0,0 @@
-export { Share } from '@symbiote-native/engine';
-export type { IShareContent, IShareOptions, IShareAction } from '@symbiote-native/engine';

package/build/modules/share.js

@@ -1,4 +0,0 @@
-// Share now lives framework-agnostic in @symbiote-native/engine (imperative native-bridge
-// module, no visual, no lifecycle). The React adapter re-exports it verbatim; the
-// platform split (share.ios/share.android) lives inside engine.
-export { Share } from '@symbiote-native/engine';

package/build/modules/text-input-state.d.ts

@@ -1 +0,0 @@
-export { currentlyFocusedInput, setInputFocused, setInputBlurred, blurTextInput, } from '@symbiote-native/engine';

package/build/modules/text-input-state.js

@@ -1,3 +0,0 @@
-// TextInputState moved to @symbiote-native/engine (a framework-agnostic module: Keyboard.dismiss
-// and TextInput both reach it). This thin re-export keeps the adapter's import path stable.
-export { currentlyFocusedInput, setInputFocused, setInputBlurred, blurTextInput, } from '@symbiote-native/engine';

package/build/modules/toast-android.d.ts

@@ -1 +0,0 @@
-export { ToastAndroid } from '@symbiote-native/engine';

package/build/modules/toast-android.js

@@ -1,4 +0,0 @@
-// ToastAndroid lives framework-agnostic in @symbiote-native/engine (imperative
-// native-bridge module, no visual, no lifecycle). The React adapter re-exports it
-// verbatim so the public surface is unchanged.
-export { ToastAndroid } from '@symbiote-native/engine';

package/build/modules/vibration.d.ts

@@ -1 +0,0 @@
-export { Vibration } from '@symbiote-native/engine';