@symbiote-native/vue 1.0.0 → 3.0.0

package/build/components/touchable.js

@@ -1,281 +0,0 @@
-// The Touchable* family for Vue, all built on Pressable. Ported against RN's own sources
-// (.vendors/react-native/.../Components/Touchable/*.js) after the 2026-08-19 audit found ten
-// divergences shared by the React/Vue/Svelte/Angular ports; Solid migrated first, this is Vue.
-//
-// Shared (framework-agnostic) half: the press-scheduling machine, the underlay machine, the
-// resting-opacity math, the press-handler gate, the extra-style split. Vue owns only the
-// lifecycle — refs, the real timers, the Animated wiring, and the emit bridge:
-//   TouchableOpacity: an Animated.Value fading toward activeOpacity on press-in and back to the
-//     style's own opacity on press-out.
-//   TouchableHighlight: the underlay machine flipping a `shown` ref; underlayColor lands on the
-//     container, the lowered opacity on the cloned child.
-//   TouchableWithoutFeedback: the same press-scheduling machine with the visual half empty.
-//
-// Inputs arrive as attrs (untyped), narrowed with runtime guards. The handlers read attrs LIVE
-// (they fire on events, not render) so a re-supplied callback / timing is always honored.
-import { cloneVNode, defineComponent, getCurrentInstance, h, onUnmounted, ref, watch, } from '@vue/runtime-core';
-import { createHighlightUnderlayHandlers, createHighlightUnderlayRuntime, createTouchableFeedbackHandlers, createTouchableFeedbackRuntime, hasTouchablePressHandler, resolveHighlightExtraStyles, restingOpacityFromStyle, DEFAULT_ACTIVE_OPACITY, OPACITY_ACTIVE_GRANT_DURATION_MS, OPACITY_INACTIVE_DURATION_MS, TOUCHABLE_MIN_PRESS_DURATION_MS, } from '@symbiote-native/components';
-import { dlog, } from '@symbiote-native/engine';
-import { Pressable, emitPressableEvents, PRESSABLE_EMITS, } from './pressable.js';
-import { Animated } from '../modules/animated/index.js';
-import { normalizeVueAttrs } from '../utils/normalize-attrs.js';
-const TOUCHABLE_HIGHLIGHT_EMITS = {
-    ...PRESSABLE_EMITS,
-    showUnderlay: () => true,
-    hideUnderlay: () => true,
-};
-function numberOr(value, fallback) {
-    return typeof value === 'number' ? value : fallback;
-}
-// The real setTimeout the shared machines schedule their deferred activation/deactivation/underlay
-// hide on (core/components has no timer globals). Returns a canceller so an early release flushes
-// the timer.
-function scheduleTimeout(callback, ms) {
-    const id = setTimeout(callback, ms);
-    return () => clearTimeout(id);
-}
-function forwardExcept(attrs, handled) {
-    const result = {};
-    for (const key of Object.keys(attrs)) {
-        if (!handled.includes(key))
-            result[key] = attrs[key];
-    }
-    return result;
-}
-const TOUCHABLE_OPACITY_HANDLED = [
-    'activeOpacity',
-    'style',
-    'class',
-    'onPressIn',
-    'onPressOut',
-    'delayPressIn',
-    'delayPressOut',
-    'minPressDuration',
-];
-export const TouchableOpacity = defineComponent((_props, { slots, attrs: rawAttrs, emit }) => {
-    // RN's _getChildStyleOpacityWithDefault: the fade settles at the opacity the CALLER's style
-    // asks for, not at a hard 1 — and the Animated.Value is SEEDED there, or the first paint jumps
-    // to fully opaque on a Touchable styled `opacity: 0.6`.
-    const restingOpacity = () => restingOpacityFromStyle(normalizeVueAttrs(rawAttrs).style);
-    // One Animated.Value per mount. Held by identity in setup scope (an engine object, never a
-    // reactive ref — a Proxy would miss the graph's bookkeeping). The Animated.View leaf commits
-    // it every frame.
-    const opacity = new Animated.Value(restingOpacity());
-    // The shared press-scheduling cell (delayPressIn timer + activation clock), persisted across
-    // renders in setup scope; the handlers are rebuilt each render over live attrs.
-    const runtime = createTouchableFeedbackRuntime();
-    function setOpacityTo(toValue, duration) {
-        dlog(`TouchableOpacity opacity -> ${toValue} over ${duration}ms`);
-        // useNativeDriver: true is RN's own (TouchableOpacity.js:242). opacity is natively drivable,
-        // so the fade survives a busy JS thread — the whole point of press feedback.
-        Animated.timing(opacity, {
-            toValue,
-            duration,
-            easing: Animated.Easing.inOut(Animated.Easing.quad),
-            useNativeDriver: true,
-        }).start();
-    }
-    // RN's componentDidUpdate: a changed `disabled` or a changed style opacity re-settles the view,
-    // so a Touchable disabled mid-press does not stay stuck at its active opacity. NO `immediate` —
-    // RN does this on UPDATE only, and firing at mount would animate over the value the
-    // Animated.Value was just seeded with. Two getter sources, not one object: Vue compares an
-    // array source element-wise, so an unrelated attr change does not re-settle the opacity.
-    watch([() => normalizeVueAttrs(rawAttrs).disabled, restingOpacity], ([, resting]) => {
-        setOpacityTo(resting, OPACITY_INACTIVE_DURATION_MS);
-    });
-    // RN's componentWillUnmount: stop the animation and drop the value back, so a teardown
-    // mid-fade leaves no driver running against a node that is gone.
-    onUnmounted(() => {
-        opacity.resetAnimation();
-    });
-    return () => {
-        const attrs = normalizeVueAttrs(rawAttrs);
-        const style = attrs.style;
-        // Rebuilt each render so a re-supplied delay/opacity is honored (Vue's live-attr idiom); the
-        // shared machine owns the scheduling, the adapter supplies the Animated fade + emit.
-        const { handlePressIn, handlePressOut } = createTouchableFeedbackHandlers({
-            delayPressIn: numberOr(attrs.delayPressIn, 0),
-            delayPressOut: numberOr(attrs.delayPressOut, 0),
-            // RN's Touchables override Pressability's 130ms floor with 0; what holds the active
-            // visual is the fade's own duration, not a press-duration floor.
-            minPressDuration: numberOr(attrs.minPressDuration, TOUCHABLE_MIN_PRESS_DURATION_MS),
-            schedule: scheduleTimeout,
-            now: Date.now,
-        }, runtime, {
-            activate(event) {
-                setOpacityTo(numberOr(attrs.activeOpacity, DEFAULT_ACTIVE_OPACITY), OPACITY_ACTIVE_GRANT_DURATION_MS);
-                emit('pressIn', event);
-            },
-            deactivate(event) {
-                setOpacityTo(restingOpacity(), OPACITY_INACTIVE_DURATION_MS);
-                emit('pressOut', event);
-            },
-        });
-        const pressableProps = {
-            __minPressDuration: 0,
-            ...forwardExcept(attrs, TOUCHABLE_OPACITY_HANDLED),
-            ...emitPressableEvents(emit),
-            onPressIn: handlePressIn,
-            onPressOut: handlePressOut,
-        };
-        const children = slots.default !== undefined ? slots.default() : [];
-        const feedback = h(Animated.View, { style: [style, { opacity }], class: attrs.class }, () => children);
-        return h(Pressable, pressableProps, { default: () => [feedback] });
-    };
-}, {
-    name: 'TouchableOpacity',
-    inheritAttrs: false,
-    emits: PRESSABLE_EMITS,
-});
-// delayPressOut is CONSUMED here (the underlay hold), so it must not also forward to the host.
-// onPress/onPressIn/onPressOut/onShowUnderlay/onHideUnderlay never appear in attrs at all — they
-// are declared emits, which Vue strips from $attrs.
-const TOUCHABLE_HIGHLIGHT_HANDLED = [
-    'activeOpacity',
-    'underlayColor',
-    'style',
-    'delayPressOut',
-];
-// A vnode that can carry a style prop: a host tag (string) or a component (object/function).
-// Fragment / Text / Comment / Static are Symbols and fail all three — cloning one with a style
-// would silently drop it.
-function isStylableVNode(vnode) {
-    const type = vnode.type;
-    return (typeof type === 'string' ||
-        typeof type === 'function' ||
-        (typeof type === 'object' && type !== null));
-}
-export const TouchableHighlight = defineComponent((_props, { slots, attrs: rawAttrs, emit }) => {
-    // `shown` is NOT `pressed`: RN holds the underlay for delayPressOut past the tap so a fast tap
-    // still flashes, and the pressed flag is already false by then.
-    const shown = ref(false);
-    // The mutable underlay cell (the in-flight hide canceller). A plain setup-scope object, never
-    // a ref: the machine mutates it on every event and nothing reads it reactively.
-    const runtime = createHighlightUnderlayRuntime();
-    // The press callbacks are declared emits, so Vue has stripped their onX listeners from $attrs.
-    // RN's _hasPressHandler gate therefore reads what the PARENT actually passed, off the
-    // instance's own vnode props — the same shape FlatList/VirtualizedList use for this.
-    const instance = getCurrentInstance();
-    const listener = (onName) => {
-        const vnodeProps = instance?.vnode.props;
-        return vnodeProps == null ? undefined : vnodeProps[onName];
-    };
-    return () => {
-        const attrs = normalizeVueAttrs(rawAttrs);
-        const hasPressHandler = hasTouchablePressHandler({
-            onPress: listener('onPress'),
-            onPressIn: listener('onPressIn'),
-            onPressOut: listener('onPressOut'),
-            onLongPress: listener('onLongPress'),
-        });
-        // Rebuilt each render over live attrs; the runtime persists, so an in-flight hide timer
-        // survives a rebuild.
-        const underlay = createHighlightUnderlayHandlers({
-            delayPressOut: numberOr(attrs.delayPressOut, 0),
-            hasPressHandler,
-            schedule: scheduleTimeout,
-        }, runtime, {
-            setShown: next => {
-                shown.value = next;
-            },
-            onShowUnderlay: () => emit('showUnderlay'),
-            onHideUnderlay: () => emit('hideUnderlay'),
-        });
-        const extra = resolveHighlightExtraStyles({
-            shown: shown.value,
-            hasPressHandler,
-            underlayColor: typeof attrs.underlayColor === 'string'
-                ? attrs.underlayColor
-                : undefined,
-            activeOpacity: typeof attrs.activeOpacity === 'number'
-                ? attrs.activeOpacity
-                : undefined,
-        });
-        const children = slots.default !== undefined ? slots.default() : [];
-        // RN's _createExtraStyles split: the backgroundColor on the CONTAINER, the lowered opacity
-        // on the CHILD (TouchableHighlight.js clones its single child). Vue can reach the child
-        // without a wrapper node — cloneVNode merges the style onto exactly one existing vnode, so
-        // nothing is inserted into the flex chain. It needs RN's own single-element-child shape
-        // though (React.Children.only): a fragment, a raw text node or several roots have no one
-        // child to clone, and there both styles fold onto the container — the pre-audit
-        // approximation, where the opacity fades the very underlay it should reveal.
-        const onlyChild = children.length === 1 && children[0] !== undefined
-            ? children[0]
-            : undefined;
-        const canStyleChild = onlyChild !== undefined && isStylableVNode(onlyChild);
-        const styledChildren = extra !== undefined && canStyleChild && onlyChild !== undefined
-            ? [cloneVNode(onlyChild, { style: extra.child })]
-            : children;
-        const containerStyle = extra === undefined
-            ? attrs.style
-            : canStyleChild
-                ? [attrs.style, extra.underlay]
-                : [attrs.style, extra.underlay, extra.child];
-        const pressableProps = {
-            __minPressDuration: 0,
-            ...forwardExcept(attrs, TOUCHABLE_HIGHLIGHT_HANDLED),
-            ...emitPressableEvents(emit),
-            style: containerStyle,
-            // Visual first, then the caller's callback — RN's order in _createPressabilityConfig.
-            onPress: (event) => {
-                underlay.handlePress(event);
-                emit('press', event);
-            },
-            onPressIn: (event) => {
-                underlay.handlePressIn(event);
-                emit('pressIn', event);
-            },
-            onPressOut: (event) => {
-                underlay.handlePressOut(event);
-                emit('pressOut', event);
-            },
-        };
-        return h(Pressable, pressableProps, { default: () => styledChildren });
-    };
-}, {
-    name: 'TouchableHighlight',
-    inheritAttrs: false,
-    emits: TOUCHABLE_HIGHLIGHT_EMITS,
-});
-// RN's TouchableWithoutFeedback builds a FULL Pressability config — "without feedback" means no
-// VISUAL, not no timing — so the delay props are consumed by the shared machine here instead of
-// forwarding to the host as unknown Fabric props.
-const TOUCHABLE_WITHOUT_FEEDBACK_HANDLED = [
-    'delayPressIn',
-    'delayPressOut',
-    'minPressDuration',
-];
-export const TouchableWithoutFeedback = defineComponent((_props, { slots, attrs: rawAttrs, emit }) => {
-    const runtime = createTouchableFeedbackRuntime();
-    return () => {
-        const attrs = normalizeVueAttrs(rawAttrs);
-        // The same machine TouchableOpacity runs, with the visual half left empty.
-        const { handlePressIn, handlePressOut } = createTouchableFeedbackHandlers({
-            delayPressIn: numberOr(attrs.delayPressIn, 0),
-            delayPressOut: numberOr(attrs.delayPressOut, 0),
-            minPressDuration: numberOr(attrs.minPressDuration, TOUCHABLE_MIN_PRESS_DURATION_MS),
-            schedule: scheduleTimeout,
-            now: Date.now,
-        }, runtime, {
-            activate(event) {
-                emit('pressIn', event);
-            },
-            deactivate(event) {
-                emit('pressOut', event);
-            },
-        });
-        const pressableProps = {
-            __minPressDuration: 0,
-            ...forwardExcept(attrs, TOUCHABLE_WITHOUT_FEEDBACK_HANDLED),
-            ...emitPressableEvents(emit),
-            onPressIn: handlePressIn,
-            onPressOut: handlePressOut,
-        };
-        const children = slots.default !== undefined ? slots.default() : [];
-        return h(Pressable, pressableProps, { default: () => children });
-    };
-}, {
-    name: 'TouchableWithoutFeedback',
-    inheritAttrs: false,
-    emits: PRESSABLE_EMITS,
-});

