@xaui/native 0.9.1-alpha.3 → 0.9.1-alpha.30

package/dist/components/switch/index.js

@@ -0,0 +1,27 @@
+import {
+  Switch,
+  SwitchLabel,
+  SwitchRoot,
+  SwitchThumb,
+  SwitchTrack,
+  switchRecipe,
+  useSwitch
+} from "../../chunk-6RVCGLKZ.js";
+import "../../chunk-BFMTUMTU.js";
+import "../../chunk-423RQBOX.js";
+import "../../chunk-F6W3JQ7K.js";
+import "../../chunk-EGLLDKN6.js";
+import "../../chunk-4GTAZM2C.js";
+import "../../chunk-A3EGFI6T.js";
+import "../../chunk-E2CWBQTV.js";
+import "../../chunk-URSKA2VR.js";
+import "../../chunk-GGW42MY4.js";
+export {
+  Switch,
+  SwitchLabel,
+  SwitchRoot,
+  SwitchThumb,
+  SwitchTrack,
+  switchRecipe,
+  useSwitch
+};

package/dist/components/text-area/index.cjs

@@ -0,0 +1,14 @@
+"use strict";Object.defineProperty(exports, "__esModule", {value: true});
+
+
+var _chunk5GO7MAVYcjs = require('../../chunk-5GO7MAVY.cjs');
+require('../../chunk-5Z4P6WHR.cjs');
+require('../../chunk-FNEUOBCV.cjs');
+require('../../chunk-57SJ4LJF.cjs');
+require('../../chunk-ZP2E2H2G.cjs');
+require('../../chunk-GLGU2WFL.cjs');
+require('../../chunk-MC7SY2QH.cjs');
+
+
+
+exports.TextArea = _chunk5GO7MAVYcjs.TextArea; exports.useTextArea = _chunk5GO7MAVYcjs.useTextArea;

package/dist/components/text-area/index.d.cts

@@ -0,0 +1,73 @@
+import * as react from 'react';
+import { ReactNode } from 'react';
+import { I as InputFieldProps, a as InputProps } from '../../input.type-BUMDlzL9.cjs';
+import * as react_native from 'react-native';
+import { T as TextStyleProps } from '../../style-props.type-CfnoGEP7.cjs';
+import '../../theme.type-C2gNHpEx.cjs';
+
+type TextAreaOwnProps = {
+    /**
+     * How many lines tall the field starts. It is a **raw value**, not a token: it resolves
+     * outside the style cache from the line height the size chose, the same path `color`
+     * takes — which is what lets `rows={7}` exist without seven entries in the cache.
+     *
+     * @default 3
+     */
+    rows?: number;
+    /**
+     * The ceiling, in lines. Past it the field stops growing and scrolls; unset, it grows
+     * with the text for as long as the text goes on.
+     */
+    maxRows?: number;
+    children?: ReactNode;
+};
+/**
+ * Everything the `Input` root understands, plus the two the shape of a multiline field
+ * needs. They sit on the **root** rather than on `TextArea.Field` for the reason `size`
+ * and `variant` do: the root is where the field's shape is decided, and the slot reads
+ * what it resolved.
+ */
+type TextAreaProps = Omit<InputProps, 'children'> & TextAreaOwnProps;
+/**
+ * Everything `Input.Field` accepts except `multiline`, which this sets — it is the same
+ * `TextInput`, and the same props, with the three things several lines need.
+ */
+type TextAreaFieldProps = Omit<InputFieldProps, 'multiline'>;
+/**
+ * The one thing the `Input`'s own context cannot carry, because `rows` is not the
+ * `Input`'s business: a single-line field has no use for it, and a prop that does nothing
+ * in the common case is a prop that reads as broken.
+ */
+type TextAreaContextValue = {
+    rows: number;
+    maxRows: number | undefined;
+};
+
+declare const useTextArea: () => TextAreaContextValue;
+
+/**
+ * Three of the four slots **are** the `Input`'s, re-exported rather than wrapped.
+ *
+ * A wrapper would add three components to the tree to change a `displayName` string, and
+ * the string it would change is the one that tells you the truth: a `XAUI.Input.Label`
+ * showing up inside a `XAUI.TextArea.Root` is exactly what is happening. Only the field
+ * differs, and it is the only one written here.
+ */
+declare const TextArea: react.ForwardRefExoticComponent<Omit<InputProps, "children"> & {
+    rows?: number;
+    maxRows?: number;
+    children?: react.ReactNode;
+} & react.RefAttributes<react_native.View>> & {
+    Label: react.ForwardRefExoticComponent<react_native.TextProps & Omit<TextStyleProps, keyof react_native.TextProps> & {
+        children?: react.ReactNode;
+    } & react.RefAttributes<react_native.Text>>;
+    Field: react.ForwardRefExoticComponent<TextAreaFieldProps & react.RefAttributes<react_native.TextInput>>;
+    Description: react.ForwardRefExoticComponent<react_native.TextProps & Omit<TextStyleProps, keyof react_native.TextProps> & {
+        children?: react.ReactNode;
+    } & react.RefAttributes<react_native.Text>>;
+    Error: react.ForwardRefExoticComponent<react_native.TextProps & Omit<TextStyleProps, keyof react_native.TextProps> & {
+        children?: react.ReactNode;
+    } & react.RefAttributes<react_native.Text>>;
+};
+
+export { TextArea, type TextAreaContextValue, type TextAreaFieldProps, type TextAreaProps, useTextArea };

