import type { ControlSize } from "@charcuterie/tokens";
import type { ComponentPropsWithRef, ReactNode } from "react";
export type SpinnerProps = Omit<ComponentPropsWithRef<"span">, "children"> & {
    /**
     * Required by omission of a default that could be wrong.
     * "Loading…" is right for a fetch and wrong for "Ripping disc 3",
     * and the label is the *only* thing a screen-reader user gets —
     * the animation says nothing.
     */
    label?: string;
    isLabelVisible?: boolean;
    size?: ControlSize;
};
/**
 * **Zero of these exist anywhere in the fleet.** Not one repo has a
 * spinner; every app renders bare `"loading…"` text, which is why
 * this is the best effort-to-payoff component in the M3 list.
 *
 * Three things it does that a hand-rolled `animate-spin` does not:
 *
 *  - **It is a live region.** `role="status"` with the label inside
 *    means a screen reader announces the load starting. A bare
 *    rotating `<div>` announces nothing, which is the state of the
 *    art in every repo that renders `"loading…"` into a `<span>`.
 *  - **It stops.** The animation is `--duration-loop-fast`, which
 *    `prefers-reduced-motion` zeroes and
 *    `@charcuterie/ui/styles.css` then switches off outright —
 *    vestibular-triggering motion is the single most common a11y
 *    complaint about spinners, and Tailwind's `animate-spin`
 *    hardcodes 1s past the media query.
 *  - **It leaves a static fallback that still reads.** With motion
 *    off, the ring stays a ring and the label stays a label, so the
 *    component degrades to "there is a thing here, and it says
 *    loading" rather than to nothing.
 */
export declare const Spinner: ({ className, isLabelVisible, label, size, ...spanProps }: SpinnerProps) => ReactNode;
//# sourceMappingURL=Spinner.d.ts.map