package/build/components.d.ts

@@ -1,53 +0,0 @@
-import { type FunctionalComponent, type VNodeRef } from '@vue/runtime-core';
-import type { ISymbioteEvent, IClassNameValue, IStyleProp, ITextStyle, IViewStyle } from '@symbiote-native/engine';
-import type { IAccessibilityProps, IAriaProps, IResponderProps } from '@symbiote-native/components';
-export interface IViewProps extends IAccessibilityProps, IAriaProps, IResponderProps {
-    style?: IStyleProp<IViewStyle>;
-    class?: IClassNameValue;
-    onPress?: (event: ISymbioteEvent) => void;
-    onPressIn?: (event: ISymbioteEvent) => void;
-    onPressOut?: (event: ISymbioteEvent) => void;
-    onLayout?: (event: ISymbioteEvent) => void;
-    onFocus?: (event: ISymbioteEvent) => void;
-    onBlur?: (event: ISymbioteEvent) => void;
-    pointerEvents?: 'auto' | 'none' | 'box-none' | 'box-only';
-    hitSlop?: number | {
-        top?: number;
-        left?: number;
-        bottom?: number;
-        right?: number;
-    };
-    id?: string;
-    focusable?: boolean;
-    collapsable?: boolean;
-    removeClippedSubviews?: boolean;
-    renderToHardwareTextureAndroid?: boolean;
-    shouldRasterizeIOS?: boolean;
-    needsOffscreenAlphaCompositing?: boolean;
-    ref?: VNodeRef;
-    key?: string | number | symbol;
-}
-export interface ITextProps extends IAccessibilityProps, IAriaProps {
-    style?: IStyleProp<ITextStyle>;
-    class?: IClassNameValue;
-    onPress?: (event: ISymbioteEvent) => void;
-    onLongPress?: (event: ISymbioteEvent) => void;
-    onPressIn?: (event: ISymbioteEvent) => void;
-    onPressOut?: (event: ISymbioteEvent) => void;
-    onLayout?: (event: ISymbioteEvent) => void;
-    onTextLayout?: (event: ISymbioteEvent) => void;
-    numberOfLines?: number;
-    ellipsizeMode?: 'head' | 'middle' | 'tail' | 'clip';
-    selectable?: boolean;
-    adjustsFontSizeToFit?: boolean;
-    minimumFontScale?: number;
-    allowFontScaling?: boolean;
-    maxFontSizeMultiplier?: number | null;
-    selectionColor?: string;
-    ref?: VNodeRef;
-    key?: string | number | symbol;
-}
-export declare const HOST_VIEW = "symbiote-view";
-export declare const HOST_TEXT = "symbiote-text";
-export declare const View: FunctionalComponent<IViewProps, {}, any, {}>;
-export declare const Text: FunctionalComponent<ITextProps, {}, any, {}>;

