@xaui/native 0.9.1-alpha.21 → 0.9.1-alpha.23

package/dist/system/index.d.cts

@@ -1,16 +1,18 @@
+import * as react_native from 'react-native';
+import { StyleProp, ViewStyle, View } from 'react-native';
 import * as react from 'react';
 import { ReactNode, Provider, Ref, RefCallback } from 'react';
-import { b as IconProps, a as IconContextValue } from '../icon.type-Cs1tMX0W.cjs';
-export { I as IconComponentProps } from '../icon.type-Cs1tMX0W.cjs';
-import { V as ViewStyleProps } from '../style-props.type-B1BG5TCm.cjs';
-export { D as DirectionalStyleKey, I as ImageStyleProps, S as StyleProps, T as TextStyleProps } from '../style-props.type-B1BG5TCm.cjs';
-import { S as SlotAnimation, F as FeedbackContext, a as AnimationProp, b as ResolvedAnimation } from '../pressable-feedback.type-wfeiJz5m.cjs';
-export { A as AnimationConfig, P as PressableFeedbackProps, R as RadiusStyle, c as RippleWave } from '../pressable-feedback.type-wfeiJz5m.cjs';
-import * as react_native from 'react-native';
-import { StyleProp, ViewStyle } from 'react-native';
-export { A as Axes, C as CompoundVariant, R as Recipe, b as RecipeConfig, a as ResolveArgs, d as ResolvedSelection, e as ResolvedStyles, S as Selection, f as SlotStyle, g as SlotStyles, h as StateName, i as States, j as StyleFn, T as TintArgs, V as VariantColors, k as VariantRole, l as VariantTokens, c as createRecipe } from '../create-recipe-CPBFg7ym.cjs';
+import { S as SlotAnimation, F as FeedbackContext, a as AnimationProp, b as ResolvedAnimation, P as PressableFeedbackProps } from '../pressable-feedback.type-BA2C9sSz.cjs';
+export { A as AnimationConfig, R as RadiusStyle, c as RippleWave } from '../pressable-feedback.type-BA2C9sSz.cjs';
+import { R as RadiusKey, X as XAUITheme } from '../theme.type-C2gNHpEx.cjs';
+import { j as StyleFn, f as SlotStyle } from '../create-recipe-dBN_ewZc.cjs';
+export { A as Axes, C as CompoundVariant, R as Recipe, b as RecipeConfig, a as ResolveArgs, d as ResolvedSelection, e as ResolvedStyles, S as Selection, g as SlotStyles, h as StateName, i as States, T as TintArgs, V as VariantColors, k as VariantRole, l as VariantTokens, c as createRecipe } from '../create-recipe-dBN_ewZc.cjs';
+export { C as CloseButtonProps } from '../close-button.type-CHsgZ3wO.cjs';
+import { b as IconProps, a as IconContextValue } from '../icon.type-CF4KiMKl.cjs';
+export { I as IconComponentProps } from '../icon.type-CF4KiMKl.cjs';
+import { V as ViewStyleProps } from '../style-props.type-CfnoGEP7.cjs';
+export { D as DirectionalStyleKey, I as ImageStyleProps, S as StyleProps, T as TextStyleProps } from '../style-props.type-CfnoGEP7.cjs';
 import 'react-native-reanimated';
