@xaui/native 0.9.1-alpha.13 → 0.9.1-alpha.15

package/dist/system/index.d.ts

@@ -1,12 +1,44 @@
 import * as react from 'react';
-import { ReactNode, Ref, Provider, RefCallback } from 'react';
-import { b as IconProps, a as IconContextValue, S as SlotAnimation, F as FeedbackContext, c as AnimationProp, d as ResolvedAnimation } from '../create-recipe-3OPwcC6P.js';
-export { A as AnimationConfig, i as Axes, C as CompoundVariant, D as DirectionalStyleKey, I as IconComponentProps, u as ImageStyleProps, P as PressableFeedbackProps, R as RadiusStyle, g as Recipe, j as RecipeConfig, h as ResolveArgs, k as ResolvedSelection, l as ResolvedStyles, e as RippleWave, m as Selection, n as SlotStyle, o as SlotStyles, p as StateName, q as States, r as StyleFn, v as StyleProps, w as TextStyleProps, T as TintArgs, V as VariantColors, s as VariantRole, t as VariantTokens, x as ViewStyleProps, f as createRecipe } from '../create-recipe-3OPwcC6P.js';
+import { ReactNode, Provider, Ref, RefCallback } from 'react';
+import { b as IconProps, a as IconContextValue, x as ViewStyleProps, S as SlotAnimation, F as FeedbackContext, c as AnimationProp, d as ResolvedAnimation } from '../create-recipe-DD9W6m9b.js';
+export { A as AnimationConfig, i as Axes, C as CompoundVariant, D as DirectionalStyleKey, I as IconComponentProps, u as ImageStyleProps, P as PressableFeedbackProps, R as RadiusStyle, g as Recipe, j as RecipeConfig, h as ResolveArgs, k as ResolvedSelection, l as ResolvedStyles, e as RippleWave, m as Selection, n as SlotStyle, o as SlotStyles, p as StateName, q as States, r as StyleFn, v as StyleProps, w as TextStyleProps, T as TintArgs, V as VariantColors, s as VariantRole, t as VariantTokens, f as createRecipe } from '../create-recipe-DD9W6m9b.js';
 import * as react_native from 'react-native';
 import { StyleProp, ViewStyle } from 'react-native';
 import 'react-native-reanimated';
 import '../theme.type-C9bFJKFm.js';
 