package/dist/components/text-area/index.d.ts

@@ -0,0 +1,73 @@
+import * as react from 'react';
+import { ReactNode } from 'react';
+import { I as InputFieldProps, a as InputProps } from '../../input.type-D2qgi03E.js';
+import * as react_native from 'react-native';
+import { T as TextStyleProps } from '../../style-props.type-CfnoGEP7.js';
+import '../../theme.type-C2gNHpEx.js';
+
+type TextAreaOwnProps = {
+    /**
+     * How many lines tall the field starts. It is a **raw value**, not a token: it resolves
+     * outside the style cache from the line height the size chose, the same path `color`
+     * takes — which is what lets `rows={7}` exist without seven entries in the cache.
+     *
+     * @default 3
+     */
+    rows?: number;
+    /**
+     * The ceiling, in lines. Past it the field stops growing and scrolls; unset, it grows
+     * with the text for as long as the text goes on.
+     */
+    maxRows?: number;
+    children?: ReactNode;
+};
+/**
+ * Everything the `Input` root understands, plus the two the shape of a multiline field
+ * needs. They sit on the **root** rather than on `TextArea.Field` for the reason `size`
+ * and `variant` do: the root is where the field's shape is decided, and the slot reads
+ * what it resolved.
+ */
+type TextAreaProps = Omit<InputProps, 'children'> & TextAreaOwnProps;
+/**
+ * Everything `Input.Field` accepts except `multiline`, which this sets — it is the same
+ * `TextInput`, and the same props, with the three things several lines need.
+ */
+type TextAreaFieldProps = Omit<InputFieldProps, 'multiline'>;
+/**
+ * The one thing the `Input`'s own context cannot carry, because `rows` is not the
+ * `Input`'s business: a single-line field has no use for it, and a prop that does nothing
+ * in the common case is a prop that reads as broken.
+ */
+type TextAreaContextValue = {
+    rows: number;
+    maxRows: number | undefined;
+};
+
+declare const useTextArea: () => TextAreaContextValue;
+
+/**
+ * Three of the four slots **are** the `Input`'s, re-exported rather than wrapped.
+ *
+ * A wrapper would add three components to the tree to change a `displayName` string, and
+ * the string it would change is the one that tells you the truth: a `XAUI.Input.Label`
+ * showing up inside a `XAUI.TextArea.Root` is exactly what is happening. Only the field
+ * differs, and it is the only one written here.
+ */
+declare const TextArea: react.ForwardRefExoticComponent<Omit<InputProps, "children"> & {
+    rows?: number;
+    maxRows?: number;
+    children?: react.ReactNode;
+} & react.RefAttributes<react_native.View>> & {
+    Label: react.ForwardRefExoticComponent<react_native.TextProps & Omit<TextStyleProps, keyof react_native.TextProps> & {
+        children?: react.ReactNode;
+    } & react.RefAttributes<react_native.Text>>;
+    Field: react.ForwardRefExoticComponent<TextAreaFieldProps & react.RefAttributes<react_native.TextInput>>;
+    Description: react.ForwardRefExoticComponent<react_native.TextProps & Omit<TextStyleProps, keyof react_native.TextProps> & {
+        children?: react.ReactNode;
+    } & react.RefAttributes<react_native.Text>>;
+    Error: react.ForwardRefExoticComponent<react_native.TextProps & Omit<TextStyleProps, keyof react_native.TextProps> & {
+        children?: react.ReactNode;
+    } & react.RefAttributes<react_native.Text>>;
+};
+
+export { TextArea, type TextAreaContextValue, type TextAreaFieldProps, type TextAreaProps, useTextArea };