-import '../theme.type-C2gNHpEx.cjs';
 
 /**
  * The runtime half of R14. The type half lives in `system/style-props/`, and the two are
@@ -119,95 +121,6 @@ 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;
@@ -385,7 +298,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, "style" | "children" | "disabled"> & ViewStyleProps & {
+declare const PressableFeedback: react.ForwardRefExoticComponent<Omit<react_native.PressableProps, "disabled" | "style" | "children"> & ViewStyleProps & {
     isPressed?: boolean;
     isDisabled?: boolean;
     asChild?: boolean;
@@ -397,4 +310,165 @@ declare const PressableFeedback: react.ForwardRefExoticComponent<Omit<react_nati
     Ripple: typeof PressableFeedbackRipple;
 };
 
-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 };
+/**
+ * The `radius` axis, which is the same ten lines in every component that has one — a key
+ * of the radius scale, applied to one slot, overriding whatever `size` chose.
+ *
+ * It is written here rather than a third time in a recipe because that is the rule §2 bis
+ * states: extract at the second use, and by the end of P3 this axis exists in a dozen
+ * components. Nothing about it is component-specific except which slot carries the corner.
+ *
+ * ```ts
+ * variants: { size: { … }, radius: radiusAxis('root') }
+ * ```
+ *
+ * The return type is a full `Record<RadiusKey, …>` rather than a partial one, so
+ * `createRecipe` still infers `radius="3xl"` as the axis's value union and a typo in a
+ * caller's `radius` is a type error rather than a silently ignored key.
+ */
+declare function radiusAxis<Slot extends string>(slot: Slot): Record<RadiusKey, StyleFn<Slot>>;
+
+/**
+ * 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>>;
+
+/**
+ * The dismiss affordance shared by everything that can be dismissed — `Chip.Close`,
+ * `Alert.Close`, and the `Dialog`, `Snackbar` and `Sheet` of P5. Each of those is a
+ * five-line call site handing it the styles its own recipe resolved:
+ *
+ * ```tsx
+ * const { closeStyle, closeGlyphStyle, isDisabled } = useChip()
+ *
+ * <CloseButton
+ *   name="Chip.Close"
+ *   baseStyle={closeStyle}
+ *   glyphStyle={closeGlyphStyle}
+ *   isDisabled={isDisabled}
+ * />
+ * ```
+ *
+ * **It owns its press state**, unlike every other pressable in the library, where the
+ * component root owns it because its recipe resolves on it. Here the surrounding
+ * component is usually not a control at all, and where it is, the two are different
+ * targets: pressing the cross must not read as pressing the chip around it.
+ *
+ * With no children it draws its own cross from two bars a quarter turn apart, so a
+ * dismissible component works in a project that has installed no icon set.
+ */
+declare const CloseButton: react.ForwardRefExoticComponent<{
+    name: string;
+    children?: react.ReactNode;
+    baseStyle?: react_native.StyleProp<react_native.ViewStyle>;
+    glyphStyle?: react_native.StyleProp<react_native.ViewStyle>;
+    style?: react_native.StyleProp<react_native.ViewStyle> | ((state: react_native.PressableStateCallbackType) => react_native.StyleProp<react_native.ViewStyle>);
+} & Omit<PressableFeedbackProps, "isPressed" | "style" | "children"> & react.RefAttributes<View>>;
+
+/** The two slots a component publishes for a `CloseButton`: its box and one cross bar. */
+type CloseButtonSlots = {
+    close: SlotStyle;
+    closeGlyph: SlotStyle;
+};
+/**
+ * The cross's own geometry, for the `base` of any recipe that hosts a `CloseButton`:
+ *
+ * ```ts
+ * base: theme => ({ ...closeButtonBase(theme), root: { … } })
+ * ```
+ *
+ * The bar's thickness and the box's centring belong to the button rather than to the
+ * component around it, so they are written once here. What stays in the recipe is what is
+ * genuinely the component's: the size of the box and the length of the bar, both of which
+ * follow that component's own scale.
+ *
+ * Two bars are rendered, rotated a quarter turn apart, which is why only one is described
+ * and why it is positioned absolutely — they overlap at the centre of the box.
+ */
+declare function closeButtonBase(theme: XAUITheme): CloseButtonSlots;
+
+export { AnimationProp, type AsChildProps, CloseButton, type CloseButtonSlots, 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, PressableFeedbackProps, 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, SlotStyle, StyleFn, ViewStyleProps, childrenToString, closeButtonBase, createSlotContext, markOverlay, mergeProps, mergeRefs, pressScaleFor, radiusAxis, resolveAnimation, resolveSlotAnimation, rippleRadiusFor, useFeedback, useIconContext, useStyleProps };

package/dist/system/index.d.ts

@@ -1,16 +1,18 @@
+import * as react_native from 'react-native';
+import { StyleProp, ViewStyle, View } from 'react-native';
 import * as react from 'react';
 import { ReactNode, Provider, Ref, RefCallback } from 'react';
