@xaui/native 0.9.1-alpha.9 → 0.9.1-alpha.90

package/dist/components/search-field/index.js

@@ -0,0 +1,35 @@
+import {
+  SearchField,
+  SearchFieldClear,
+  SearchFieldField,
+  SearchFieldIcon,
+  SearchFieldRoot,
+  SearchIcon,
+  searchFieldRecipe,
+  useSearchField
+} from "../../chunk-W6TFYAEF.js";
+import "../../chunk-3CPLJJWX.js";
+import "../../chunk-5YZUYSV7.js";
+import "../../chunk-43S673KF.js";
+import "../../chunk-4BAKKBHJ.js";
+import "../../chunk-XZ42OWKC.js";
+import "../../chunk-423RQBOX.js";
+import "../../chunk-JN6IRT2M.js";
+import "../../chunk-WFZDAXDI.js";
+import "../../chunk-DKVXTMIJ.js";
+import "../../chunk-3Q42X6EQ.js";
+import "../../chunk-TTZOIXKE.js";
+import "../../chunk-36PRYGAM.js";
+import "../../chunk-EGLLDKN6.js";
+import "../../chunk-Z6JBWRPL.js";
+import "../../chunk-M63GFNKV.js";
+export {
+  SearchField,
+  SearchFieldClear,
+  SearchFieldField,
+  SearchFieldIcon,
+  SearchFieldRoot,
+  SearchIcon,
+  searchFieldRecipe,
+  useSearchField
+};

package/dist/components/search-field/search-field-clear.d.cts

@@ -0,0 +1,30 @@
+import type { View } from 'react-native';
+import type { SearchFieldClearProps } from './search-field.type';
+/**
+ * The cross that empties the box:
+ *
+ * ```tsx
+ * <FieldGroup>
+ *   <SearchField.Field placeholder="Search…" />
+ *   <SearchField.Clear accessibilityLabel="Clear the search" />
+ * </FieldGroup>
+ * ```
+ *
+ * **It renders nothing while the box is empty**, which is the one place this component
+ * departs from the library's rule that a slot rendering nothing is a slot you cannot debug.
+ * A cross that clears an empty field is a target that does nothing, and every search box
+ * ever drawn hides it — the alternative is the caller writing that condition at the call
+ * site, in the middle of their JSX, on every screen with a search on it.
+ *
+ * **And it is its own `FieldGroup.Suffix`**, unlike `SearchField.Icon`, which the caller
+ * wraps in a `Prefix` the way every other decorator in the library is wrapped. That is the
+ * price of being conditional: a decorator is inset by the field's own padding, so an empty
+ * one is still two paddings wide and the field would go on clearing room for a cross that
+ * is not there. Owning the edge is what lets the whole decorator go with the cross.
+ *
+ * Everything else is the shared close button's: it owns its press state, because the cross
+ * and the field under it are different targets; it grows its target with `hitSlop` rather
+ * than growing the glyph; and with no children it draws its own cross from two bars a
+ * quarter turn apart.
+ */
+export declare const SearchFieldClear: import("react").ForwardRefExoticComponent<SearchFieldClearProps & import("react").RefAttributes<View>>;

package/dist/components/search-field/search-field-clear.d.ts