package/dist/components/text-area/index.js

@@ -0,0 +1,14 @@
+import {
+  TextArea,
+  useTextArea
+} from "../../chunk-GVQOD3VW.js";
+import "../../chunk-A5OCK3C2.js";
+import "../../chunk-4GTAZM2C.js";
+import "../../chunk-A3EGFI6T.js";
+import "../../chunk-E2CWBQTV.js";
+import "../../chunk-URSKA2VR.js";
+import "../../chunk-GGW42MY4.js";
+export {
+  TextArea,
+  useTextArea
+};

package/dist/components/typography/index.cjs

@@ -0,0 +1,15 @@
+"use strict";Object.defineProperty(exports, "__esModule", {value: true});
+
+
+
+var _chunkQGN2BBJOcjs = require('../../chunk-QGN2BBJO.cjs');
+require('../../chunk-FNEUOBCV.cjs');
+require('../../chunk-57SJ4LJF.cjs');
+require('../../chunk-ZP2E2H2G.cjs');
+require('../../chunk-GLGU2WFL.cjs');
+require('../../chunk-MC7SY2QH.cjs');
+
+
+
+
+exports.TextSpan = _chunkQGN2BBJOcjs.TextSpan; exports.Typography = _chunkQGN2BBJOcjs.Typography; exports.typographyRecipe = _chunkQGN2BBJOcjs.typographyRecipe;

package/dist/components/typography/index.d.cts