+/**
+ * The runtime half of R14. The type half lives in `system/style-props/`, and the two are
+ * pinned to each other by a compile-time check there: a React Native upgrade that adds or
+ * removes a style key fails `type-check` with the key's name rather than drifting.
+ *
+ * One set for the three style types rather than one per node. A caller cannot write
+ * `fontSize` on a view slot — that slot's props are typed `ViewStyleProps` — so the split
+ * never has to know which node it runs for, and every component shares one table.
+ */
+declare const STYLE_PROP_KEYS: readonly ["alignContent", "alignItems", "alignSelf", "aspectRatio", "boxSizing", "columnGap", "direction", "display", "flex", "flexBasis", "flexDirection", "flexGrow", "flexShrink", "flexWrap", "gap", "justifyContent", "overflow", "rowGap", "bottom", "end", "inset", "insetBlock", "insetBlockEnd", "insetBlockStart", "insetInline", "insetInlineEnd", "insetInlineStart", "position", "start", "top", "zIndex", "margin", "marginBlock", "marginBlockEnd", "marginBlockStart", "marginBottom", "marginEnd", "marginHorizontal", "marginInline", "marginInlineEnd", "marginInlineStart", "marginStart", "marginTop", "marginVertical", "padding", "paddingBlock", "paddingBlockEnd", "paddingBlockStart", "paddingBottom", "paddingEnd", "paddingHorizontal", "paddingInline", "paddingInlineEnd", "paddingInlineStart", "paddingStart", "paddingTop", "paddingVertical", "height", "maxHeight", "maxWidth", "minHeight", "minWidth", "width", "borderBlockColor", "borderBlockEndColor", "borderBlockStartColor", "borderBottomColor", "borderBottomEndRadius", "borderBottomStartRadius", "borderBottomWidth", "borderColor", "borderCurve", "borderEndColor", "borderEndEndRadius", "borderEndStartRadius", "borderEndWidth", "borderRadius", "borderStartColor", "borderStartEndRadius", "borderStartStartRadius", "borderStartWidth", "borderStyle", "borderTopColor", "borderTopEndRadius", "borderTopStartRadius", "borderTopWidth", "borderWidth", "backfaceVisibility", "backgroundColor", "boxShadow", "cursor", "elevation", "experimental_backgroundImage", "filter", "isolation", "mixBlendMode", "opacity", "outlineColor", "outlineOffset", "outlineStyle", "outlineWidth", "shadowColor", "shadowOffset", "shadowOpacity", "shadowRadius", "rotation", "scaleX", "scaleY", "transform", "transformMatrix", "transformOrigin", "translateX", "translateY", "color", "fontFamily", "fontSize", "fontStyle", "fontVariant", "fontWeight", "includeFontPadding", "letterSpacing", "lineHeight", "textAlign", "textAlignVertical", "textDecorationColor", "textDecorationLine", "textDecorationStyle", "textShadowColor", "textShadowOffset", "textShadowRadius", "textTransform", "userSelect", "verticalAlign", "writingDirection", "objectFit", "overlayColor", "resizeMode", "tintColor"];
+type StylePropKey = (typeof STYLE_PROP_KEYS)[number];
+/** What `splitStyleProps` takes out of a props object. */
+type StylePropsOf<P> = Pick<P, Extract<keyof P, StylePropKey>>;
+/** What it leaves in it. */
+type RestPropsOf<P> = Omit<P, StylePropKey>;
+
+/**
+ * `splitStyleProps`, memoized on the values (R14). A component calls it on what is left
+ * after destructuring its own props, applies the style half between the tint and its
+ * `style`, and forwards the rest:
+ *
+ * ```tsx
+ * const [styleProps, rest] = useStyleProps(props)
+ * <Pressable style={[styles.root, tint, styleProps, style]} {...rest} />
+ * ```
+ *
+ * The identity is stable while the values are, which is what a memoized child or an
+ * animated style depends on. It is keyed on a hash rather than on the object, because the
+ * object is a fresh rest-spread on every render and would never hit.
+ */
+declare function useStyleProps<P extends object>(props: P): [StylePropsOf<P>, RestPropsOf<P>];
+
 /**
  * The gap nobody else closes: an icon is a third-party component, so a slot context does
  * not reach it and every call site ends up computing the colour by hand.
@@ -22,7 +54,7 @@ import '../theme.type-C9bFJKFm.js';
  * through `source` — and the resolution is the same for all three: an explicit prop, else
  * what the surrounding slot published, else the theme.
  */
-declare function Icon({ as: Component, children, source, size, color, style, }: IconProps): react.JSX.Element;
+declare function Icon({ as: Component, children, source, size, color, style, ...props }: IconProps): react.JSX.Element;
 declare namespace Icon {
     var displayName: string;
 }