-import { b as IconProps, a as IconContextValue } from '../icon.type-BkcEPJbK.js';
-export { I as IconComponentProps } from '../icon.type-BkcEPJbK.js';
-import { V as ViewStyleProps } from '../style-props.type-B1BG5TCm.js';
-export { D as DirectionalStyleKey, I as ImageStyleProps, S as StyleProps, T as TextStyleProps } from '../style-props.type-B1BG5TCm.js';
-import { S as SlotAnimation, F as FeedbackContext, a as AnimationProp, b as ResolvedAnimation } from '../pressable-feedback.type-DsvWZXWC.js';
-export { A as AnimationConfig, P as PressableFeedbackProps, R as RadiusStyle, c as RippleWave } from '../pressable-feedback.type-DsvWZXWC.js';
-import * as react_native from 'react-native';
-import { StyleProp, ViewStyle } from 'react-native';
-export { A as Axes, C as CompoundVariant, R as Recipe, b as RecipeConfig, a as ResolveArgs, d as ResolvedSelection, e as ResolvedStyles, S as Selection, f as SlotStyle, g as SlotStyles, h as StateName, i as States, j as StyleFn, T as TintArgs, V as VariantColors, k as VariantRole, l as VariantTokens, c as createRecipe } from '../create-recipe-CC3NNCqF.js';
+import { S as SlotAnimation, F as FeedbackContext, a as AnimationProp, b as ResolvedAnimation, P as PressableFeedbackProps } from '../pressable-feedback.type-Bs4dQlGj.js';
+export { A as AnimationConfig, R as RadiusStyle, c as RippleWave } from '../pressable-feedback.type-Bs4dQlGj.js';
+import { R as RadiusKey, X as XAUITheme } from '../theme.type-C2gNHpEx.js';
+import { j as StyleFn, f as SlotStyle } from '../create-recipe-C4JkINrA.js';
+export { A as Axes, C as CompoundVariant, R as Recipe, b as RecipeConfig, a as ResolveArgs, d as ResolvedSelection, e as ResolvedStyles, S as Selection, g as SlotStyles, h as StateName, i as States, T as TintArgs, V as VariantColors, k as VariantRole, l as VariantTokens, c as createRecipe } from '../create-recipe-C4JkINrA.js';
+export { C as CloseButtonProps } from '../close-button.type-BUYuoSt2.js';
+import { b as IconProps, a as IconContextValue } from '../icon.type-Dq4_qePa.js';
+export { I as IconComponentProps } from '../icon.type-Dq4_qePa.js';
+import { V as ViewStyleProps } from '../style-props.type-CfnoGEP7.js';
+export { D as DirectionalStyleKey, I as ImageStyleProps, S as StyleProps, T as TextStyleProps } from '../style-props.type-CfnoGEP7.js';
 import 'react-native-reanimated';
