@xaui/native 0.9.1-alpha.16 → 0.9.1-alpha.18

package/dist/create-recipe-BcUu9b2I.d.cts

@@ -1,280 +0,0 @@
-import { ComponentType, ReactNode } from 'react';
-import { ImageStyle, TextStyle, ViewStyle, ImageSourcePropType, StyleProp, PressableProps } from 'react-native';
-import { SharedValue } from 'react-native-reanimated';
-import { g as XAUITheme, X as XAUIColors } from './theme.type-C9bFJKFm.cjs';
-
-/**
- * R13 — React Native mirrors a layout under RTL through the Start/End properties and only
- * those. A props API is exactly where someone writes `paddingLeft` without thinking, so
- * the type removes the temptation instead of leaving it to a review.
- */
-type DirectionalStyleKey = 'left' | 'right' | 'paddingLeft' | 'paddingRight' | 'marginLeft' | 'marginRight' | 'borderLeftWidth' | 'borderRightWidth' | 'borderLeftColor' | 'borderRightColor' | 'borderTopLeftRadius' | 'borderTopRightRadius' | 'borderBottomLeftRadius' | 'borderBottomRightRadius';
-/**
- * `pointerEvents` is a style key *and* a `View` prop. R14 says the component's own prop
- * wins, so it stays the prop it has always been and is not exposed twice — the one name
- * where the two vocabularies collide.
- */
-type ComponentOwnedStyleKey = 'pointerEvents';
-/**
- * The style keys of a node, exposed as props (R14). Not a maintained list: it derives
- * from the React Native type, minus what R13 forbids.
- *
- * ```ts
- * type CardProps = ViewStyleProps & { variant?: CardVariant }
- * ```
- */
-type StyleProps<Style> = Omit<Style, DirectionalStyleKey | ComponentOwnedStyleKey>;
-/** A root, or any slot that renders a view. */
-type ViewStyleProps = StyleProps<ViewStyle>;
-/** A text slot — `color`, `fontSize`, `letterSpacing`… */
-type TextStyleProps = StyleProps<TextStyle>;
-/** An image slot — `resizeMode`, `tintColor`… */
-type ImageStyleProps = StyleProps<ImageStyle>;
-
-/**
- * The props Lucide, Ionicons and `react-native-vector-icons` all accept — the shape
- * `as` is handed. It is a convention rather than an interface anyone published, which is
- * exactly why `Icon` exists: without it every call site computes the two values by hand.
- */
-type IconComponentProps = {
-    size?: number;
-    color?: string;
-};
-/**
- * R14 reaches the **`source` form only**, exactly like `style` below and for the same
- * reason: it is the one of the three forms where we render the node. On the other two,
- * `size` and `color` are what shapes the icon.
- */
-type IconProps = ImageStyleProps & {
-    /** An icon component. `size` and `color` are injected into it. */
-    as?: ComponentType<IconComponentProps>;
-    /** A raw `react-native-svg` element, cloned with the resolved size and colour. */
-    children?: ReactNode;
-    /** An image, tinted with the resolved colour. */
-    source?: ImageSourcePropType;
-    /** Overrides what the surrounding slot asked for. */
-    size?: number;
-    /** A raw value (R7), never a token. Overrides the slot's. */
-    color?: string;
-    /**
-     * The **`source` form only** — it is the one of the three where we render the view.
-     * `as` hands its props to a third-party component and the children form clones an
-     * element the caller made; neither is a view this can style, and wrapping them would
-     * add a level of depth to every icon in the library. `size` and `color` are the
-     * escape hatch there.
-     */
-    style?: StyleProp<ImageStyle>;
-};
-/** What a component root publishes so the icons inside it need no props at all. */
-type IconContextValue = {
-    size?: number;
-    color?: string;
-};
-
-type AnimationConfig = {
-    scale?: boolean;
-    highlight?: boolean;
-    ripple?: boolean;
-};
-/**
- * `false` and `'disabled'` turn this component's animations off. `'disable-all'` turns
- * them off for its descendants too — a long list kills every row's worklets with one
- * prop instead of threading it down. An object switches them off one at a time.
- */
-type AnimationProp = boolean | 'disabled' | 'disable-all' | AnimationConfig;
-/** `animation` once normalised — what the components actually read. */
-type ResolvedAnimation = {
-    scale: boolean;
-    highlight: boolean;
-    ripple: boolean;
-    /** True when every sub-animation is off: the branch that mounts no worklet at all. */
-    none: boolean;
-    /** Propagated to descendants through context. */
-    disableAll: boolean;
-};
-/**
- * R14 — it renders a `Pressable`, so it takes that node's style keys as props. The
- * primitive every pressable component in the library is built on cannot be the one place
- * where `padding={16}` has to become an object again.
- */
-type PressableFeedbackProps = Omit<PressableProps, 'style' | 'children' | 'disabled'> & ViewStyleProps & {
-    /** Controlled: the root owns the state, because its recipe resolves on it (R5). */
-    isPressed?: boolean;
-    /** R8: `disabled` is not part of the public vocabulary, `isX` is. */
-    isDisabled?: boolean;
-    /**
-     * Merge into the single child instead of rendering a pressable (R12) — **keeping the
-     * feedback**. Swapping this component out for a bare `Slot` would silently drop the
-     * touch feedback of every `asChild` control.
-     */
-    asChild?: boolean;
-    animation?: AnimationProp;
-    style?: StyleProp<ViewStyle>;
-    /**
-     * The overlays are children, not a prop — `<PressableFeedback.Highlight />` or
-     * `<PressableFeedback.Ripple />`, in any order: the root paints them under everything
-     * else wherever they sit. The scale is the root's own and needs nothing rendered.
-     *
-     * `Pressable`'s function form is dropped on purpose. It exists to hand the press state
-     * to children; here the root above already owns that state and this publishes it
-     * through context, so the function form would be a second, quieter source of truth.
-     */
-    children?: ReactNode;
-};
-/**
- * A slot's own animation, overriding the blanket one on the root. `false` switches that
- * slot off; the object tunes it. Deliberately two knobs rather than a full timing
- * surface — anything past this is a different animation, and that is a component's job,
- * not a prop's.
- */
-type SlotAnimation = boolean | {
-    /** Milliseconds. Falls back to the shared press timing. */
-    duration?: number;
-    /** How far the overlay goes at full press, 0 to 1. */
-    opacity?: number;
-};
-/** One ripple wave. Two of them, so a rapid double tap does not cut the one in flight. */
-type RippleWave = {
-    /** `0 → 1` as the circle opens. */
-    expand: SharedValue<number>;
-    /** `0 → 1` as the ink arrives, on its own curve. */
-    alpha: SharedValue<number>;
-    /** Where the finger landed, in the root's coordinates. */
-    origin: SharedValue<{
-        x: number;
-        y: number;
-    }>;
-};
-/**
- * The corner keys an overlay copies off the root. The `Left`/`Right` forms are absent
- * rather than forgotten: R13 bans them, because RN mirrors only the logical ones under RTL.
- */
-type RadiusStyle = Pick<ViewStyle, 'borderRadius' | 'borderStartStartRadius' | 'borderStartEndRadius' | 'borderEndStartRadius' | 'borderEndEndRadius'>;
-type FeedbackContext = {
-    /**
-     * The overlay's ink, resolved by the root from its own background.
-     *
-     * A wash or a wave has to contrast with what it sits on, and only the root knows that —
-     * it flattens its own `style` and reads `backgroundColor`, then takes the contrasting
-     * side the same way a tint does. Black ink at 10% on a saturated fill is close to
-     * invisible, which is the one thing a press indicator cannot be.
-     */
-    ink: string;
-    /**
-     * The root's own corners, so an overlay rounds itself to match. `corners` and not
-     * `radius`: the ripple already has a radius, and it is a length in points rather than a
-     * shape.
-     *
-     * An absolute fill has square corners and every control here is rounded, so without this
-     * both the wash and the wave paint outside the surface at each corner. The overlay
-     * carries the clip rather than the root: clipping the root would also cut a child that
-     * legitimately overflows — a badge on a button's corner — and that child has nothing to
-     * do with the press.
-     */
-    corners: RadiusStyle;
-    isPressed: boolean;
-    animation: ResolvedAnimation;
-    /** Absent on the static branch, where nothing animates and no worklet is mounted. */
-    progress?: SharedValue<number>;
-    /** How big the root is — what the scale coefficient is computed from. */
-    size?: SharedValue<{
-        width: number;
-        height: number;
-    }>;
-    /**
-     * The two ripple waves, driven by the **root**.
-     *
-     * They belong to the root because the root is the touch surface. An overlay carrying its
-     * own handlers only hears touches that land on *it* — and it is a sibling of the label,
-     * not its parent, so pressing the text of a button would do nothing. Touches bubble to
-     * the `Pressable`, which is why the handlers live there and the waves are published down.
-     */
-    waves?: readonly [RippleWave, RippleWave];
-};
-
-/**
- * A slot is a view or a text node, and a recipe writes one object per slot, so the two
- * RN style shapes are merged rather than discriminated per slot.
- */
-type SlotStyle = ViewStyle & TextStyle;
-type SlotStyles<Slot extends string> = Partial<Record<Slot, SlotStyle>>;
-/** The roles a variant consumes. The variant names tokens; `paint` says where they land. */
-type VariantRole = 'bg' | 'bgPressed' | 'fg' | 'border';
-/** Token names per role — no colour value ever appears in a recipe. */
-type VariantTokens = Partial<Record<VariantRole, keyof XAUIColors>>;
-/** The same roles resolved: theme colours, or the slices of a raw `color`. */
-type VariantColors = Partial<Record<VariantRole, string>>;
-/**
- * `disabled` is applied last of the three: a control that is both pressed and disabled
- * has to read disabled.
- */
-type StateName = 'focused' | 'pressed' | 'disabled';
-type States = Partial<Record<StateName, boolean>>;
-/** Reads the theme and the variant's resolved colours; returns one style per slot. */
-type StyleFn<Slot extends string> = (theme: XAUITheme, colors: VariantColors) => SlotStyles<Slot>;
-/** Named axes of finite token values — `{ size: { sm: fn, md: fn } }`. */
-type Axes<Slot extends string> = Record<string, Record<string, StyleFn<Slot>>>;
-/** One value per axis, plus the variant. Missing keys fall back to `defaultVariants`. */
-type Selection<Variant extends string, A extends Axes<string>> = {
-    variant?: Variant;
-} & {
-    [Axis in keyof A]?: Extract<keyof A[Axis], string>;
-};
-type CompoundVariant<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    when: Selection<Variant, A>;
-    style: StyleFn<Slot>;
-};
-type RecipeConfig<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    /** Every slot the component publishes. Slots a recipe never styles resolve to `{}`. */
-    slots: readonly Slot[];
-    base?: StyleFn<Slot>;
-    variantTokens?: Record<Variant, VariantTokens>;
-    /** Where the variant's colours land — written once, and it holds for every variant. */
-    paint?: StyleFn<Slot>;
-    variants?: A;
-    compoundVariants?: ReadonlyArray<CompoundVariant<Slot, Variant, A>>;
-    states?: Partial<Record<StateName, StyleFn<Slot>>>;
-    /**
-     * `NoInfer`, because this is the one place a single variant name appears on its own:
-     * without it, inference reads `Variant` off `{ variant: 'primary' }` and narrows the
-     * whole recipe to that one value, so every other variant becomes a type error at the
-     * call site. `variantTokens` is the declaration; this only picks a default from it.
-     */
-    defaultVariants?: Selection<NoInfer<Variant>, A>;
-};
-/** Stable references: the same object for the same tokens, for the app's lifetime. */
-type ResolvedStyles<Slot extends string> = Readonly<Record<Slot, SlotStyle>>;
-/** A selection with `defaultVariants` already folded in, keyed by axis name. */
-type ResolvedSelection = Readonly<Record<string, string | undefined>>;
-
-type ResolveArgs<Variant extends string, A extends Axes<string>> = {
-    theme: XAUITheme;
-    selection?: Selection<Variant, A>;
-    states?: States;
-};
-type TintArgs<Variant extends string, A extends Axes<string>> = ResolveArgs<Variant, A> & {
-    color: string;
-};
-type Recipe<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    readonly slots: readonly Slot[];
-    /** The cached pass: stable `StyleSheet` references, keyed by tokens alone. */
-    resolve(args: ResolveArgs<Variant, A>): ResolvedStyles<Slot>;
-    /**
-     * The tint pass: the same functions run again with `color`'s slices in place of the
-     * theme's tokens. Uncached and allocating, and only ever called when `color` is set.
-     */
-    tint(args: TintArgs<Variant, A>): SlotStyles<Slot>;
-};
-/**
- * A component's style, declared once. Resolution splits in two because the two halves
- * have different lifetimes: everything keyed by a finite token is cached forever, and
- * an arbitrary `color` is recomputed per render — which is what keeps the cache bounded
- * by the number of token combinations rather than by the palette users invent.
- *
- *     const styles = buttonRecipe.resolve({ theme, selection: { variant, size }, states })
- *     const tint = color ? buttonRecipe.tint({ theme, color, selection, states }) : undefined
- *     <View style={[styles.root, tint?.root, style]} />
- */
-declare function createRecipe<Slot extends string, Variant extends string, const A extends Axes<Slot>>(config: RecipeConfig<Slot, Variant, A>): Recipe<Slot, Variant, A>;
-
-export { type AnimationConfig as A, type CompoundVariant as C, type DirectionalStyleKey as D, type FeedbackContext as F, type IconComponentProps as I, type PressableFeedbackProps as P, type RadiusStyle as R, type SlotAnimation as S, type TintArgs as T, type VariantColors as V, type IconContextValue as a, type IconProps as b, type AnimationProp as c, type ResolvedAnimation as d, type RippleWave as e, createRecipe as f, type Recipe as g, type ResolveArgs as h, type Axes as i, type RecipeConfig as j, type ResolvedSelection as k, type ResolvedStyles as l, type Selection as m, type SlotStyle as n, type SlotStyles as o, type StateName as p, type States as q, type StyleFn as r, type VariantRole as s, type VariantTokens as t, type ImageStyleProps as u, type StyleProps as v, type TextStyleProps as w, type ViewStyleProps as x };