@@ -35,7 +67,139 @@ declare namespace Icon {
 declare const IconContext: react.Context<IconContextValue>;
 declare function useIconContext(): IconContextValue;
 
-type PressableFeedbackHighlightProps = {
+type PortalProps = {
+    children: ReactNode;
+};
+/**
+ * Renders its children into the nearest `PortalHost` instead of where it sits. What
+ * `Dialog`, `Sheet`, `Drawer` and `Snackbar` are built on: an overlay has to escape the
+ * clipping and stacking of whatever container happened to hold the trigger.
+ *
+ * Both halves run in layout effects rather than effects, which is deliberate: the content
+ * lands in the same commit as the trigger's, so an overlay neither shows one frame late
+ * nor survives one frame past the unmount that closed it. The unpublish sits in its own
+ * effect so that it does not depend on `children` — a re-publish then keeps the portal's
+ * place in the host's order instead of dropping it and re-adding it at the end.
+ */
+declare function Portal({ children }: PortalProps): null;
+declare namespace Portal {
+    var displayName: string;
+}
+
+type PortalMethods = {
+    addPortal: (key: string, element: ReactNode) => void;
+    removePortal: (key: string) => void;
+};
+/**
+ * `null` outside a host, and `Portal` treats that as "render nothing" rather than
+ * throwing: an app that forgot `PortalHost` should lose its overlays, not crash on the
+ * first `Dialog`.
+ */
+declare const PortalContext: react.Context<PortalMethods | null>;
+
+/** R14 — it renders a view of its own, so it takes that view's style keys as props. */
+type PortalHostProps = ViewStyleProps & {
+    children: ReactNode;
+};
+/**
+ * Where every `Portal` in the tree below renders. Mounted once, at the root of the app,
+ * above navigation — an overlay that renders inside a screen is clipped by it.
+ */
+declare function PortalHost({ children, ...props }: PortalHostProps): react.JSX.Element;
+declare namespace PortalHost {
+    var displayName: string;
+}
+
+/**
+ * R3: the string a root should wrap in its default text slot, or `null` when it should
+ * render its children as they are.
+ *
+ * The whole tree is stringified recursively rather than the first child inspected. That
+ * is what makes `<Button>{count} items</Button>` work — children there are the array
+ * `[3, ' items']`, and an `isValidElement` check on the first entry would call it an
+ * element-free tree only by accident, while a check for "is the first child a string"
+ * would miss it outright.
+ *
+ * `null` for an empty result as much as for a tree containing an element: in both cases
+ * there is nothing to wrap, and a root's fallback — render the children — is right for
+ * both. It also keeps `<Button>{false}</Button>` from mounting an empty text node.
+ */
+declare function childrenToString(children: ReactNode): string | null;
+
+/**
+ * A context a slot cannot read by accident. Every compound gets one, and it carries
+ * **resolved** values — style references the root already computed, not tokens for the
+ * slot to resolve again (R5).
+ *
+ * ```ts
+ * const [ButtonProvider, useButton] = createSlotContext<ButtonContext>('Button')
+ * ```
+ *
+ * The tuple is what lets each compound name its own hook, which R10 requires it to
+ * export. `name` gives both halves of the error, so there is one place to spell it.
+ */
+declare function createSlotContext<T>(name: string): readonly [Provider<T | null>, () => T];
+
+/** Anything React accepts as a ref, plus the absence of one. */
+type PossibleRef<T> = Ref<T> | undefined;
+/**
+ * The props `mergeProps` knows how to combine. Deliberately loose: it merges whatever a
+ * root hands to whatever child it was given, and neither side is knowable from here.
+ */
+type MergeableProps = Record<string, unknown>;
+type AsChildProps = {
+    /**
+     * Merge this component's props into its single child instead of rendering an element
+     * of its own — a navigation `Link` as a `Button`, a bespoke trigger as a `Select`.
+     */
+    asChild?: boolean;
+};
+
+/**
+ * Merges a root's own props into the child it renders through `asChild` (R12). Four
+ * rules, and the child wins wherever they do not apply — it is the more specific intent:
+ *
+ * - **Event handlers compose.** Both run, ours first: the component's own behaviour (the
+ *   press state that drives its styles) happens before the child's side effect (the
+ *   navigation). Replacing one with the other is the bug this exists to prevent.
+ * - **Styles stack**, ours under the child's, so the child can override.
+ * - **`ref`s merge** through `mergeRefs`. React 19 passes `ref` as an ordinary prop, so
+ *   it arrives here rather than beside the props, and dropping it would sever the root's
+ *   handle on the node.
+ * - **Everything else: the child's value wins**, and ours fills in what it left unset.
+ */
+declare function mergeProps(ours: MergeableProps, theirs: MergeableProps): MergeableProps;
+
+/**
+ * One callback that feeds several refs — what lets a root keep its own handle on a node
+ * while still honouring the ref its caller passed (R9), and what `asChild` needs to
+ * forward a ref into the child it merges into (R12).
+ *
+ * It returns nothing on purpose. React 19 reads a ref callback's return value as a
+ * cleanup function while React 18 ignores it, and this package supports both; letting
+ * a merged cleanup through would behave differently on each. React calls every ref with
+ * `null` on unmount anyway, which this forwards.
+ */
+declare function mergeRefs<T>(...refs: Array<PossibleRef<T>>): RefCallback<T>;
+
+type SlotProps = MergeableProps & {
+    children?: ReactNode;
+};
+/**
+ * The render branch behind `asChild` (R12). A root picks it instead of its own element:
+ *
+ * ```tsx
+ * const Root = asChild ? Slot : Pressable
+ * return <Root ref={ref} {...rootProps}>{children}</Root>
+ * ```
+ *
+ * One line per root, which is the point — forty-seven roots each hand-rolling a
+ * `cloneElement` and a ref merge would drift, and R12 has to hold uniformly from the
+ * first component or the ref signature of the whole core changes later.
+ */
+declare const Slot: react.ForwardRefExoticComponent<Omit<SlotProps, "ref"> & react.RefAttributes<unknown>>;
+
+type PressableFeedbackHighlightProps = ViewStyleProps & {
     style?: StyleProp<ViewStyle>;
     animation?: SlotAnimation;
     /**
@@ -69,12 +233,12 @@ type PressableFeedbackHighlightProps = {
  * have made the root's layout apply to the wrapper instead, and would have added the depth
  * §8 removed.
  */
-declare function PressableFeedbackHighlight({ style, animation: override, children, }: PressableFeedbackHighlightProps): react.JSX.Element;
+declare function PressableFeedbackHighlight({ style, animation: override, children, ...props }: PressableFeedbackHighlightProps): react.JSX.Element;
 declare namespace PressableFeedbackHighlight {
     var displayName: string;
 }
 
-type PressableFeedbackRippleProps = {
+type PressableFeedbackRippleProps = ViewStyleProps & {
     /** Applies to the wave itself, not to the container that clips it. */
     style?: StyleProp<ViewStyle>;
     animation?: SlotAnimation;
@@ -118,7 +282,7 @@ type PressableFeedbackRippleProps = {
  * target rather than at a point, the target is **half the diagonal**, and the centre
  * **travels** from the finger to the middle of the control. The constants carry the why.
  */
-declare function PressableFeedbackRipple({ style, animation: override, children, }: PressableFeedbackRippleProps): react.JSX.Element;
+declare function PressableFeedbackRipple({ style, animation: override, children, ...props }: PressableFeedbackRippleProps): react.JSX.Element;
 declare namespace PressableFeedbackRipple {
     var displayName: string;
 }
@@ -212,7 +376,7 @@ declare function resolveSlotAnimation(override: SlotAnimation | undefined, enabl
  * off — and it is the only shape that survives `asChild`, where the caller's own element
  * is the pressable and there is no sibling for the primitive to inject.
  */
-declare const PressableFeedback: react.ForwardRefExoticComponent<Omit<react_native.PressableProps, "children" | "style" | "disabled"> & {
+declare const PressableFeedback: react.ForwardRefExoticComponent<Omit<react_native.PressableProps, "children" | "style" | "disabled"> & ViewStyleProps & {
     isPressed?: boolean;
     isDisabled?: boolean;
     asChild?: boolean;
@@ -224,167 +388,4 @@ declare const PressableFeedback: react.ForwardRefExoticComponent<Omit<react_nati
     Ripple: typeof PressableFeedbackRipple;
 };
 
-/**
- * The runtime half of R14. The type half lives in `system/style-props/`, and the two are
- * pinned to each other by a compile-time check there: a React Native upgrade that adds or
- * removes a style key fails `type-check` with the key's name rather than drifting.
- *
- * One set for the three style types rather than one per node. A caller cannot write
- * `fontSize` on a view slot — that slot's props are typed `ViewStyleProps` — so the split
- * never has to know which node it runs for, and every component shares one table.
- */
-declare const STYLE_PROP_KEYS: readonly ["alignContent", "alignItems", "alignSelf", "aspectRatio", "boxSizing", "columnGap", "direction", "display", "flex", "flexBasis", "flexDirection", "flexGrow", "flexShrink", "flexWrap", "gap", "justifyContent", "overflow", "rowGap", "bottom", "end", "inset", "insetBlock", "insetBlockEnd", "insetBlockStart", "insetInline", "insetInlineEnd", "insetInlineStart", "position", "start", "top", "zIndex", "margin", "marginBlock", "marginBlockEnd", "marginBlockStart", "marginBottom", "marginEnd", "marginHorizontal", "marginInline", "marginInlineEnd", "marginInlineStart", "marginStart", "marginTop", "marginVertical", "padding", "paddingBlock", "paddingBlockEnd", "paddingBlockStart", "paddingBottom", "paddingEnd", "paddingHorizontal", "paddingInline", "paddingInlineEnd", "paddingInlineStart", "paddingStart", "paddingTop", "paddingVertical", "height", "maxHeight", "maxWidth", "minHeight", "minWidth", "width", "borderBlockColor", "borderBlockEndColor", "borderBlockStartColor", "borderBottomColor", "borderBottomEndRadius", "borderBottomStartRadius", "borderBottomWidth", "borderColor", "borderCurve", "borderEndColor", "borderEndEndRadius", "borderEndStartRadius", "borderEndWidth", "borderRadius", "borderStartColor", "borderStartEndRadius", "borderStartStartRadius", "borderStartWidth", "borderStyle", "borderTopColor", "borderTopEndRadius", "borderTopStartRadius", "borderTopWidth", "borderWidth", "backfaceVisibility", "backgroundColor", "boxShadow", "cursor", "elevation", "experimental_backgroundImage", "filter", "isolation", "mixBlendMode", "opacity", "outlineColor", "outlineOffset", "outlineStyle", "outlineWidth", "shadowColor", "shadowOffset", "shadowOpacity", "shadowRadius", "rotation", "scaleX", "scaleY", "transform", "transformMatrix", "transformOrigin", "translateX", "translateY", "color", "fontFamily", "fontSize", "fontStyle", "fontVariant", "fontWeight", "includeFontPadding", "letterSpacing", "lineHeight", "textAlign", "textAlignVertical", "textDecorationColor", "textDecorationLine", "textDecorationStyle", "textShadowColor", "textShadowOffset", "textShadowRadius", "textTransform", "userSelect", "verticalAlign", "writingDirection", "objectFit", "overlayColor", "resizeMode", "tintColor"];
-type StylePropKey = (typeof STYLE_PROP_KEYS)[number];
-/** What `splitStyleProps` takes out of a props object. */
-type StylePropsOf<P> = Pick<P, Extract<keyof P, StylePropKey>>;
-/** What it leaves in it. */
-type RestPropsOf<P> = Omit<P, StylePropKey>;
-
-/**
- * `splitStyleProps`, memoized on the values (R14). A component calls it on what is left
- * after destructuring its own props, applies the style half between the tint and its
- * `style`, and forwards the rest:
- *
- * ```tsx
- * const [styleProps, rest] = useStyleProps(props)
- * <Pressable style={[styles.root, tint, styleProps, style]} {...rest} />
- * ```
- *
- * The identity is stable while the values are, which is what a memoized child or an
- * animated style depends on. It is keyed on a hash rather than on the object, because the
- * object is a fresh rest-spread on every render and would never hit.
- */
-declare function useStyleProps<P extends object>(props: P): [StylePropsOf<P>, RestPropsOf<P>];
-
-/** Anything React accepts as a ref, plus the absence of one. */
-type PossibleRef<T> = Ref<T> | undefined;
-/**
- * The props `mergeProps` knows how to combine. Deliberately loose: it merges whatever a
- * root hands to whatever child it was given, and neither side is knowable from here.
- */
-type MergeableProps = Record<string, unknown>;
-type AsChildProps = {
-    /**
-     * Merge this component's props into its single child instead of rendering an element
-     * of its own — a navigation `Link` as a `Button`, a bespoke trigger as a `Select`.
-     */
-    asChild?: boolean;
-};
-
-type PortalProps = {
-    children: ReactNode;
-};
-/**
- * Renders its children into the nearest `PortalHost` instead of where it sits. What
- * `Dialog`, `Sheet`, `Drawer` and `Snackbar` are built on: an overlay has to escape the
- * clipping and stacking of whatever container happened to hold the trigger.
- *
- * Both halves run in layout effects rather than effects, which is deliberate: the content
- * lands in the same commit as the trigger's, so an overlay neither shows one frame late
- * nor survives one frame past the unmount that closed it. The unpublish sits in its own
- * effect so that it does not depend on `children` — a re-publish then keeps the portal's
- * place in the host's order instead of dropping it and re-adding it at the end.
- */
-declare function Portal({ children }: PortalProps): null;
-declare namespace Portal {
-    var displayName: string;
-}
-
-type PortalMethods = {
-    addPortal: (key: string, element: ReactNode) => void;
-    removePortal: (key: string) => void;
-};
-/**
- * `null` outside a host, and `Portal` treats that as "render nothing" rather than
- * throwing: an app that forgot `PortalHost` should lose its overlays, not crash on the
- * first `Dialog`.
- */
-declare const PortalContext: react.Context<PortalMethods | null>;
-
-type PortalHostProps = {
-    children: ReactNode;
-};
-/**
- * Where every `Portal` in the tree below renders. Mounted once, at the root of the app,
- * above navigation — an overlay that renders inside a screen is clipped by it.
- */
-declare function PortalHost({ children }: PortalHostProps): react.JSX.Element;
-declare namespace PortalHost {
-    var displayName: string;
-}
-
-/**
- * R3: the string a root should wrap in its default text slot, or `null` when it should
- * render its children as they are.
- *
- * The whole tree is stringified recursively rather than the first child inspected. That
- * is what makes `<Button>{count} items</Button>` work — children there are the array
- * `[3, ' items']`, and an `isValidElement` check on the first entry would call it an
- * element-free tree only by accident, while a check for "is the first child a string"
- * would miss it outright.
- *
- * `null` for an empty result as much as for a tree containing an element: in both cases
- * there is nothing to wrap, and a root's fallback — render the children — is right for
- * both. It also keeps `<Button>{false}</Button>` from mounting an empty text node.
- */
-declare function childrenToString(children: ReactNode): string | null;
-
-/**
- * A context a slot cannot read by accident. Every compound gets one, and it carries
- * **resolved** values — style references the root already computed, not tokens for the
- * slot to resolve again (R5).
- *
- * ```ts
- * const [ButtonProvider, useButton] = createSlotContext<ButtonContext>('Button')
- * ```
- *
- * The tuple is what lets each compound name its own hook, which R10 requires it to
- * export. `name` gives both halves of the error, so there is one place to spell it.
- */
-declare function createSlotContext<T>(name: string): readonly [Provider<T | null>, () => T];
-
-/**
- * Merges a root's own props into the child it renders through `asChild` (R12). Four
- * rules, and the child wins wherever they do not apply — it is the more specific intent:
- *
- * - **Event handlers compose.** Both run, ours first: the component's own behaviour (the
- *   press state that drives its styles) happens before the child's side effect (the
- *   navigation). Replacing one with the other is the bug this exists to prevent.
- * - **Styles stack**, ours under the child's, so the child can override.
- * - **`ref`s merge** through `mergeRefs`. React 19 passes `ref` as an ordinary prop, so
- *   it arrives here rather than beside the props, and dropping it would sever the root's
- *   handle on the node.
- * - **Everything else: the child's value wins**, and ours fills in what it left unset.
- */
-declare function mergeProps(ours: MergeableProps, theirs: MergeableProps): MergeableProps;
-
-/**
- * One callback that feeds several refs — what lets a root keep its own handle on a node
- * while still honouring the ref its caller passed (R9), and what `asChild` needs to
- * forward a ref into the child it merges into (R12).
- *
- * It returns nothing on purpose. React 19 reads a ref callback's return value as a
- * cleanup function while React 18 ignores it, and this package supports both; letting
- * a merged cleanup through would behave differently on each. React calls every ref with
- * `null` on unmount anyway, which this forwards.
- */
-declare function mergeRefs<T>(...refs: Array<PossibleRef<T>>): RefCallback<T>;
-
-type SlotProps = MergeableProps & {
-    children?: ReactNode;
-};
-/**
- * The render branch behind `asChild` (R12). A root picks it instead of its own element:
- *
- * ```tsx
- * const Root = asChild ? Slot : Pressable
- * return <Root ref={ref} {...rootProps}>{children}</Root>
- * ```
- *
- * One line per root, which is the point — forty-seven roots each hand-rolling a
- * `cloneElement` and a ref merge would drift, and R12 has to hold uniformly from the
- * first component or the ref signature of the whole core changes later.
- */
-declare const Slot: react.ForwardRefExoticComponent<Omit<SlotProps, "ref"> & react.RefAttributes<unknown>>;
-
-export { AnimationProp, type AsChildProps, FEEDBACK_OVERLAY, FeedbackContext, HIGHLIGHT_DURATION, HIGHLIGHT_OPACITY, Icon, IconContext, IconContextValue, IconProps, type MergeableProps, PRESS_DURATION, PRESS_SCALE, Portal, PortalContext, PortalHost, type PortalHostProps, type PortalMethods, type PortalProps, type PossibleRef, PressableFeedback, type PressableFeedbackHighlightProps, type PressableFeedbackRippleProps, RIPPLE_CONFIRM_DURATION, RIPPLE_EXPAND_DURATION, RIPPLE_FADE_IN, RIPPLE_FADE_OUT, RIPPLE_FADE_OUT_DELAY, RIPPLE_OPACITY, RIPPLE_START_SCALE, ResolvedAnimation, SCALE_REFERENCE_WIDTH, Slot, SlotAnimation, type SlotProps, childrenToString, createSlotContext, markOverlay, mergeProps, mergeRefs, pressScaleFor, resolveAnimation, resolveSlotAnimation, rippleRadiusFor, useFeedback, useIconContext, useStyleProps };
+export { AnimationProp, type AsChildProps, FEEDBACK_OVERLAY, FeedbackContext, HIGHLIGHT_DURATION, HIGHLIGHT_OPACITY, Icon, IconContext, IconContextValue, IconProps, type MergeableProps, PRESS_DURATION, PRESS_SCALE, Portal, PortalContext, PortalHost, type PortalHostProps, type PortalMethods, type PortalProps, type PossibleRef, PressableFeedback, type PressableFeedbackHighlightProps, type PressableFeedbackRippleProps, RIPPLE_CONFIRM_DURATION, RIPPLE_EXPAND_DURATION, RIPPLE_FADE_IN, RIPPLE_FADE_OUT, RIPPLE_FADE_OUT_DELAY, RIPPLE_OPACITY, RIPPLE_START_SCALE, ResolvedAnimation, SCALE_REFERENCE_WIDTH, Slot, SlotAnimation, type SlotProps, ViewStyleProps, childrenToString, createSlotContext, markOverlay, mergeProps, mergeRefs, pressScaleFor, resolveAnimation, resolveSlotAnimation, rippleRadiusFor, useFeedback, useIconContext, useStyleProps };

package/dist/system/index.js

@@ -2,7 +2,7 @@ import {
   Portal,
   PortalContext,
   PortalHost
-} from "../chunk-TO6DAGFB.js";
+} from "../chunk-UOJBK5Z4.js";
 import {
   FEEDBACK_OVERLAY,
   HIGHLIGHT_DURATION,
@@ -34,7 +34,7 @@ import {
   useFeedback,
   useIconContext,
   useStyleProps
-} from "../chunk-B3EAZ2CC.js";
+} from "../chunk-64L44HEI.js";
 import "../chunk-XJARE6SC.js";
 export {
   FEEDBACK_OVERLAY,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xaui/native",
-  "version": "0.9.1-alpha.13",
+  "version": "0.9.1-alpha.15",
   "description": "Composition-first React Native UI components with native animations powered by Reanimated",
   "keywords": [
     "react-native",