@@ -0,0 +1,30 @@
+import type { View } from 'react-native';
+import type { SearchFieldClearProps } from './search-field.type';
+/**
+ * The cross that empties the box:
+ *
+ * ```tsx
+ * <FieldGroup>
+ *   <SearchField.Field placeholder="Search…" />
+ *   <SearchField.Clear accessibilityLabel="Clear the search" />
+ * </FieldGroup>
+ * ```
+ *
+ * **It renders nothing while the box is empty**, which is the one place this component
+ * departs from the library's rule that a slot rendering nothing is a slot you cannot debug.
+ * A cross that clears an empty field is a target that does nothing, and every search box
+ * ever drawn hides it — the alternative is the caller writing that condition at the call
+ * site, in the middle of their JSX, on every screen with a search on it.
+ *
+ * **And it is its own `FieldGroup.Suffix`**, unlike `SearchField.Icon`, which the caller
+ * wraps in a `Prefix` the way every other decorator in the library is wrapped. That is the
+ * price of being conditional: a decorator is inset by the field's own padding, so an empty
+ * one is still two paddings wide and the field would go on clearing room for a cross that
+ * is not there. Owning the edge is what lets the whole decorator go with the cross.
+ *
+ * Everything else is the shared close button's: it owns its press state, because the cross
+ * and the field under it are different targets; it grows its target with `hitSlop` rather
+ * than growing the glyph; and with no children it draws its own cross from two bars a
+ * quarter turn apart.
+ */
+export declare const SearchFieldClear: import("react").ForwardRefExoticComponent<SearchFieldClearProps & import("react").RefAttributes<View>>;

package/dist/components/search-field/search-field-field.d.cts

@@ -0,0 +1,18 @@
+import type { TextInput } from 'react-native';
+import type { SearchFieldFieldProps } from './search-field.type';
+/**
+ * The box, read as a query.
+ *
+ * It **is** `TextField.Field` — the same node, the same focus plumbing, the same
+ * `isInvalid` — with the value, the keystroke and the return key taken over by the root's
+ * query, and the variant's fill laid over the box the `TextField` resolved.
+ *
+ * The three defaults are what a search box is: no autocorrect and no leading capital,
+ * because a query is not a sentence, and a keyboard whose return key says "search". All
+ * three are the caller's to override — a field searching a list of proper nouns wants its
+ * capitals back.
+ *
+ * Inside a `FieldGroup` it clears the two decorators by the width they measured, exactly
+ * as `FieldGroup.Field` does, which is how the magnifier and the cross get their room.
+ */
+export declare const SearchFieldField: import("react").ForwardRefExoticComponent<SearchFieldFieldProps & import("react").RefAttributes<TextInput>>;

package/dist/components/search-field/search-field-field.d.ts

@@ -0,0 +1,18 @@
+import type { TextInput } from 'react-native';
+import type { SearchFieldFieldProps } from './search-field.type';
+/**
+ * The box, read as a query.
+ *
+ * It **is** `TextField.Field` — the same node, the same focus plumbing, the same
+ * `isInvalid` — with the value, the keystroke and the return key taken over by the root's
+ * query, and the variant's fill laid over the box the `TextField` resolved.
+ *
+ * The three defaults are what a search box is: no autocorrect and no leading capital,
+ * because a query is not a sentence, and a keyboard whose return key says "search". All
+ * three are the caller's to override — a field searching a list of proper nouns wants its
+ * capitals back.
+ *
+ * Inside a `FieldGroup` it clears the two decorators by the width they measured, exactly
+ * as `FieldGroup.Field` does, which is how the magnifier and the cross get their room.
+ */
+export declare const SearchFieldField: import("react").ForwardRefExoticComponent<SearchFieldFieldProps & import("react").RefAttributes<TextInput>>;

package/dist/components/search-field/search-field-icon.d.cts

@@ -0,0 +1,23 @@
+import type { SearchFieldIconProps } from './search-field.type';
+/**
+ * The magnifier, at the field's own scale and in the placeholder's grey:
+ *
+ * ```tsx
+ * <FieldGroup.Prefix isDecorative>
+ *   <SearchField.Icon />
+ * </FieldGroup.Prefix>
+ * ```
+ *
+ * It **is** `FieldGroup.Icon` with a mark of its own, which is what makes the size and the
+ * colour follow the `TextField`'s `size` and theme without being told either — and what
+ * makes `as` work, for a project whose icon set already has a glass in the right weight.
+ *
+ * The built-in one is drawn with `react-native-svg`, an **optional** peer of this package.
+ * A project that has installed no icon set still gets a search mark; one that would rather
+ * not carry the peer passes `as` — the import is at the top of this module, so the peer is
+ * needed either way, exactly as it is for the `Select`'s chevron.
+ */
+export declare function SearchFieldIcon({ as, size, color, }: SearchFieldIconProps): import("react").JSX.Element;
+export declare namespace SearchFieldIcon {
+    var displayName: string;
+}