@@ -0,0 +1,116 @@
+import * as react from 'react';
+import { ReactNode } from 'react';
+import * as react_native from 'react-native';
+import { TextProps, StyleProp, TextStyle, Text } from 'react-native';
+import { T as TextStyleProps } from '../../style-props.type-CfnoGEP7.cjs';
+import { R as Recipe } from '../../create-recipe-dC7wMfnj.cjs';
+import { X as XAUITheme } from '../../theme.type-C2gNHpEx.cjs';
+
+/**
+ * The ten roles, aligned with HeroUI Native's `text` — six headings, three body steps and
+ * inline code. Each one fixes **size, line height, weight and family together**, which is
+ * what removes the separate `size` and `weight` props the legacy component carried, and
+ * with them the illegal combinations they allowed: a heading in `weight="light"`, a
+ * caption in `lg`.
+ *
+ * `h1`–`h6` name a level, not an HTML tag — React Native has no document outline, so the
+ * number is the step on the scale and nothing more. Announcing a heading to a screen
+ * reader stays explicit: `accessibilityRole="header"`.
+ */
+type TypographyVariant = 'h1' | 'h2' | 'h3' | 'h4' | 'h5' | 'h6' | 'body' | 'body-sm' | 'body-xs' | 'code';
+type TypographySlot = 'root';
+type TypographyOwnProps = {
+    /** The role. It fixes size, line height, weight and family at once. */
+    variant?: TypographyVariant;
+    /**
+     * A raw tint (`'#7c3aed'`), never a token (R7). In a text component there is only one
+     * thing to tint, so it lands on the text itself.
+     */
+    color?: string;
+    /** R12 — the child element becomes the text node, keeping this variant's style. */
+    asChild?: boolean;
+    style?: StyleProp<TextStyle>;
+    children?: ReactNode;
+};
+/**
+ * R14 — the role's own vocabulary, then every `TextStyle` key it does not already claim.
+ * `color` is the component's, so it keeps its R7 meaning here rather than becoming the
+ * style key of the same name; `fontSize` and `fontWeight` stay available, which is how a
+ * one-off deviation is written without inventing a prop for it.
+ */
+type TypographyProps = Omit<TextProps, 'style'> & TypographyOwnProps & Omit<TextStyleProps, keyof TypographyOwnProps | keyof TextProps>;
+type TextSpanOwnProps = {
+    /** R12 — the child element becomes the span. */
+    asChild?: boolean;
+    style?: StyleProp<TextStyle>;
+    children?: ReactNode;
+};
+type TextSpanProps = Omit<TextProps, 'style'> & TextSpanOwnProps & Omit<TextStyleProps, keyof TextSpanOwnProps | keyof TextProps>;
+
+/**
+ * Text, by the role it plays.
+ *
+ * ```tsx
+ * <Typography variant="heading-lg">Projets</Typography>
+ * <Typography>Trois en cours, un archivé.</Typography>
+ * <Typography variant="caption">Mis à jour il y a deux minutes</Typography>
+ * ```
+ *
+ * **One node, and no slots.** A paragraph is a `Text`; there is nothing inside it for the
+ * component to publish. Styling a fragment of it is `TextSpan`'s job, not a slot of this
+ * one — React Native already makes a nested `Text` inherit from its parent, so a span
+ * needs no context, no resolved style and nothing from here. This component would only be
+ * duplicating a mechanism the platform ships.
+ *
+ * **The role fixes size, line height, weight and family together**, which is why there is
+ * no `size` and no `weight` prop: those axes are not free to combine. A one-off deviation
+ * is a style prop — `fontSize={17}` — said plainly rather than dressed as vocabulary.
+ *
+ * Alignment likewise has no prop of its own: `textAlign` is a `TextStyle` key, so R14
+ * already exposes it, and the caller writes the value React Native understands instead of
+ * a translation layer this component would have to keep honest.
+ */
+declare const Typography: react.ForwardRefExoticComponent<Omit<react_native.TextProps, "style"> & {
+    variant?: TypographyVariant;
+    color?: string;
+    asChild?: boolean;
+    style?: react_native.StyleProp<react_native.TextStyle>;
+    children?: react.ReactNode;
+} & Omit<TextStyleProps, "color" | "pointerEvents" | "disabled" | "style" | "children" | "id" | "onLayout" | "testID" | "nativeID" | "accessible" | "accessibilityActions" | "accessibilityLabel" | "aria-label" | "accessibilityRole" | "accessibilityState" | "aria-busy" | "aria-checked" | "aria-disabled" | "aria-expanded" | "aria-selected" | "accessibilityHint" | "accessibilityValue" | "aria-valuemax" | "aria-valuemin" | "aria-valuenow" | "aria-valuetext" | "onAccessibilityAction" | "importantForAccessibility" | "aria-hidden" | "aria-modal" | "role" | "accessibilityLabelledBy" | "aria-labelledby" | "accessibilityLiveRegion" | "aria-live" | "screenReaderFocusable" | "accessibilityElementsHidden" | "accessibilityViewIsModal" | "onAccessibilityEscape" | "onAccessibilityTap" | "onMagicTap" | "accessibilityIgnoresInvertColors" | "accessibilityLanguage" | "accessibilityShowsLargeContentViewer" | "accessibilityLargeContentTitle" | "accessibilityRespondsToUserInteraction" | "onPress" | "onPressIn" | "onPressOut" | "onLongPress" | "pressRetentionOffset" | "asChild" | "variant" | "allowFontScaling" | "ellipsizeMode" | "lineBreakMode" | "numberOfLines" | "onTextLayout" | "maxFontSizeMultiplier" | "minimumFontScale" | "adjustsFontSizeToFit" | "dynamicTypeRamp" | "suppressHighlighting" | "lineBreakStrategyIOS" | "selectable" | "selectionColor" | "textBreakStrategy" | "dataDetectorType" | "android_hyphenationFrequency"> & react.RefAttributes<Text>>;
+
+/**
+ * A fragment of text, styled apart from the text around it.
+ *
+ * ```tsx
+ * <Typography>
+ *   Supprimer <TextSpan fontWeight="600">trois projets</TextSpan> définitivement.
+ * </Typography>
+ * ```
+ *
+ * **It is a bare React Native `Text`, and that is the whole design.** Nesting a `Text`
+ * inside a `Text` already inherits the parent's font, size, weight and colour on both
+ * platforms — so a span needs no context to read, no role to resolve and no provider
+ * above it. The legacy component published a `TextSpanContext` to carry that inheritance
+ * by hand; it was reimplementing the platform, and it is gone.
+ *
+ * What is left is R14 and nothing else: every `TextStyle` key as a prop, and `style` after
+ * them. There is no `variant` here on purpose — a span that names a role would be a
+ * `Typography`, and nesting one of those is how you change role mid-sentence.
+ */
+declare const TextSpan: react.ForwardRefExoticComponent<Omit<react_native.TextProps, "style"> & {
+    asChild?: boolean;
+    style?: react_native.StyleProp<react_native.TextStyle>;
+    children?: react.ReactNode;
+} & Omit<TextStyleProps, "pointerEvents" | "disabled" | "style" | "children" | "id" | "onLayout" | "testID" | "nativeID" | "accessible" | "accessibilityActions" | "accessibilityLabel" | "aria-label" | "accessibilityRole" | "accessibilityState" | "aria-busy" | "aria-checked" | "aria-disabled" | "aria-expanded" | "aria-selected" | "accessibilityHint" | "accessibilityValue" | "aria-valuemax" | "aria-valuemin" | "aria-valuenow" | "aria-valuetext" | "onAccessibilityAction" | "importantForAccessibility" | "aria-hidden" | "aria-modal" | "role" | "accessibilityLabelledBy" | "aria-labelledby" | "accessibilityLiveRegion" | "aria-live" | "screenReaderFocusable" | "accessibilityElementsHidden" | "accessibilityViewIsModal" | "onAccessibilityEscape" | "onAccessibilityTap" | "onMagicTap" | "accessibilityIgnoresInvertColors" | "accessibilityLanguage" | "accessibilityShowsLargeContentViewer" | "accessibilityLargeContentTitle" | "accessibilityRespondsToUserInteraction" | "onPress" | "onPressIn" | "onPressOut" | "onLongPress" | "pressRetentionOffset" | "asChild" | "allowFontScaling" | "ellipsizeMode" | "lineBreakMode" | "numberOfLines" | "onTextLayout" | "maxFontSizeMultiplier" | "minimumFontScale" | "adjustsFontSizeToFit" | "dynamicTypeRamp" | "suppressHighlighting" | "lineBreakStrategyIOS" | "selectable" | "selectionColor" | "textBreakStrategy" | "dataDetectorType" | "android_hyphenationFrequency"> & react.RefAttributes<Text>>;
+
+/** Every role produces the same one slot, so the recipe's style functions share a shape. */
+type StyleFn = (theme: XAUITheme) => Record<TypographySlot, TextStyle>;
+/**
+ * There is no `base`. A text node's defaults are React Native's own, and restating them
+ * here would only give them a second place to drift from.
+ */
+declare const typographyRecipe: Recipe<"root", TypographyVariant, {
+    readonly variant: Record<TypographyVariant, StyleFn>;
+}>;
+
+export { TextSpan, type TextSpanProps, Typography, type TypographyProps, type TypographySlot, type TypographyVariant, typographyRecipe };