-import '../theme.type-C2gNHpEx.js';
 
 /**
  * The runtime half of R14. The type half lives in `system/style-props/`, and the two are
@@ -119,95 +121,6 @@ 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;
@@ -385,7 +298,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, "style" | "children" | "disabled"> & ViewStyleProps & {
+declare const PressableFeedback: react.ForwardRefExoticComponent<Omit<react_native.PressableProps, "disabled" | "style" | "children"> & ViewStyleProps & {
     isPressed?: boolean;
     isDisabled?: boolean;
     asChild?: boolean;
@@ -397,4 +310,165 @@ declare const PressableFeedback: react.ForwardRefExoticComponent<Omit<react_nati
     Ripple: typeof PressableFeedbackRipple;
 };
 
-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 };
+/**
+ * The `radius` axis, which is the same ten lines in every component that has one — a key
+ * of the radius scale, applied to one slot, overriding whatever `size` chose.
+ *
+ * It is written here rather than a third time in a recipe because that is the rule §2 bis
+ * states: extract at the second use, and by the end of P3 this axis exists in a dozen
+ * components. Nothing about it is component-specific except which slot carries the corner.
+ *
+ * ```ts
+ * variants: { size: { … }, radius: radiusAxis('root') }
+ * ```
+ *
+ * The return type is a full `Record<RadiusKey, …>` rather than a partial one, so
+ * `createRecipe` still infers `radius="3xl"` as the axis's value union and a typo in a
+ * caller's `radius` is a type error rather than a silently ignored key.
+ */
+declare function radiusAxis<Slot extends string>(slot: Slot): Record<RadiusKey, StyleFn<Slot>>;
+
+/**
+ * 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>>;
+
+/**
+ * The dismiss affordance shared by everything that can be dismissed — `Chip.Close`,
+ * `Alert.Close`, and the `Dialog`, `Snackbar` and `Sheet` of P5. Each of those is a
+ * five-line call site handing it the styles its own recipe resolved:
+ *
+ * ```tsx
+ * const { closeStyle, closeGlyphStyle, isDisabled } = useChip()
+ *
+ * <CloseButton
+ *   name="Chip.Close"
+ *   baseStyle={closeStyle}
+ *   glyphStyle={closeGlyphStyle}
+ *   isDisabled={isDisabled}
+ * />
+ * ```
+ *
+ * **It owns its press state**, unlike every other pressable in the library, where the
+ * component root owns it because its recipe resolves on it. Here the surrounding
+ * component is usually not a control at all, and where it is, the two are different
+ * targets: pressing the cross must not read as pressing the chip around it.
+ *
+ * With no children it draws its own cross from two bars a quarter turn apart, so a
+ * dismissible component works in a project that has installed no icon set.
+ */
+declare const CloseButton: react.ForwardRefExoticComponent<{
+    name: string;
+    children?: react.ReactNode;
+    baseStyle?: react_native.StyleProp<react_native.ViewStyle>;
+    glyphStyle?: react_native.StyleProp<react_native.ViewStyle>;
+    style?: react_native.StyleProp<react_native.ViewStyle> | ((state: react_native.PressableStateCallbackType) => react_native.StyleProp<react_native.ViewStyle>);
+} & Omit<PressableFeedbackProps, "isPressed" | "style" | "children"> & react.RefAttributes<View>>;
+
+/** The two slots a component publishes for a `CloseButton`: its box and one cross bar. */
+type CloseButtonSlots = {
+    close: SlotStyle;
+    closeGlyph: SlotStyle;
+};
+/**
+ * The cross's own geometry, for the `base` of any recipe that hosts a `CloseButton`:
+ *
+ * ```ts
+ * base: theme => ({ ...closeButtonBase(theme), root: { … } })
+ * ```
+ *
+ * The bar's thickness and the box's centring belong to the button rather than to the
+ * component around it, so they are written once here. What stays in the recipe is what is
+ * genuinely the component's: the size of the box and the length of the bar, both of which
+ * follow that component's own scale.
+ *
+ * Two bars are rendered, rotated a quarter turn apart, which is why only one is described
+ * and why it is positioned absolutely — they overlap at the centre of the box.
+ */
+declare function closeButtonBase(theme: XAUITheme): CloseButtonSlots;
+
+export { AnimationProp, type AsChildProps, CloseButton, type CloseButtonSlots, 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, PressableFeedbackProps, 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, SlotStyle, StyleFn, ViewStyleProps, childrenToString, closeButtonBase, createSlotContext, markOverlay, mergeProps, mergeRefs, pressScaleFor, radiusAxis, resolveAnimation, resolveSlotAnimation, rippleRadiusFor, useFeedback, useIconContext, useStyleProps };

package/dist/system/index.js

@@ -2,12 +2,16 @@ import {
   Portal,
   PortalContext,
   PortalHost
-} from "../chunk-XHZBXYVU.js";
+} from "../chunk-AKXG43S4.js";
+import {
+  CloseButton,
+  closeButtonBase
+} from "../chunk-ZQ3JSWRO.js";
 import {
   Icon,
   IconContext,
   useIconContext
-} from "../chunk-JL27KVRT.js";
+} from "../chunk-FVP5FUVS.js";
 import {
   FEEDBACK_OVERLAY,
   HIGHLIGHT_DURATION,
@@ -29,10 +33,12 @@ import {
   resolveSlotAnimation,
   rippleRadiusFor,
   useFeedback
-} from "../chunk-IBRVMLUF.js";
+} from "../chunk-KM2TI5IC.js";
 import {
-  createRecipe
-} from "../chunk-N7C4UNUL.js";
+  createRecipe,
+  radiusAxis
+} from "../chunk-3JATAB7S.js";
+import "../chunk-A3EGFI6T.js";
 import {
   Slot,
   childrenToString,
@@ -40,10 +46,10 @@ import {
   mergeProps,
   mergeRefs,
   useStyleProps
-} from "../chunk-EXX6ATAS.js";
-import "../chunk-A3EGFI6T.js";
+} from "../chunk-PMO62QK4.js";
 import "../chunk-GGW42MY4.js";
 export {
+  CloseButton,
   FEEDBACK_OVERLAY,
   HIGHLIGHT_DURATION,
   HIGHLIGHT_OPACITY,
@@ -65,12 +71,14 @@ export {
   SCALE_REFERENCE_WIDTH,
   Slot,
   childrenToString,
+  closeButtonBase,
   createRecipe,
   createSlotContext,
   markOverlay,
   mergeProps,
   mergeRefs,
   pressScaleFor,
+  radiusAxis,
   resolveAnimation,
   resolveSlotAnimation,
   rippleRadiusFor,