import type { ControlSize } from "@charcuterie/tokens";
import type { ComponentPropsWithRef, ReactNode } from "react";
/**
 * @deprecated Part of the deprecated native `Select`. The
 * replacement shape is `PickerOption` / `ListboxItem`, whose
 * `label` is a `ReactNode` rather than a `string`.
 */
export type SelectOption = {
    isDisabled?: boolean;
    label: string;
    value: string;
};
/**
 * @deprecated Part of the deprecated native `Select`. `Listbox`
 * has **no `<optgroup>` equivalent**, so a grouped picker is the
 * one shape this deprecation has no replacement for — an app that
 * needs one is a change to `Listbox`, not a reason to keep
 * reaching for the native control.
 */
export type SelectOptionGroup = {
    label: string;
    options: readonly SelectOption[];
};
/** @deprecated Part of the deprecated native `Select`. */
export type SelectItem = SelectOption | SelectOptionGroup;
/**
 * @deprecated Part of the deprecated native `Select` — see the
 * component's docblock. `PickerProps` is the replacement.
 *
 * The HTML attributes are passed through, and that is not
 * convenience — it is what makes the `Field` slot work at all.
 *
 * `Field` clones `id`, `aria-describedby`, `aria-invalid` and
 * `required` onto whatever control it is given. A component with a
 * closed prop list **silently drops all four**: the field renders,
 * the label still points at nothing, and every assertion about the
 * control's own props passes because they never arrived. Found by
 * the one test that asked the control what it had been handed.
 *
 * Same arrangement as `Button`, for the same reason.
 */
export type SelectProps = Omit<ComponentPropsWithRef<"select">, "disabled" | "onChange" | "size" | "value"> & {
    /**
     * Goes on the **wrapper**, which is the box a caller means when
     * they size a control. See the component docblock — the chevron
     * is positioned against that wrapper, so a width anywhere else
     * leaves it behind.
     */
    className?: string;
    /**
     * The escape hatch for the inner `<select>` itself, for the
     * things that genuinely are not the outer box: `font-mono` on the
     * option text, a `text-*` override, a `bg-*`.
     *
     * Sizing does **not** belong here. The inner element is `w-full`
     * and a width on it desynchronises it from the wrapper the
     * chevron is pinned to, which is the whole of #112.
     */
    controlClassName?: string;
    isDisabled?: boolean;
    /**
     * The accessible name, when this is **not** inside a `Field`. A
     * `<select>` with neither a `<label for>` nor an `aria-label` is
     * announced as "combobox" and is unfindable by
     * `getByRole("combobox", { name })` — twelve of the fleet's
     * fourteen native selects are in exactly that state.
     */
    label?: string;
    onChange?: (value: string) => void;
    /**
     * `readonly`, because a caller's list is usually a constant and
     * TypeScript will not hand a `readonly` array to a mutable
     * parameter — image-viewer hit `TS4104` on an `as const` options
     * table and had to spread a copy at every call. This component
     * only ever `.map`s over it, so demanding a mutable array was
     * asking for a permission it never uses.
     */
    options: readonly SelectItem[];
    /**
     * A disabled first entry, not a real option. Reads as a prompt to
     * a sighted user and cannot be submitted, which is what a
     * placeholder should mean — unlike an empty-valued option, which
     * is selectable and silently posts "".
     */
    placeholder?: string;
    size?: ControlSize;
    /** **Initial** only, like every other value prop in this library. */
    value?: string;
};
/**
 * @deprecated Reach for `Picker` — a `Listbox` with the trigger
 * already attached, and a near drop-in for this component
 * (`label`, `options`, `value`, `onChange`) — or `Combobox` when
 * the list is long enough to want typing.
 *
 * A styled native `<select>`, kept only so the call sites that
 * already have one keep compiling while they are converted.
 *
 * ### Deprecated 2026-08-20, and the platform hatch is closed
 *
 * The 2026-08-10 record demoted this to a stated-reason exception
 * and named four cases where the platform behaviour is the
 * feature: the mobile wheel picker, autofill, `:invalid`, and a
 * form that posts with no JS. **None of them has ever applied to
 * an app in this fleet**, and the exception is what agents kept
 * reading as permission — so the exception is gone. A new native
 * `Select` is a new decision with the reason written down, not a
 * call-site choice.
 *
 * The objection is that the popup is painted by the OS. No token,
 * no class and no amount of `appearance-none` reaches inside it,
 * so a fleet with any of these in it has two focus treatments, two
 * hover treatments and two keyboard feels — which is the thing the
 * library exists to stop.
 *
 * Everything below is how the component works, for the call sites
 * still on it. It is not a reason to add one.
 *
 * ### Sizing: `className` is the wrapper, `controlClassName` is the select
 *
 * This renders a wrapper around the native `<select>` because the
 * chevron has to live somewhere, and the chevron is positioned
 * against that wrapper. `className` therefore lands on the wrapper
 * and the `<select>` stays `w-full` inside it, so
 * `className="w-44"` means "this control is 176px" — chevron
 * included — which is what a caller writing a width already assumes.
 *
 * Before this, `className` went to the inner element only. The
 * wrapper stayed `w-full`, the chevron stayed at *its* edge, and
 * mux-magic's rules builder measured the gap at **869.6px** with the
 * control's own text clipping beside it. The width never worked;
 * `ui@2.16.0`'s `tailwind-merge` only made half of it work and made
 * the other half visible.
 *
 * For the genuinely-inner things — `font-mono` on the option text, a
 * `bg-*` — there is `controlClassName`.
 *
 * ### There is no state kind here, and that is the finding
 *
 * Every other interactive component in this package owns its state
 * through `@charcuterie/logic`. This one owns none, because the
 * platform already does: a `<select>` holds the chosen option in the
 * DOM, and putting a `useSinglePicker` beside it would create the
 * exact conflict the state layer exists to prevent — two things
 * believing they hold `value`, which is the Radix argument from
 * `Popover` pointed at ourselves. So `value` seeds `defaultValue`
 * and changes are reported outward.
 *
 * The consequence worth knowing: **`Select` is uncontrolled and
 * `Tabs` is not**, and a reader should be able to tell why without
 * asking. A tab bar's selection has no DOM representation, so
 * something has to hold it; a select's does.
 *
 * ### Native, and what that rules out
 *
 * A `<select>` cannot render a rich option — an icon, two lines, a
 * badge — and cannot filter. mux-magic has six controls that need
 * one of those (`CommandPicker`, `PathPicker`, `LinkPicker`,
 * `EnumPicker`, `AssFieldPicker`, `RenameTargetPicker`), and every
 * one of them is a **`Combobox`**: a text input that filters a
 * listbox. That is a different pattern with a different ARIA
 * contract, it is P2 in the plan, and building a bare `Listbox`
 * here that none of the six could adopt would have shipped a
 * component with no caller.
 *
 * What native buys, and what a hand-rolled listbox has to rebuild
 * from nothing: type-ahead, Home/End, PageUp/PageDown, the mobile
 * wheel picker, form submission, `:invalid`, and autofill.
 */
export declare const Select: ({ className, controlClassName, isDisabled, label, onChange, options, placeholder, size, value, ...selectProps }: SelectProps) => ReactNode;
//# sourceMappingURL=Select.d.ts.map