package/dist/components/typography/index.d.ts

@@ -0,0 +1,116 @@
+import * as react from 'react';
+import { ReactNode } from 'react';
+import * as react_native from 'react-native';
+import { TextProps, StyleProp, TextStyle, Text } from 'react-native';
+import { T as TextStyleProps } from '../../style-props.type-CfnoGEP7.js';
+import { R as Recipe } from '../../create-recipe-BdVd2ffi.js';
+import { X as XAUITheme } from '../../theme.type-C2gNHpEx.js';
+
+/**
+ * The ten roles, aligned with HeroUI Native's `text` — six headings, three body steps and
+ * inline code. Each one fixes **size, line height, weight and family together**, which is
+ * what removes the separate `size` and `weight` props the legacy component carried, and
+ * with them the illegal combinations they allowed: a heading in `weight="light"`, a
+ * caption in `lg`.
+ *
+ * `h1`–`h6` name a level, not an HTML tag — React Native has no document outline, so the
+ * number is the step on the scale and nothing more. Announcing a heading to a screen
+ * reader stays explicit: `accessibilityRole="header"`.
+ */
+type TypographyVariant = 'h1' | 'h2' | 'h3' | 'h4' | 'h5' | 'h6' | 'body' | 'body-sm' | 'body-xs' | 'code';
+type TypographySlot = 'root';
+type TypographyOwnProps = {
+    /** The role. It fixes size, line height, weight and family at once. */
+    variant?: TypographyVariant;
+    /**
+     * A raw tint (`'#7c3aed'`), never a token (R7). In a text component there is only one
+     * thing to tint, so it lands on the text itself.
+     */
+    color?: string;
+    /** R12 — the child element becomes the text node, keeping this variant's style. */
+    asChild?: boolean;
+    style?: StyleProp<TextStyle>;
+    children?: ReactNode;
+};
+/**
+ * R14 — the role's own vocabulary, then every `TextStyle` key it does not already claim.
+ * `color` is the component's, so it keeps its R7 meaning here rather than becoming the
+ * style key of the same name; `fontSize` and `fontWeight` stay available, which is how a
+ * one-off deviation is written without inventing a prop for it.
+ */
+type TypographyProps = Omit<TextProps, 'style'> & TypographyOwnProps & Omit<TextStyleProps, keyof TypographyOwnProps | keyof TextProps>;
+type TextSpanOwnProps = {
+    /** R12 — the child element becomes the span. */
+    asChild?: boolean;
+    style?: StyleProp<TextStyle>;
+    children?: ReactNode;
+};
+type TextSpanProps = Omit<TextProps, 'style'> & TextSpanOwnProps & Omit<TextStyleProps, keyof TextSpanOwnProps | keyof TextProps>;
+
+/**
+ * Text, by the role it plays.
+ *
+ * ```tsx
+ * <Typography variant="heading-lg">Projets</Typography>
+ * <Typography>Trois en cours, un archivé.</Typography>
+ * <Typography variant="caption">Mis à jour il y a deux minutes</Typography>
+ * ```
+ *
+ * **One node, and no slots.** A paragraph is a `Text`; there is nothing inside it for the
+ * component to publish. Styling a fragment of it is `TextSpan`'s job, not a slot of this
+ * one — React Native already makes a nested `Text` inherit from its parent, so a span
+ * needs no context, no resolved style and nothing from here. This component would only be
+ * duplicating a mechanism the platform ships.
+ *
+ * **The role fixes size, line height, weight and family together**, which is why there is
+ * no `size` and no `weight` prop: those axes are not free to combine. A one-off deviation
+ * is a style prop — `fontSize={17}` — said plainly rather than dressed as vocabulary.
+ *
+ * Alignment likewise has no prop of its own: `textAlign` is a `TextStyle` key, so R14
+ * already exposes it, and the caller writes the value React Native understands instead of
+ * a translation layer this component would have to keep honest.
+ */
+declare const Typography: react.ForwardRefExoticComponent<Omit<react_native.TextProps, "style"> & {
+    variant?: TypographyVariant;
+    color?: string;
+    asChild?: boolean;
+    style?: react_native.StyleProp<react_native.TextStyle>;
+    children?: react.ReactNode;
+} & Omit<TextStyleProps, "color" | "pointerEvents" | "disabled" | "style" | "children" | "id" | "onLayout" | "testID" | "nativeID" | "accessible" | "accessibilityActions" | "accessibilityLabel" | "aria-label" | "accessibilityRole" | "accessibilityState" | "aria-busy" | "aria-checked" | "aria-disabled" | "aria-expanded" | "aria-selected" | "accessibilityHint" | "accessibilityValue" | "aria-valuemax" | "aria-valuemin" | "aria-valuenow" | "aria-valuetext" | "onAccessibilityAction" | "importantForAccessibility" | "aria-hidden" | "aria-modal" | "role" | "accessibilityLabelledBy" | "aria-labelledby" | "accessibilityLiveRegion" | "aria-live" | "screenReaderFocusable" | "accessibilityElementsHidden" | "accessibilityViewIsModal" | "onAccessibilityEscape" | "onAccessibilityTap" | "onMagicTap" | "accessibilityIgnoresInvertColors" | "accessibilityLanguage" | "accessibilityShowsLargeContentViewer" | "accessibilityLargeContentTitle" | "accessibilityRespondsToUserInteraction" | "onPress" | "onPressIn" | "onPressOut" | "onLongPress" | "pressRetentionOffset" | "asChild" | "variant" | "allowFontScaling" | "ellipsizeMode" | "lineBreakMode" | "numberOfLines" | "onTextLayout" | "maxFontSizeMultiplier" | "minimumFontScale" | "adjustsFontSizeToFit" | "dynamicTypeRamp" | "suppressHighlighting" | "lineBreakStrategyIOS" | "selectable" | "selectionColor" | "textBreakStrategy" | "dataDetectorType" | "android_hyphenationFrequency"> & react.RefAttributes<Text>>;
+
+/**
+ * A fragment of text, styled apart from the text around it.
+ *
+ * ```tsx
+ * <Typography>
+ *   Supprimer <TextSpan fontWeight="600">trois projets</TextSpan> définitivement.
+ * </Typography>
+ * ```
+ *
+ * **It is a bare React Native `Text`, and that is the whole design.** Nesting a `Text`
+ * inside a `Text` already inherits the parent's font, size, weight and colour on both
+ * platforms — so a span needs no context to read, no role to resolve and no provider
+ * above it. The legacy component published a `TextSpanContext` to carry that inheritance
+ * by hand; it was reimplementing the platform, and it is gone.
+ *
+ * What is left is R14 and nothing else: every `TextStyle` key as a prop, and `style` after
+ * them. There is no `variant` here on purpose — a span that names a role would be a
+ * `Typography`, and nesting one of those is how you change role mid-sentence.
+ */
+declare const TextSpan: react.ForwardRefExoticComponent<Omit<react_native.TextProps, "style"> & {
+    asChild?: boolean;
+    style?: react_native.StyleProp<react_native.TextStyle>;
+    children?: react.ReactNode;
+} & Omit<TextStyleProps, "pointerEvents" | "disabled" | "style" | "children" | "id" | "onLayout" | "testID" | "nativeID" | "accessible" | "accessibilityActions" | "accessibilityLabel" | "aria-label" | "accessibilityRole" | "accessibilityState" | "aria-busy" | "aria-checked" | "aria-disabled" | "aria-expanded" | "aria-selected" | "accessibilityHint" | "accessibilityValue" | "aria-valuemax" | "aria-valuemin" | "aria-valuenow" | "aria-valuetext" | "onAccessibilityAction" | "importantForAccessibility" | "aria-hidden" | "aria-modal" | "role" | "accessibilityLabelledBy" | "aria-labelledby" | "accessibilityLiveRegion" | "aria-live" | "screenReaderFocusable" | "accessibilityElementsHidden" | "accessibilityViewIsModal" | "onAccessibilityEscape" | "onAccessibilityTap" | "onMagicTap" | "accessibilityIgnoresInvertColors" | "accessibilityLanguage" | "accessibilityShowsLargeContentViewer" | "accessibilityLargeContentTitle" | "accessibilityRespondsToUserInteraction" | "onPress" | "onPressIn" | "onPressOut" | "onLongPress" | "pressRetentionOffset" | "asChild" | "allowFontScaling" | "ellipsizeMode" | "lineBreakMode" | "numberOfLines" | "onTextLayout" | "maxFontSizeMultiplier" | "minimumFontScale" | "adjustsFontSizeToFit" | "dynamicTypeRamp" | "suppressHighlighting" | "lineBreakStrategyIOS" | "selectable" | "selectionColor" | "textBreakStrategy" | "dataDetectorType" | "android_hyphenationFrequency"> & react.RefAttributes<Text>>;
+
+/** Every role produces the same one slot, so the recipe's style functions share a shape. */
+type StyleFn = (theme: XAUITheme) => Record<TypographySlot, TextStyle>;
+/**
+ * There is no `base`. A text node's defaults are React Native's own, and restating them
+ * here would only give them a second place to drift from.
+ */
+declare const typographyRecipe: Recipe<"root", TypographyVariant, {
+    readonly variant: Record<TypographyVariant, StyleFn>;
+}>;
+
+export { TextSpan, type TextSpanProps, Typography, type TypographyProps, type TypographySlot, type TypographyVariant, typographyRecipe };