package/dist/components/search-field/search-field-icon.d.ts

@@ -0,0 +1,23 @@
+import type { SearchFieldIconProps } from './search-field.type';
+/**
+ * The magnifier, at the field's own scale and in the placeholder's grey:
+ *
+ * ```tsx
+ * <FieldGroup.Prefix isDecorative>
+ *   <SearchField.Icon />
+ * </FieldGroup.Prefix>
+ * ```
+ *
+ * It **is** `FieldGroup.Icon` with a mark of its own, which is what makes the size and the
+ * colour follow the `TextField`'s `size` and theme without being told either — and what
+ * makes `as` work, for a project whose icon set already has a glass in the right weight.
+ *
+ * The built-in one is drawn with `react-native-svg`, an **optional** peer of this package.
+ * A project that has installed no icon set still gets a search mark; one that would rather
+ * not carry the peer passes `as` — the import is at the top of this module, so the peer is
+ * needed either way, exactly as it is for the `Select`'s chevron.
+ */
+export declare function SearchFieldIcon({ as, size, color, }: SearchFieldIconProps): import("react").JSX.Element;
+export declare namespace SearchFieldIcon {
+    var displayName: string;
+}

package/dist/components/search-field/search-field.context.d.cts

@@ -0,0 +1,7 @@
+import type { SearchFieldContextValue } from './search-field.type';
+/**
+ * R10 — `useSearchField` is exported so a third party can write its own slot against the
+ * query and the resolved styles the built-in ones read: a voice button beside the cross, a
+ * result count inside the box. Outside a `<SearchField>` it throws by name.
+ */
+export declare const SearchFieldProvider: import("react").Provider<SearchFieldContextValue | null>, useSearchField: () => SearchFieldContextValue;

package/dist/components/search-field/search-field.context.d.ts

@@ -0,0 +1,7 @@
+import type { SearchFieldContextValue } from './search-field.type';
+/**
+ * R10 — `useSearchField` is exported so a third party can write its own slot against the
+ * query and the resolved styles the built-in ones read: a voice button beside the cross, a
+ * result count inside the box. Outside a `<SearchField>` it throws by name.
+ */
+export declare const SearchFieldProvider: import("react").Provider<SearchFieldContextValue | null>, useSearchField: () => SearchFieldContextValue;

package/dist/components/search-field/search-field.d.cts