package/build/components.js

@@ -1,45 +0,0 @@
-// Host primitives for app code. Thin FUNCTIONAL components over the intrinsic tags the
-// renderer maps to Fabric: `inheritAttrs: false` + a manual attr spread passes every
-// prop and `@event` (onX) straight through to patchProp -> routeProp. The full prop
-// surface (typed ViewProps/TextProps, a11y folding) arrives with @symbiote-native/components.
-//
-// FUNCTIONAL, not a stateful defineComponent: a functional component has no instance, so
-// a template/function ref on it falls through to its single root host element (the raw
-// SymbioteNode), exactly like React's functional View hands back its host instance. A
-// stateful component's ref would resolve to a useless component proxy, which is why
-// createAnimatedComponent (which captures the host node via that ref) needs the fall-through.
-import { h } from '@vue/runtime-core';
-import { resolveTextProps } from '@symbiote-native/components';
-import { normalizeVueAttrs } from './utils/normalize-attrs.js';
-function hostComponent(intrinsic, name, 
-// An optional last fold over the normalized attrs. Text needs one (RN's ellipsizeMode /
-// allowFontScaling defaults); View does not, so it stays a straight pass-through.
-fold = attrs => attrs) {
-    // normalizeVueAttrs folds kebab template props (:accessibility-label) to the RN camelCase contract.
-    const component = (_props, { slots, attrs }) => h(intrinsic, fold(normalizeVueAttrs(attrs)), slots.default !== undefined ? slots.default() : undefined);
-    component.displayName = name;
-    component.inheritAttrs = false;
-    return component;
-}
-// The intrinsic tags the two bare primitives wrap. Exported because ADAPTER-INTERNAL renders must
-// use the TAG, never the component: Vue charges a full component instance even for a functional
-// one, so `h(View, …)` inside our own Pressable/Button costs an instance per node for a wrapper
-// that only forwards attrs.
-//
-// These stay LITERALS rather than being read out of `@symbiote-native/components/host-primitives`,
-// which is where the two transforms now get them: the spec types `intrinsic` as `string`, and
-// reading it here would widen `HOST_VIEW` from the literal type that `hostComponent` and every
-// adapter-internal `h(HOST_VIEW, …)` rely on. So this is the last remaining second encoding, and
-// `components.test.ts` pins it against the spec rather than trusting the two to stay in step.
-//
-// Children go to a tag as an ARRAY (or a bare string / vnode), never a slot function — an element
-// ignores slot children entirely and renders nothing. The reverse of the rule that applies to a
-// component.
-export const HOST_VIEW = 'symbiote-view';
-export const HOST_TEXT = 'symbiote-text';
-export const View = hostComponent(HOST_VIEW, 'View');
-export const Text = hostComponent(HOST_TEXT, 'Text', resolveTextProps);
-// Text is no longer bare either — it carries RN's Text.js defaults through resolveTextProps.
-// Image is NOT a bare host primitive: it needs the shared fold (source/src/srcSet resolution,
-// width/height -> style, alt -> accessibility) + the Image statics, so it lives in ./image as a
-// functional component over renderImage. View/Text stay bare; they forward attrs verbatim.