package/dist/components/typography/index.js

@@ -0,0 +1,15 @@
+import {
+  TextSpan,
+  Typography,
+  typographyRecipe
+} from "../../chunk-NYRXUGVL.js";
+import "../../chunk-4GTAZM2C.js";
+import "../../chunk-A3EGFI6T.js";
+import "../../chunk-E2CWBQTV.js";
+import "../../chunk-URSKA2VR.js";
+import "../../chunk-GGW42MY4.js";
+export {
+  TextSpan,
+  Typography,
+  typographyRecipe
+};

package/dist/components/view/index.cjs

@@ -0,0 +1,17 @@
+"use strict";Object.defineProperty(exports, "__esModule", {value: true});
+
+
+
+
+
+var _chunkXFSW3ZNIcjs = require('../../chunk-XFSW3ZNI.cjs');
+require('../../chunk-ZP2E2H2G.cjs');
+require('../../chunk-GLGU2WFL.cjs');
+require('../../chunk-MC7SY2QH.cjs');
+
+
+
+
+
+
+exports.Column = _chunkXFSW3ZNIcjs.Column; exports.Grid = _chunkXFSW3ZNIcjs.Grid; exports.Row = _chunkXFSW3ZNIcjs.Row; exports.Stack = _chunkXFSW3ZNIcjs.Stack; exports.useGrid = _chunkXFSW3ZNIcjs.useGrid;