@@ -0,0 +1,50 @@
+import type { View } from 'react-native';
+/**
+ * A query, with the mark that says so and the cross that takes it back.
+ *
+ * ```tsx
+ * <SearchField onValueChange={setQuery}>
+ *   <SearchField.Label>Find products</SearchField.Label>
+ *   <FieldGroup>
+ *     <FieldGroup.Prefix isDecorative>
+ *       <SearchField.Icon />
+ *     </FieldGroup.Prefix>
+ *     <SearchField.Field placeholder="Search…" />
+ *     <SearchField.Clear accessibilityLabel="Clear the search" />
+ *   </FieldGroup>
+ *   <SearchField.Description>Search by name, category, or SKU</SearchField.Description>
+ * </SearchField>
+ * ```
+ *
+ * **It is a `TextField`.** The root below is the `TextField`'s: the same `size`, `radius`,
+ * `color`, `labelPlacement`, `isInvalid` and `isDisabled`, and `SearchField.Label`,
+ * `.Description` and `.Error` **are** its slots — the same components, not wrappers. The
+ * `MaskField`'s and the `NumberField`'s arrangement exactly.
+ *
+ * **What differs is the fill and the two marks.** There are two variants rather than four
+ * — a flat `primary` and a soft `secondary`, both without the `field` shadow — because a
+ * search box sits alone on a screen or on a surface, and those are the two things it has to
+ * be. The `TextField` underneath is handed `tertiary`, which is the edge and the focus
+ * colour with no fill of their own; the fill goes over it.
+ *
+ * **Typing and searching are two callbacks, on purpose.** `onValueChange` is every
+ * keystroke, which is what a list filtered in memory reads; `onSearch` is the search key on
+ * the keyboard, which is what a query costing a request waits for. A field that fired one
+ * callback for both would make the caller debounce to tell them apart.
+ *
+ * For a query that opens a list of suggestions, that is `Autocomplete`; for one that picks
+ * from a closed set, `Combobox`.
+ */
+export declare const SearchFieldRoot: import("react").ForwardRefExoticComponent<{
+    variant?: import("./search-field.type").SearchFieldVariant;
+    value?: string;
+    defaultValue?: string;
+    onValueChange?: (query: string) => void;
+    onSearch?: (query: string) => void;
+} & Omit<import("..").TextFieldProps, keyof {
+    variant?: import("./search-field.type").SearchFieldVariant;
+    value?: string;
+    defaultValue?: string;
+    onValueChange?: (query: string) => void;
+    onSearch?: (query: string) => void;
+}> & import("react").RefAttributes<View>>;

package/dist/components/search-field/search-field.d.ts

@@ -0,0 +1,50 @@
+import type { View } from 'react-native';
+/**
+ * A query, with the mark that says so and the cross that takes it back.
+ *
+ * ```tsx
+ * <SearchField onValueChange={setQuery}>
+ *   <SearchField.Label>Find products</SearchField.Label>
+ *   <FieldGroup>
+ *     <FieldGroup.Prefix isDecorative>
+ *       <SearchField.Icon />
+ *     </FieldGroup.Prefix>
+ *     <SearchField.Field placeholder="Search…" />
+ *     <SearchField.Clear accessibilityLabel="Clear the search" />
+ *   </FieldGroup>
+ *   <SearchField.Description>Search by name, category, or SKU</SearchField.Description>
+ * </SearchField>
+ * ```
+ *
+ * **It is a `TextField`.** The root below is the `TextField`'s: the same `size`, `radius`,
+ * `color`, `labelPlacement`, `isInvalid` and `isDisabled`, and `SearchField.Label`,
+ * `.Description` and `.Error` **are** its slots — the same components, not wrappers. The
+ * `MaskField`'s and the `NumberField`'s arrangement exactly.
+ *
+ * **What differs is the fill and the two marks.** There are two variants rather than four
+ * — a flat `primary` and a soft `secondary`, both without the `field` shadow — because a
+ * search box sits alone on a screen or on a surface, and those are the two things it has to
+ * be. The `TextField` underneath is handed `tertiary`, which is the edge and the focus
+ * colour with no fill of their own; the fill goes over it.
+ *
+ * **Typing and searching are two callbacks, on purpose.** `onValueChange` is every
+ * keystroke, which is what a list filtered in memory reads; `onSearch` is the search key on
+ * the keyboard, which is what a query costing a request waits for. A field that fired one
+ * callback for both would make the caller debounce to tell them apart.
+ *
+ * For a query that opens a list of suggestions, that is `Autocomplete`; for one that picks
+ * from a closed set, `Combobox`.
+ */
+export declare const SearchFieldRoot: import("react").ForwardRefExoticComponent<{
+    variant?: import("./search-field.type").SearchFieldVariant;
+    value?: string;
+    defaultValue?: string;
+    onValueChange?: (query: string) => void;
+    onSearch?: (query: string) => void;
+} & Omit<import("..").TextFieldProps, keyof {
+    variant?: import("./search-field.type").SearchFieldVariant;
+    value?: string;
+    defaultValue?: string;
+    onValueChange?: (query: string) => void;
+    onSearch?: (query: string) => void;
+}> & import("react").RefAttributes<View>>;