package/dist/create-recipe-DD9W6m9b.d.ts

@@ -1,280 +0,0 @@
-import { ComponentType, ReactNode } from 'react';
-import { ImageStyle, TextStyle, ViewStyle, ImageSourcePropType, StyleProp, PressableProps } from 'react-native';
-import { SharedValue } from 'react-native-reanimated';
-import { g as XAUITheme, X as XAUIColors } from './theme.type-C9bFJKFm.js';
-
-/**
- * R13 — React Native mirrors a layout under RTL through the Start/End properties and only
- * those. A props API is exactly where someone writes `paddingLeft` without thinking, so
- * the type removes the temptation instead of leaving it to a review.
- */
-type DirectionalStyleKey = 'left' | 'right' | 'paddingLeft' | 'paddingRight' | 'marginLeft' | 'marginRight' | 'borderLeftWidth' | 'borderRightWidth' | 'borderLeftColor' | 'borderRightColor' | 'borderTopLeftRadius' | 'borderTopRightRadius' | 'borderBottomLeftRadius' | 'borderBottomRightRadius';
-/**
- * `pointerEvents` is a style key *and* a `View` prop. R14 says the component's own prop
- * wins, so it stays the prop it has always been and is not exposed twice — the one name
- * where the two vocabularies collide.
- */
-type ComponentOwnedStyleKey = 'pointerEvents';
-/**
- * The style keys of a node, exposed as props (R14). Not a maintained list: it derives
- * from the React Native type, minus what R13 forbids.
- *
- * ```ts
- * type CardProps = ViewStyleProps & { variant?: CardVariant }
- * ```
- */
-type StyleProps<Style> = Omit<Style, DirectionalStyleKey | ComponentOwnedStyleKey>;
-/** A root, or any slot that renders a view. */
-type ViewStyleProps = StyleProps<ViewStyle>;
-/** A text slot — `color`, `fontSize`, `letterSpacing`… */
-type TextStyleProps = StyleProps<TextStyle>;
-/** An image slot — `resizeMode`, `tintColor`… */
-type ImageStyleProps = StyleProps<ImageStyle>;
-
-/**
- * The props Lucide, Ionicons and `react-native-vector-icons` all accept — the shape
- * `as` is handed. It is a convention rather than an interface anyone published, which is
- * exactly why `Icon` exists: without it every call site computes the two values by hand.
- */
-type IconComponentProps = {
-    size?: number;
-    color?: string;
-};
-/**
- * R14 reaches the **`source` form only**, exactly like `style` below and for the same
- * reason: it is the one of the three forms where we render the node. On the other two,
- * `size` and `color` are what shapes the icon.
- */
-type IconProps = ImageStyleProps & {
-    /** An icon component. `size` and `color` are injected into it. */
-    as?: ComponentType<IconComponentProps>;
-    /** A raw `react-native-svg` element, cloned with the resolved size and colour. */
-    children?: ReactNode;
-    /** An image, tinted with the resolved colour. */
-    source?: ImageSourcePropType;
-    /** Overrides what the surrounding slot asked for. */
-    size?: number;
-    /** A raw value (R7), never a token. Overrides the slot's. */
-    color?: string;
-    /**
-     * The **`source` form only** — it is the one of the three where we render the view.
-     * `as` hands its props to a third-party component and the children form clones an
-     * element the caller made; neither is a view this can style, and wrapping them would
-     * add a level of depth to every icon in the library. `size` and `color` are the
-     * escape hatch there.
-     */
-    style?: StyleProp<ImageStyle>;
-};
-/** What a component root publishes so the icons inside it need no props at all. */
-type IconContextValue = {
-    size?: number;
-    color?: string;
-};
-
-type AnimationConfig = {
-    scale?: boolean;
-    highlight?: boolean;
-    ripple?: boolean;
-};
-/**
- * `false` and `'disabled'` turn this component's animations off. `'disable-all'` turns
- * them off for its descendants too — a long list kills every row's worklets with one
- * prop instead of threading it down. An object switches them off one at a time.
- */
-type AnimationProp = boolean | 'disabled' | 'disable-all' | AnimationConfig;
-/** `animation` once normalised — what the components actually read. */
-type ResolvedAnimation = {
-    scale: boolean;
-    highlight: boolean;
-    ripple: boolean;
-    /** True when every sub-animation is off: the branch that mounts no worklet at all. */
-    none: boolean;
-    /** Propagated to descendants through context. */
-    disableAll: boolean;
-};
-/**
- * R14 — it renders a `Pressable`, so it takes that node's style keys as props. The
- * primitive every pressable component in the library is built on cannot be the one place
- * where `padding={16}` has to become an object again.
- */
-type PressableFeedbackProps = Omit<PressableProps, 'style' | 'children' | 'disabled'> & ViewStyleProps & {
-    /** Controlled: the root owns the state, because its recipe resolves on it (R5). */
-    isPressed?: boolean;
-    /** R8: `disabled` is not part of the public vocabulary, `isX` is. */
-    isDisabled?: boolean;
-    /**
-     * Merge into the single child instead of rendering a pressable (R12) — **keeping the
-     * feedback**. Swapping this component out for a bare `Slot` would silently drop the
-     * touch feedback of every `asChild` control.
-     */
-    asChild?: boolean;
-    animation?: AnimationProp;
-    style?: StyleProp<ViewStyle>;
-    /**
-     * The overlays are children, not a prop — `<PressableFeedback.Highlight />` or
-     * `<PressableFeedback.Ripple />`, in any order: the root paints them under everything
-     * else wherever they sit. The scale is the root's own and needs nothing rendered.
-     *
-     * `Pressable`'s function form is dropped on purpose. It exists to hand the press state
-     * to children; here the root above already owns that state and this publishes it
-     * through context, so the function form would be a second, quieter source of truth.
-     */
-    children?: ReactNode;
-};
-/**
- * A slot's own animation, overriding the blanket one on the root. `false` switches that
- * slot off; the object tunes it. Deliberately two knobs rather than a full timing
- * surface — anything past this is a different animation, and that is a component's job,
- * not a prop's.
- */
-type SlotAnimation = boolean | {
-    /** Milliseconds. Falls back to the shared press timing. */
-    duration?: number;
-    /** How far the overlay goes at full press, 0 to 1. */
-    opacity?: number;
-};
-/** One ripple wave. Two of them, so a rapid double tap does not cut the one in flight. */
-type RippleWave = {
-    /** `0 → 1` as the circle opens. */
-    expand: SharedValue<number>;
-    /** `0 → 1` as the ink arrives, on its own curve. */
-    alpha: SharedValue<number>;
-    /** Where the finger landed, in the root's coordinates. */
-    origin: SharedValue<{
-        x: number;
-        y: number;
-    }>;
-};
-/**
- * The corner keys an overlay copies off the root. The `Left`/`Right` forms are absent
- * rather than forgotten: R13 bans them, because RN mirrors only the logical ones under RTL.
- */
-type RadiusStyle = Pick<ViewStyle, 'borderRadius' | 'borderStartStartRadius' | 'borderStartEndRadius' | 'borderEndStartRadius' | 'borderEndEndRadius'>;
-type FeedbackContext = {
-    /**
-     * The overlay's ink, resolved by the root from its own background.
-     *
-     * A wash or a wave has to contrast with what it sits on, and only the root knows that —
-     * it flattens its own `style` and reads `backgroundColor`, then takes the contrasting
-     * side the same way a tint does. Black ink at 10% on a saturated fill is close to
-     * invisible, which is the one thing a press indicator cannot be.
-     */
-    ink: string;
-    /**
-     * The root's own corners, so an overlay rounds itself to match. `corners` and not
-     * `radius`: the ripple already has a radius, and it is a length in points rather than a
-     * shape.
-     *
-     * An absolute fill has square corners and every control here is rounded, so without this
-     * both the wash and the wave paint outside the surface at each corner. The overlay
-     * carries the clip rather than the root: clipping the root would also cut a child that
-     * legitimately overflows — a badge on a button's corner — and that child has nothing to
-     * do with the press.
-     */
-    corners: RadiusStyle;
-    isPressed: boolean;
-    animation: ResolvedAnimation;
-    /** Absent on the static branch, where nothing animates and no worklet is mounted. */
-    progress?: SharedValue<number>;
-    /** How big the root is — what the scale coefficient is computed from. */
-    size?: SharedValue<{
-        width: number;
-        height: number;
-    }>;
-    /**
-     * The two ripple waves, driven by the **root**.
-     *
-     * They belong to the root because the root is the touch surface. An overlay carrying its
-     * own handlers only hears touches that land on *it* — and it is a sibling of the label,
-     * not its parent, so pressing the text of a button would do nothing. Touches bubble to
-     * the `Pressable`, which is why the handlers live there and the waves are published down.
-     */
-    waves?: readonly [RippleWave, RippleWave];
-};
-
-/**
- * A slot is a view or a text node, and a recipe writes one object per slot, so the two
- * RN style shapes are merged rather than discriminated per slot.
- */
-type SlotStyle = ViewStyle & TextStyle;
-type SlotStyles<Slot extends string> = Partial<Record<Slot, SlotStyle>>;
-/** The roles a variant consumes. The variant names tokens; `paint` says where they land. */
-type VariantRole = 'bg' | 'bgPressed' | 'fg' | 'border';
-/** Token names per role — no colour value ever appears in a recipe. */
-type VariantTokens = Partial<Record<VariantRole, keyof XAUIColors>>;
-/** The same roles resolved: theme colours, or the slices of a raw `color`. */
-type VariantColors = Partial<Record<VariantRole, string>>;
-/**
- * `disabled` is applied last of the three: a control that is both pressed and disabled
- * has to read disabled.
- */
-type StateName = 'focused' | 'pressed' | 'disabled';
-type States = Partial<Record<StateName, boolean>>;
-/** Reads the theme and the variant's resolved colours; returns one style per slot. */
-type StyleFn<Slot extends string> = (theme: XAUITheme, colors: VariantColors) => SlotStyles<Slot>;
-/** Named axes of finite token values — `{ size: { sm: fn, md: fn } }`. */
-type Axes<Slot extends string> = Record<string, Record<string, StyleFn<Slot>>>;
-/** One value per axis, plus the variant. Missing keys fall back to `defaultVariants`. */
-type Selection<Variant extends string, A extends Axes<string>> = {
-    variant?: Variant;
-} & {
-    [Axis in keyof A]?: Extract<keyof A[Axis], string>;
-};
-type CompoundVariant<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    when: Selection<Variant, A>;
-    style: StyleFn<Slot>;
-};
-type RecipeConfig<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    /** Every slot the component publishes. Slots a recipe never styles resolve to `{}`. */
-    slots: readonly Slot[];
-    base?: StyleFn<Slot>;
-    variantTokens?: Record<Variant, VariantTokens>;
-    /** Where the variant's colours land — written once, and it holds for every variant. */
-    paint?: StyleFn<Slot>;
-    variants?: A;
-    compoundVariants?: ReadonlyArray<CompoundVariant<Slot, Variant, A>>;
-    states?: Partial<Record<StateName, StyleFn<Slot>>>;
-    /**
-     * `NoInfer`, because this is the one place a single variant name appears on its own:
-     * without it, inference reads `Variant` off `{ variant: 'primary' }` and narrows the
-     * whole recipe to that one value, so every other variant becomes a type error at the
-     * call site. `variantTokens` is the declaration; this only picks a default from it.
-     */
-    defaultVariants?: Selection<NoInfer<Variant>, A>;
-};
-/** Stable references: the same object for the same tokens, for the app's lifetime. */
-type ResolvedStyles<Slot extends string> = Readonly<Record<Slot, SlotStyle>>;
-/** A selection with `defaultVariants` already folded in, keyed by axis name. */
-type ResolvedSelection = Readonly<Record<string, string | undefined>>;
-
-type ResolveArgs<Variant extends string, A extends Axes<string>> = {
-    theme: XAUITheme;
-    selection?: Selection<Variant, A>;
-    states?: States;
-};
-type TintArgs<Variant extends string, A extends Axes<string>> = ResolveArgs<Variant, A> & {
-    color: string;
-};
-type Recipe<Slot extends string, Variant extends string, A extends Axes<Slot>> = {
-    readonly slots: readonly Slot[];
-    /** The cached pass: stable `StyleSheet` references, keyed by tokens alone. */
-    resolve(args: ResolveArgs<Variant, A>): ResolvedStyles<Slot>;
-    /**
-     * The tint pass: the same functions run again with `color`'s slices in place of the
-     * theme's tokens. Uncached and allocating, and only ever called when `color` is set.
-     */
-    tint(args: TintArgs<Variant, A>): SlotStyles<Slot>;
-};
-/**
- * A component's style, declared once. Resolution splits in two because the two halves
- * have different lifetimes: everything keyed by a finite token is cached forever, and
- * an arbitrary `color` is recomputed per render — which is what keeps the cache bounded
- * by the number of token combinations rather than by the palette users invent.
- *
- *     const styles = buttonRecipe.resolve({ theme, selection: { variant, size }, states })
- *     const tint = color ? buttonRecipe.tint({ theme, color, selection, states }) : undefined
- *     <View style={[styles.root, tint?.root, style]} />
- */
-declare function createRecipe<Slot extends string, Variant extends string, const A extends Axes<Slot>>(config: RecipeConfig<Slot, Variant, A>): Recipe<Slot, Variant, A>;
-
-export { type AnimationConfig as A, type CompoundVariant as C, type DirectionalStyleKey as D, type FeedbackContext as F, type IconComponentProps as I, type PressableFeedbackProps as P, type RadiusStyle as R, type SlotAnimation as S, type TintArgs as T, type VariantColors as V, type IconContextValue as a, type IconProps as b, type AnimationProp as c, type ResolvedAnimation as d, type RippleWave as e, createRecipe as f, type Recipe as g, type ResolveArgs as h, type Axes as i, type RecipeConfig as j, type ResolvedSelection as k, type ResolvedStyles as l, type Selection as m, type SlotStyle as n, type SlotStyles as o, type StateName as p, type States as q, type StyleFn as r, type VariantRole as s, type VariantTokens as t, type ImageStyleProps as u, type StyleProps as v, type TextStyleProps as w, type ViewStyleProps as x };