package/build/composables/use-raw-attrs.d.ts

@@ -1 +0,0 @@
-export declare function useRawAttrs(contextAttrs: Record<string, unknown>): Record<string, unknown>;

package/build/composables/use-raw-attrs.js

@@ -1,26 +0,0 @@
-// The unproxied twin of a setup context's `attrs`.
-//
-// Vue hands `setupContext.attrs` out as `new Proxy(instance.attrs, attrsProxyHandlers)`, and in
-// PRODUCTION as well as dev that proxy's only trap is `get(target, key) { track(target, "get", "");
-// return target[key]; }` (runtime-core.esm-bundler.js:8357). So every attribute read costs a
-// WeakMap get, a Map get and a `dep.track()`, and the first read of each instance also allocates
-// a Map and a Dep into the module-global `targetMap` that live as long as the component does.
-// Pressable reads ~16 attrs per render and a benchmark create mounts 2 000 of them.
-//
-// `instance.attrs` is the raw object behind that proxy. Capturing it is safe because its identity
-// never changes: `initProps` assigns it once (:4907) and `updateProps` mutates that same object in
-// place (`attrs[key] = value` / `delete attrs[key]`), so a reference taken at setup always reads
-// current values. The tracking the proxy performs is for reads in a setup BODY; a render fn does
-// not need it, because the parent's patch re-runs the child render through `updateComponentPreRender`
-// whether or not the child subscribed.
-//
-// CALL THIS FROM A SETUP BODY ONLY, never from a render fn, a `computed`, or any other deferred
-// callback. `getCurrentInstance()` resolves to `currentInstance || currentRenderingInstance`, so in
-// a callback that runs while a DIFFERENT component is rendering it returns that component and this
-// would silently hand back the wrong bag. `virtualized-list/index.ts` calls normalizeVueAttrs
-// inside a `computed` for exactly that reason and must keep using the context attrs.
-import { getCurrentInstance } from '@vue/runtime-core';
-export function useRawAttrs(contextAttrs) {
-    const instance = getCurrentInstance();
-    return instance === null ? contextAttrs : instance.attrs;
-}

package/build/state-style.d.ts

@@ -1 +0,0 @@
-export { resolveStateStyle, type IPressStateArgument, type IResolvedStateStyle, } from '@symbiote-native/components/state-style';

package/build/state-style.js

@@ -1,13 +0,0 @@
-// Re-export only. The implementation is shared (`@symbiote-native/components`) because two adapters
-// had written byte-identical copies; this file exists so the code a transform EMITS keeps importing
-// from the adapter package the app already depends on, rather than reaching past it.
-//
-// Imported from the SUBPATH, not the barrel: every adapter barrel re-exports
-// `@symbiote-native/components` wholesale, so a name on that barrel silently becomes public API on
-// all five — which is how a transform internal nearly shipped as a supported export.
-//
-// Present on every adapter, including those with no lowering transform yet: a per-framework subpath
-// that four of five declare is exactly the silent gap `tests/package-subpath-parity.test.ts` exists
-// to catch, and the file costs a re-export. Deliberately NOT on the public barrel — the emitted
-// code names it, app code does not.
-export { resolveStateStyle, } from '@symbiote-native/components/state-style';