package/dist/components/search-field/search-field.recipe.d.cts

@@ -0,0 +1,11 @@
+import type { SlotStyles } from '../../system/recipe';
+import type { XAUITheme } from '../../theme/theme.type';
+import type { SearchFieldSlot, SearchFieldVariant } from './search-field.type';
+export declare const searchFieldRecipe: import("../..").Recipe<"field" | "clear" | "clearGlyph", SearchFieldVariant, {
+    readonly size: {
+        readonly xs: (theme: XAUITheme) => SlotStyles<SearchFieldSlot>;
+        readonly sm: (theme: XAUITheme) => SlotStyles<SearchFieldSlot>;
+        readonly md: (theme: XAUITheme) => SlotStyles<SearchFieldSlot>;
+        readonly lg: (theme: XAUITheme) => SlotStyles<SearchFieldSlot>;
+    };
+}>;

package/dist/components/search-field/search-field.recipe.d.ts

@@ -0,0 +1,11 @@
+import type { SlotStyles } from '../../system/recipe';
+import type { XAUITheme } from '../../theme/theme.type';
+import type { SearchFieldSlot, SearchFieldVariant } from './search-field.type';
+export declare const searchFieldRecipe: import("../..").Recipe<"field" | "clear" | "clearGlyph", SearchFieldVariant, {
+    readonly size: {
+        readonly xs: (theme: XAUITheme) => SlotStyles<SearchFieldSlot>;
+        readonly sm: (theme: XAUITheme) => SlotStyles<SearchFieldSlot>;
+        readonly md: (theme: XAUITheme) => SlotStyles<SearchFieldSlot>;
+        readonly lg: (theme: XAUITheme) => SlotStyles<SearchFieldSlot>;
+    };
+}>;

package/dist/components/search-field/search-field.type.d.cts

@@ -0,0 +1,76 @@
+import type { ComponentType } from 'react';
+import type { StyleProp, TextStyle, ViewStyle } from 'react-native';
+import type { CloseButtonBaseProps } from '../../system/close-button';
+import type { IconComponentProps } from '../../system/icon';
+import type { TextFieldFieldProps, TextFieldProps } from '../text-field';
+export type SearchFieldSlot = 'field' | 'clear' | 'clearGlyph';
+/**
+ * Two, where the `TextField` has four — and they are the two a search box is actually
+ * drawn as:
+ *
+ * - **`primary`** — the `fieldBackground` fill, flat. The `TextField`'s `primary` without
+ *   the `field` shadow: a search box is the one field that usually sits alone on a screen
+ *   rather than in a column of siblings, and there the elevation reads as a card that has
+ *   lost its content rather than as a control.
+ * - **`secondary`** — the `defaultSoft` fill, a neutral wash and no fill of its own weight.
+ *   What a search box takes when it sits *on* a surface — a sheet, a card, a header — where
+ *   a white box would be invisible and a solid grey one would read as disabled.
+ *
+ * `tertiary` and `ghost` are absent rather than narrowed away by accident: a field with no
+ * fill at all cannot be told from the text beside it once the placeholder is gone, and a
+ * search box is found before it is read.
+ */
+export type SearchFieldVariant = 'primary' | 'secondary';
+/**
+ * What the `SearchField` adds to the `TextField` it is. R14 — a name in here is the
+ * component's, so the style prop that shares it is not exposed.
+ */
+type SearchFieldOwnProps = {
+    /** The fill. Two, and `primary` is the default. */
+    variant?: SearchFieldVariant;
+    /** The query, controlled. Leave it unset and the field keeps its own. */
+    value?: string;
+    /** The query it starts with, uncontrolled. */
+    defaultValue?: string;
+    /** Every keystroke, and the clear — this is what a field filtering as you type reads. */
+    onValueChange?: (query: string) => void;
+    /**
+     * The search key on the keyboard. It is **not** every keystroke: a query that costs a
+     * request is submitted, and one that filters a list in memory is `onValueChange`.
+     */
+    onSearch?: (query: string) => void;
+};
+export type SearchFieldProps = SearchFieldOwnProps & Omit<TextFieldProps, keyof SearchFieldOwnProps>;
+/**
+ * Everything `TextField.Field` accepts, minus the four props the root owns: the query is
+ * the root's state, and a `value` or an `onChangeText` written here would be writing into
+ * the middle of it.
+ */
+export type SearchFieldFieldProps = Omit<TextFieldFieldProps, 'value' | 'defaultValue' | 'onChangeText' | 'onSubmitEditing'>;
+/** `Icon`'s two levers, plus the mark itself. */
+export type SearchFieldIconProps = {
+    /** Replaces the built-in magnifier with an icon component of your own. */
+    as?: ComponentType<IconComponentProps>;
+    /** Overrides the field's own glyph size. */
+    size?: number;
+    /** A raw value (R7), never a token. Overrides the placeholder grey. */
+    color?: string;
+};
+/**
+ * Everything the shared close button takes, minus what this slot resolves for it. `name`
+ * is `'SearchField.Clear'` and the styles are the recipe's.
+ */
+export type SearchFieldClearProps = Omit<CloseButtonBaseProps, 'name' | 'baseStyle' | 'glyphStyle'>;
+/** R5 — resolved styles and the query, never props for a slot to resolve a second time. */
+export type SearchFieldContextValue = {
+    query: string;
+    onType: (query: string) => void;
+    /** Empties the box and reports it, which is the whole of what `Clear` does. */
+    clear: () => void;
+    submit: () => void;
+    /** The variant's fill, layered over the `TextField`'s own box by `SearchField.Field`. */
+    boxStyle: StyleProp<TextStyle>;
+    clearStyle: StyleProp<ViewStyle>;
+    clearGlyphStyle: StyleProp<ViewStyle>;
+};
+export {};

package/dist/components/search-field/search-field.type.d.ts

@@ -0,0 +1,76 @@
+import type { ComponentType } from 'react';
+import type { StyleProp, TextStyle, ViewStyle } from 'react-native';
+import type { CloseButtonBaseProps } from '../../system/close-button';
+import type { IconComponentProps } from '../../system/icon';
+import type { TextFieldFieldProps, TextFieldProps } from '../text-field';
+export type SearchFieldSlot = 'field' | 'clear' | 'clearGlyph';
+/**
+ * Two, where the `TextField` has four — and they are the two a search box is actually
+ * drawn as:
+ *
+ * - **`primary`** — the `fieldBackground` fill, flat. The `TextField`'s `primary` without
+ *   the `field` shadow: a search box is the one field that usually sits alone on a screen
+ *   rather than in a column of siblings, and there the elevation reads as a card that has
+ *   lost its content rather than as a control.
+ * - **`secondary`** — the `defaultSoft` fill, a neutral wash and no fill of its own weight.
+ *   What a search box takes when it sits *on* a surface — a sheet, a card, a header — where
+ *   a white box would be invisible and a solid grey one would read as disabled.
+ *
+ * `tertiary` and `ghost` are absent rather than narrowed away by accident: a field with no
+ * fill at all cannot be told from the text beside it once the placeholder is gone, and a
+ * search box is found before it is read.
+ */
+export type SearchFieldVariant = 'primary' | 'secondary';
+/**
+ * What the `SearchField` adds to the `TextField` it is. R14 — a name in here is the
+ * component's, so the style prop that shares it is not exposed.
+ */
+type SearchFieldOwnProps = {
+    /** The fill. Two, and `primary` is the default. */
+    variant?: SearchFieldVariant;
+    /** The query, controlled. Leave it unset and the field keeps its own. */
+    value?: string;
+    /** The query it starts with, uncontrolled. */
+    defaultValue?: string;
+    /** Every keystroke, and the clear — this is what a field filtering as you type reads. */
+    onValueChange?: (query: string) => void;
+    /**
+     * The search key on the keyboard. It is **not** every keystroke: a query that costs a
+     * request is submitted, and one that filters a list in memory is `onValueChange`.
+     */
+    onSearch?: (query: string) => void;
+};
+export type SearchFieldProps = SearchFieldOwnProps & Omit<TextFieldProps, keyof SearchFieldOwnProps>;
+/**
+ * Everything `TextField.Field` accepts, minus the four props the root owns: the query is
+ * the root's state, and a `value` or an `onChangeText` written here would be writing into
+ * the middle of it.
+ */
+export type SearchFieldFieldProps = Omit<TextFieldFieldProps, 'value' | 'defaultValue' | 'onChangeText' | 'onSubmitEditing'>;
+/** `Icon`'s two levers, plus the mark itself. */
+export type SearchFieldIconProps = {
+    /** Replaces the built-in magnifier with an icon component of your own. */
+    as?: ComponentType<IconComponentProps>;
+    /** Overrides the field's own glyph size. */
+    size?: number;
+    /** A raw value (R7), never a token. Overrides the placeholder grey. */
+    color?: string;
+};
+/**
+ * Everything the shared close button takes, minus what this slot resolves for it. `name`
+ * is `'SearchField.Clear'` and the styles are the recipe's.
+ */
+export type SearchFieldClearProps = Omit<CloseButtonBaseProps, 'name' | 'baseStyle' | 'glyphStyle'>;
+/** R5 — resolved styles and the query, never props for a slot to resolve a second time. */
+export type SearchFieldContextValue = {
+    query: string;
+    onType: (query: string) => void;
+    /** Empties the box and reports it, which is the whole of what `Clear` does. */
+    clear: () => void;
+    submit: () => void;
+    /** The variant's fill, layered over the `TextField`'s own box by `SearchField.Field`. */
+    boxStyle: StyleProp<TextStyle>;
+    clearStyle: StyleProp<ViewStyle>;
+    clearGlyphStyle: StyleProp<ViewStyle>;
+};
+export {};

package/dist/components/search-field/search-icon.d.cts

@@ -0,0 +1,14 @@
+import type { IconComponentProps } from '../../system/icon';
+/**
+ * The magnifier the library ships, rather than requiring one from the caller: a field
+ * whose whole affordance is "type what you are looking for" is not a search field without
+ * it, and asking for an icon package to draw one glass is a peer dependency for a circle.
+ *
+ * It stays in this folder rather than moving to `system/`: one component draws it. §2 bis
+ * — promotion at the second use, never by anticipation. `SearchField.Icon` takes an `as`
+ * for the project that has its own set.
+ */
+export declare function SearchIcon({ size, color, }: IconComponentProps): import("react").JSX.Element;
+export declare namespace SearchIcon {
+    var displayName: string;
+}

package/dist/components/search-field/search-icon.d.ts

@@ -0,0 +1,14 @@
+import type { IconComponentProps } from '../../system/icon';
+/**
+ * The magnifier the library ships, rather than requiring one from the caller: a field
+ * whose whole affordance is "type what you are looking for" is not a search field without
+ * it, and asking for an icon package to draw one glass is a peer dependency for a circle.
+ *
+ * It stays in this folder rather than moving to `system/`: one component draws it. §2 bis
+ * — promotion at the second use, never by anticipation. `SearchField.Icon` takes an `as`
+ * for the project that has its own set.
+ */
+export declare function SearchIcon({ size, color, }: IconComponentProps): import("react").JSX.Element;
+export declare namespace SearchIcon {
+    var displayName: string;
+}