@seekalfred/primitives 0.2.0 → 0.3.0

package/dist/scroll-area/scroll-area.d.ts

@@ -0,0 +1,74 @@
+import { ComponentPropsWithoutRef, ReactNode } from "react";
+//#region src/scroll-area/scroll-area.d.ts
+/**
+ * ScrollArea. React Aria has no equivalent, so this is a plain scrolling
+ * div -- and that is the honest answer rather than a shortcut.
+ *
+ * Census: fourteen paths match, thirteen are counted, ELEVEN render
+ * anything, and across them 17 uses. Every single one passes `className`
+ * and nothing else, and 13 of the 17 are a height or flex constraint plus
+ * padding. `ScrollBar` is exported by the legacy and imported by nobody.
+ * `orientation="horizontal"` has zero call sites.
+ *
+ * So there is no styled-scrollbar requirement to port. The legacy pays for
+ * one anyway: Radix injects a `<style>` tag that hides the native
+ * scrollbar, then re-draws it in JavaScript with a ResizeObserver, a
+ * portal-free overlay and a `display: table` content wrapper. That is a
+ * lot of machinery to reproduce a scrollbar, and it is why the legacy
+ * `ScrollArea` cannot be scrolled by keyboard at all.
+ *
+ * Tailwind 4.3.3 ships `scrollbar-width` and `scrollbar-color` utilities
+ * (verified in the installed dist, not assumed), which gets the same look
+ * in three classes and no JavaScript.
+ *
+ * WHAT CANNOT BE STYLED, stated rather than glossed: `scrollbar-color`
+ * takes a thumb and a track colour and nothing else -- no width in pixels,
+ * no radius, no hover state, no margins. `::-webkit-scrollbar` can do
+ * those but is non-standard and Firefox has never supported it. This
+ * component uses the standard properties only.
+ */
+export declare const scrollAreaVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+/**
+ * A scrolling region.
+ *
+ * @example
+ * <ScrollArea label="Chat messages" className="h-64">...</ScrollArea>
+ */
+export interface ScrollAreaProps extends ComponentPropsWithoutRef<"div"> {
+  children?: ReactNode;
+  /**
+   * Names the scrolling region.
+   *
+   * **Required**, and it took a failing test to get here. A focusable
+   * element with no role fails axe `focus-order-semantics`, so the
+   * keyboard fix below cannot ship without a role -- and a role with no
+   * accessible name is a violation of its own. Naming it is the only
+   * combination that is actually correct.
+   *
+   * `role="region"` specifically. `group` was the first attempt -- it is
+   * lighter, since region is a landmark and seventeen landmarks in one app
+   * is noise -- but axe does not accept `group` as an appropriate role for
+   * a focusable element, and it is right: a named region is the role the
+   * ARIA practices name for a scrollable content area, and being able to
+   * jump to it is the point.
+   */
+  label: string;
+  /**
+   * Change this when the contents change, and the region scrolls back to the
+   * top.
+   *
+   * It lives here rather than on the caller because the caller cannot reach
+   * this node: no component in this package exposes a `ref`, and it must not
+   * -- React 18 is a supported peer, where a `ref` passed as a plain prop to a
+   * function component is silently dropped. The scroller owns its own
+   * scrollTop, so the reset belongs with it.
+   *
+   * Sheet forwards its own `scrollResetKey` straight through: going a level
+   * deeper in a panel and landing halfway down the new view is disorienting,
+   * and it is exactly the thing every call site forgets.
+   */
+  scrollResetKey?: string | number;
+}
+export declare function ScrollArea({ className, children, label, scrollResetKey, ...props }: ScrollAreaProps): import("react").JSX.Element;
+//#endregion
+//# sourceMappingURL=scroll-area.d.ts.map

package/dist/scroll-area/scroll-area.js

@@ -0,0 +1,63 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { cva } from "class-variance-authority";
+import { jsx } from "react/jsx-runtime";
+import { useEffect, useRef } from "react";
+//#region src/scroll-area/scroll-area.tsx
+/**
+* ScrollArea. React Aria has no equivalent, so this is a plain scrolling
+* div -- and that is the honest answer rather than a shortcut.
+*
+* Census: fourteen paths match, thirteen are counted, ELEVEN render
+* anything, and across them 17 uses. Every single one passes `className`
+* and nothing else, and 13 of the 17 are a height or flex constraint plus
+* padding. `ScrollBar` is exported by the legacy and imported by nobody.
+* `orientation="horizontal"` has zero call sites.
+*
+* So there is no styled-scrollbar requirement to port. The legacy pays for
+* one anyway: Radix injects a `<style>` tag that hides the native
+* scrollbar, then re-draws it in JavaScript with a ResizeObserver, a
+* portal-free overlay and a `display: table` content wrapper. That is a
+* lot of machinery to reproduce a scrollbar, and it is why the legacy
+* `ScrollArea` cannot be scrolled by keyboard at all.
+*
+* Tailwind 4.3.3 ships `scrollbar-width` and `scrollbar-color` utilities
+* (verified in the installed dist, not assumed), which gets the same look
+* in three classes and no JavaScript.
+*
+* WHAT CANNOT BE STYLED, stated rather than glossed: `scrollbar-color`
+* takes a thumb and a track colour and nothing else -- no width in pixels,
+* no radius, no hover state, no margins. `::-webkit-scrollbar` can do
+* those but is non-standard and Firefox has never supported it. This
+* component uses the standard properties only.
+*/
+const scrollAreaVariants = cva([
+	"overflow-y-auto overscroll-contain",
+	"box-border",
+	"scrollbar-thin scrollbar-thumb-border scrollbar-track-transparent",
+	"outline-none",
+	"focus-visible:outline-solid",
+	"focus-visible:outline-(length:--focus-ring-width)",
+	"focus-visible:outline-offset-(--focus-ring-offset)",
+	"focus-visible:outline-(--color-ring)"
+]);
+function ScrollArea({ className, children, label, scrollResetKey, ...props }) {
+	const region = useRef(null);
+	useEffect(() => {
+		if (region.current) region.current.scrollTop = 0;
+	}, [scrollResetKey]);
+	return /* @__PURE__ */ jsx("div", {
+		...props,
+		ref: region,
+		tabIndex: 0,
+		role: "region",
+		"aria-label": label,
+		"data-slot": "scroll-area",
+		className: cn(scrollAreaVariants(), className),
+		children
+	});
+}
+//#endregion
+export { ScrollArea, scrollAreaVariants };
+
+//# sourceMappingURL=scroll-area.js.map

package/dist/scroll-area/scroll-area.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"scroll-area.js","names":[],"sources":["../../src/scroll-area/scroll-area.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva } from \"class-variance-authority\";\nimport { useEffect, useRef, type ComponentPropsWithoutRef, type ReactNode } from \"react\";\n\nimport { cn } from \"../lib/cn.js\";\n\n/**\n * ScrollArea. React Aria has no equivalent, so this is a plain scrolling\n * div -- and that is the honest answer rather than a shortcut.\n *\n * Census: fourteen paths match, thirteen are counted, ELEVEN render\n * anything, and across them 17 uses. Every single one passes `className`\n * and nothing else, and 13 of the 17 are a height or flex constraint plus\n * padding. `ScrollBar` is exported by the legacy and imported by nobody.\n * `orientation=\"horizontal\"` has zero call sites.\n *\n * So there is no styled-scrollbar requirement to port. The legacy pays for\n * one anyway: Radix injects a `<style>` tag that hides the native\n * scrollbar, then re-draws it in JavaScript with a ResizeObserver, a\n * portal-free overlay and a `display: table` content wrapper. That is a\n * lot of machinery to reproduce a scrollbar, and it is why the legacy\n * `ScrollArea` cannot be scrolled by keyboard at all.\n *\n * Tailwind 4.3.3 ships `scrollbar-width` and `scrollbar-color` utilities\n * (verified in the installed dist, not assumed), which gets the same look\n * in three classes and no JavaScript.\n *\n * WHAT CANNOT BE STYLED, stated rather than glossed: `scrollbar-color`\n * takes a thumb and a track colour and nothing else -- no width in pixels,\n * no radius, no hover state, no margins. `::-webkit-scrollbar` can do\n * those but is non-standard and Firefox has never supported it. This\n * component uses the standard properties only.\n */\nexport const scrollAreaVariants = cva([\n  \"overflow-y-auto overscroll-contain\",\n  \"box-border\",\n  // Standard scrollbar properties. thumb = --color-border (5.25:1 on the\n  // page), track transparent so it does not draw a channel.\n  \"scrollbar-thin scrollbar-thumb-border scrollbar-track-transparent\",\n  // A scrollable region must be reachable by keyboard, or its content is\n  // unreachable without a pointer -- WCAG 2.1.1, and axe's\n  // scrollable-region-focusable rule. The legacy has no tabIndex at all,\n  // so all 17 of its scroll areas are keyboard traps in the other\n  // direction: you can see the content but never scroll to it.\n  \"outline-none\",\n  \"focus-visible:outline-solid\",\n  \"focus-visible:outline-(length:--focus-ring-width)\",\n  \"focus-visible:outline-offset-(--focus-ring-offset)\",\n  \"focus-visible:outline-(--color-ring)\",\n]);\n\n/**\n * A scrolling region.\n *\n * @example\n * <ScrollArea label=\"Chat messages\" className=\"h-64\">...</ScrollArea>\n */\nexport interface ScrollAreaProps extends ComponentPropsWithoutRef<\"div\"> {\n  children?: ReactNode;\n  /**\n   * Names the scrolling region.\n   *\n   * **Required**, and it took a failing test to get here. A focusable\n   * element with no role fails axe `focus-order-semantics`, so the\n   * keyboard fix below cannot ship without a role -- and a role with no\n   * accessible name is a violation of its own. Naming it is the only\n   * combination that is actually correct.\n   *\n   * `role=\"region\"` specifically. `group` was the first attempt -- it is\n   * lighter, since region is a landmark and seventeen landmarks in one app\n   * is noise -- but axe does not accept `group` as an appropriate role for\n   * a focusable element, and it is right: a named region is the role the\n   * ARIA practices name for a scrollable content area, and being able to\n   * jump to it is the point.\n   */\n  label: string;\n  /**\n   * Change this when the contents change, and the region scrolls back to the\n   * top.\n   *\n   * It lives here rather than on the caller because the caller cannot reach\n   * this node: no component in this package exposes a `ref`, and it must not\n   * -- React 18 is a supported peer, where a `ref` passed as a plain prop to a\n   * function component is silently dropped. The scroller owns its own\n   * scrollTop, so the reset belongs with it.\n   *\n   * Sheet forwards its own `scrollResetKey` straight through: going a level\n   * deeper in a panel and landing halfway down the new view is disorienting,\n   * and it is exactly the thing every call site forgets.\n   */\n  scrollResetKey?: string | number;\n}\n\nexport function ScrollArea({\n  className,\n  children,\n  label,\n  scrollResetKey,\n  ...props\n}: ScrollAreaProps) {\n  const region = useRef<HTMLDivElement>(null);\n\n  useEffect(() => {\n    // Unconditional rather than guarded on scrollResetKey being set: with no\n    // key this runs once on mount, where scrollTop is already 0.\n    if (region.current) region.current.scrollTop = 0;\n  }, [scrollResetKey]);\n\n  return (\n    <div\n      {...props}\n      ref={region}\n      // tabIndex 0 unconditionally: whether the content overflows is a\n      // runtime fact that changes as the content does, and a region that\n      // becomes scrollable after a fetch would otherwise never gain focus.\n      tabIndex={0}\n      role=\"region\"\n      aria-label={label}\n      data-slot=\"scroll-area\"\n      className={cn(scrollAreaVariants(), className)}\n    >\n      {children}\n    </div>\n  );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAkCA,MAAa,qBAAqB,IAAI;CACpC;CACA;CAGA;CAMA;CACA;CACA;CACA;CACA;AACF,CAAC;AA4CD,SAAgB,WAAW,EACzB,WACA,UACA,OACA,gBACA,GAAG,SACe;CAClB,MAAM,SAAS,OAAuB,IAAI;CAE1C,gBAAgB;EAGd,IAAI,OAAO,SAAS,OAAO,QAAQ,YAAY;CACjD,GAAG,CAAC,cAAc,CAAC;CAEnB,OACE,oBAAC,OAAD;EACE,GAAI;EACJ,KAAK;EAIL,UAAU;EACV,MAAK;EACL,cAAY;EACZ,aAAU;EACV,WAAW,GAAG,mBAAmB,GAAG,SAAS;EAE5C;CACE,CAAA;AAET"}

package/dist/select/index.d.ts

@@ -0,0 +1,2 @@
+import { Select, SelectItem, SelectItemProps, SelectProps, selectItemVariants, selectPopoverVariants, selectTriggerVariants, selectVariants } from "./select.js";
+export { Select, SelectItem, type SelectItemProps, type SelectProps, selectItemVariants, selectPopoverVariants, selectTriggerVariants, selectVariants };

package/dist/select/index.js

@@ -0,0 +1,2 @@
+import { Select, SelectItem, selectItemVariants, selectPopoverVariants, selectTriggerVariants, selectVariants } from "./select.js";
+export { Select, SelectItem, selectItemVariants, selectPopoverVariants, selectTriggerVariants, selectVariants };

package/dist/select/select.d.ts

@@ -0,0 +1,93 @@
+import { ListBoxItemProps, SelectProps } from "react-aria-components";
+import { ReactNode } from "react";
+//#region src/select/select.d.ts
+/**
+ * Select, ported from the legacy shadcn/Radix component.
+ *
+ * FOUR PARTS COLLAPSE INTO ONE. The census reads `SelectItem` 35 and
+ * `Select`, `SelectTrigger`, `SelectValue`, `SelectContent` 15 each --
+ * those four always appear together in the same shape, exactly like
+ * Dialog's header trio, so they are one component and a prop.
+ * `SelectGroup`, `SelectLabel`, `SelectSeparator`, `SelectScrollUpButton`
+ * and `SelectScrollDownButton` have ZERO call sites and are not ported.
+ *
+ * `label` IS REQUIRED. The legacy exports a `SelectLabel` that nobody
+ * renders and passes no `aria-label` anywhere, so all 15 selects are
+ * unnamed comboboxes -- the same finding as Progress, Slider and
+ * ScrollArea. Pass `labelHidden` when the surrounding UI already says it.
+ *
+ * The trigger reuses `fieldSurfaceVariants`, shared with Input and
+ * Textarea. A select and a text field sit in the same form row and must
+ * be the same box; the legacy styled them separately and drifted --
+ * `h-10` here against Input's `h-9`, for no stated reason.
+ *
+ * The popover is `card`, not a `popover` role: `--popover` is
+ * byte-identical to `--card` in the legacy theme. Item hover is `muted`,
+ * not `accent`, for the same reason.
+ */
+export declare const selectVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const selectTriggerVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const selectPopoverVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const selectItemVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+/**
+ * A single-choice picker.
+ *
+ * @example
+ * <Select label="Country" placeholder="Pick one"
+ *         selectedKey={code} onSelectionChange={setCode}>
+ *   <SelectItem id="gb">United Kingdom</SelectItem>
+ *   <SelectItem id="us">United States</SelectItem>
+ * </Select>
+ */
+interface SelectProps$1 extends Omit<SelectProps<object>, "className" | "style" | "children" | "items"> {
+  /** `SelectItem` children. */
+  children?: ReactNode;
+  /**
+   * What is being chosen, and the control's accessible name.
+   *
+   * **Required.** All 15 legacy selects are unnamed: the legacy exports a
+   * `SelectLabel` that nobody renders and passes no `aria-label`.
+   */
+  label: ReactNode;
+  /** Render the label for screen readers only. */
+  labelHidden?: boolean;
+  /** Shown while nothing is selected. */
+  placeholder?: string;
+  /**
+   * Why the selection is wrong. Rendered under the control, and it is what
+   * makes `isInvalid` reach a screen reader.
+   *
+   * React Aria marks the ROOT `data-invalid` and leaves the button untouched,
+   * and an `aria-invalid` handed to that button is dropped by
+   * `filterDOMProps`, whose allowlist stops at the labelling attributes -- the
+   * same silent loss as `aria-current` on a pagination button. So without a
+   * message, an invalid select is invalid only in colour, which is WCAG 1.4.1
+   * on its own. React Aria wires this into `aria-describedby` for us.
+   */
+  errorMessage?: ReactNode;
+  /** Extra classes for the wrapper. Merged last. */
+  className?: string;
+}
+declare function Select$1({ children, label, labelHidden, placeholder, errorMessage, className, ...props }: SelectProps$1): import("react").JSX.Element;
+/**
+ * One option. Its `id` is the value.
+ *
+ * @example
+ * <SelectItem id="gb">United Kingdom</SelectItem>
+ */
+export interface SelectItemProps extends Omit<ListBoxItemProps, "className" | "style" | "children"> {
+  children?: ReactNode;
+  /**
+   * The option's text, for the trigger and for typeahead.
+   *
+   * Derived from `children` when they are a string. Pass it explicitly
+   * when the option renders anything richer than text.
+   */
+  textValue?: string;
+  /** Extra classes. Merged last, so they win conflicts with ours. */
+  className?: string;
+}
+export declare function SelectItem({ className, children, textValue, ...props }: SelectItemProps): import("react").JSX.Element;
+//#endregion
+export { Select$1 as Select, SelectProps$1 as SelectProps };
+//# sourceMappingURL=select.d.ts.map

package/dist/select/select.js

@@ -0,0 +1,132 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { fieldSurfaceVariants } from "../lib/field-surface.js";
+import { cva } from "class-variance-authority";
+import { Button, FieldError, Label, ListBox, ListBoxItem, Popover, Select, SelectValue } from "react-aria-components";
+import { Fragment, jsx, jsxs } from "react/jsx-runtime";
+//#region src/select/select.tsx
+/**
+* Select, ported from the legacy shadcn/Radix component.
+*
+* FOUR PARTS COLLAPSE INTO ONE. The census reads `SelectItem` 35 and
+* `Select`, `SelectTrigger`, `SelectValue`, `SelectContent` 15 each --
+* those four always appear together in the same shape, exactly like
+* Dialog's header trio, so they are one component and a prop.
+* `SelectGroup`, `SelectLabel`, `SelectSeparator`, `SelectScrollUpButton`
+* and `SelectScrollDownButton` have ZERO call sites and are not ported.
+*
+* `label` IS REQUIRED. The legacy exports a `SelectLabel` that nobody
+* renders and passes no `aria-label` anywhere, so all 15 selects are
+* unnamed comboboxes -- the same finding as Progress, Slider and
+* ScrollArea. Pass `labelHidden` when the surrounding UI already says it.
+*
+* The trigger reuses `fieldSurfaceVariants`, shared with Input and
+* Textarea. A select and a text field sit in the same form row and must
+* be the same box; the legacy styled them separately and drifted --
+* `h-10` here against Input's `h-9`, for no stated reason.
+*
+* The popover is `card`, not a `popover` role: `--popover` is
+* byte-identical to `--card` in the legacy theme. Item hover is `muted`,
+* not `accent`, for the same reason.
+*/
+const selectVariants = cva(["group flex w-full flex-col gap-1.5 box-border font-sans"]);
+const selectTriggerVariants = cva([
+	"group-data-[invalid]:border-destructive-strong",
+	fieldSurfaceVariants(),
+	"flex items-center justify-between gap-2 text-start",
+	"h-(--density-control-h-md) px-(--density-control-pad-md)",
+	"text-base leading-(--leading-normal) cursor-pointer",
+	"[&_svg]:pointer-events-none [&_svg]:shrink-0",
+	"[&_svg:not([class*='size-'])]:size-(--icon-sm)"
+]);
+const selectPopoverVariants = cva([
+	"w-(--trigger-width) min-w-32 overflow-y-auto",
+	"rounded-md border-(length:--border-width) border-border p-1",
+	"bg-card text-card-foreground shadow-floating",
+	"box-border font-sans text-sm leading-(--leading-normal)"
+]);
+const selectItemVariants = cva([
+	"relative flex cursor-pointer select-none items-center gap-2",
+	"rounded-2xs py-1.5 pe-2 ps-8",
+	"box-border text-sm leading-(--leading-normal) text-card-foreground",
+	"outline-none data-[focused]:bg-muted",
+	"data-[focus-visible]:outline-solid",
+	"data-[focus-visible]:outline-(length:--focus-ring-width)",
+	"data-[focus-visible]:outline-offset-(--focus-ring-offset)",
+	"data-[focus-visible]:outline-(--color-ring)",
+	"data-[disabled]:cursor-not-allowed data-[disabled]:opacity-(--opacity-disabled)"
+]);
+function Select$1({ children, label, labelHidden, placeholder, errorMessage, className, ...props }) {
+	return /* @__PURE__ */ jsxs(Select, {
+		...props,
+		"data-slot": "select",
+		className: cn(selectVariants(), className),
+		children: [
+			/* @__PURE__ */ jsx(Label, {
+				"data-slot": "select-label",
+				className: cn("text-sm leading-(--leading-normal) text-foreground", labelHidden && "sr-only"),
+				children: label
+			}),
+			/* @__PURE__ */ jsxs(Button, {
+				"data-slot": "select-trigger",
+				className: selectTriggerVariants(),
+				children: [/* @__PURE__ */ jsx(SelectValue, {
+					"data-slot": "select-value",
+					children: ({ isPlaceholder, selectedText }) => isPlaceholder ? /* @__PURE__ */ jsx("span", {
+						"data-slot": "select-placeholder",
+						className: "text-muted-foreground",
+						children: placeholder
+					}) : selectedText
+				}), /* @__PURE__ */ jsx("svg", {
+					"aria-hidden": "true",
+					viewBox: "0 0 16 16",
+					fill: "none",
+					stroke: "currentColor",
+					strokeWidth: "1.75",
+					strokeLinecap: "round",
+					strokeLinejoin: "round",
+					className: "text-muted-foreground",
+					children: /* @__PURE__ */ jsx("path", { d: "m4 6 4 4 4-4" })
+				})]
+			}),
+			errorMessage == null ? null : /* @__PURE__ */ jsx(FieldError, {
+				"data-slot": "select-error",
+				className: "text-sm leading-(--leading-normal) text-destructive-strong",
+				children: errorMessage
+			}),
+			/* @__PURE__ */ jsx(Popover, {
+				"data-slot": "select-popover",
+				className: selectPopoverVariants(),
+				children: /* @__PURE__ */ jsx(ListBox, {
+					"data-slot": "select-list",
+					className: "outline-none",
+					children
+				})
+			})
+		]
+	});
+}
+function SelectItem({ className, children, textValue, ...props }) {
+	return /* @__PURE__ */ jsx(ListBoxItem, {
+		...props,
+		textValue: textValue ?? (typeof children === "string" ? children : void 0),
+		"data-slot": "select-item",
+		className: cn(selectItemVariants(), className),
+		children: ({ isSelected }) => /* @__PURE__ */ jsxs(Fragment, { children: [isSelected ? /* @__PURE__ */ jsx("svg", {
+			"data-slot": "select-item-check",
+			"aria-hidden": "true",
+			viewBox: "0 0 16 16",
+			fill: "none",
+			stroke: "currentColor",
+			strokeWidth: "2",
+			strokeLinecap: "round",
+			strokeLinejoin: "round",
+			className: "absolute start-2 size-3.5",
+			children: /* @__PURE__ */ jsx("path", { d: "m3.5 8.5 3 3 6-6" })
+		}) : null, children] })
+	});
+}
+//#endregion
+export { Select$1 as Select, SelectItem, selectItemVariants, selectPopoverVariants, selectTriggerVariants, selectVariants };
+
+//# sourceMappingURL=select.js.map

package/dist/select/select.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"select.js","names":["Select","AriaSelect","AriaLabel","AriaButton","AriaSelectValue","AriaFieldError","AriaPopover","AriaListBox","AriaListBoxItem"],"sources":["../../src/select/select.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva } from \"class-variance-authority\";\nimport type { ReactNode } from \"react\";\nimport {\n  Button as AriaButton,\n  FieldError as AriaFieldError,\n  Label as AriaLabel,\n  ListBox as AriaListBox,\n  ListBoxItem as AriaListBoxItem,\n  Popover as AriaPopover,\n  Select as AriaSelect,\n  SelectValue as AriaSelectValue,\n  type ListBoxItemProps as AriaListBoxItemProps,\n  type SelectProps as AriaSelectProps,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\nimport { fieldSurfaceVariants } from \"../lib/field-surface.js\";\n\n/**\n * Select, ported from the legacy shadcn/Radix component.\n *\n * FOUR PARTS COLLAPSE INTO ONE. The census reads `SelectItem` 35 and\n * `Select`, `SelectTrigger`, `SelectValue`, `SelectContent` 15 each --\n * those four always appear together in the same shape, exactly like\n * Dialog's header trio, so they are one component and a prop.\n * `SelectGroup`, `SelectLabel`, `SelectSeparator`, `SelectScrollUpButton`\n * and `SelectScrollDownButton` have ZERO call sites and are not ported.\n *\n * `label` IS REQUIRED. The legacy exports a `SelectLabel` that nobody\n * renders and passes no `aria-label` anywhere, so all 15 selects are\n * unnamed comboboxes -- the same finding as Progress, Slider and\n * ScrollArea. Pass `labelHidden` when the surrounding UI already says it.\n *\n * The trigger reuses `fieldSurfaceVariants`, shared with Input and\n * Textarea. A select and a text field sit in the same form row and must\n * be the same box; the legacy styled them separately and drifted --\n * `h-10` here against Input's `h-9`, for no stated reason.\n *\n * The popover is `card`, not a `popover` role: `--popover` is\n * byte-identical to `--card` in the legacy theme. Item hover is `muted`,\n * not `accent`, for the same reason.\n */\n/*\n * `group` is load-bearing, not decoration. React Aria puts `data-invalid` on\n * THIS element, never on the trigger -- so the trigger's own\n * `data-[invalid]:` rule, inherited from the shared field surface, can never\n * match and `isInvalid` painted nothing at all. The trigger reads the state\n * from here instead.\n */\nexport const selectVariants = cva([\"group flex w-full flex-col gap-1.5 box-border font-sans\"]);\n\nexport const selectTriggerVariants = cva([\n  // See selectVariants: the invalid state lives on the ROOT, so this reads it\n  // from the group rather than from itself.\n  \"group-data-[invalid]:border-destructive-strong\",\n  fieldSurfaceVariants(),\n  \"flex items-center justify-between gap-2 text-start\",\n  \"h-(--density-control-h-md) px-(--density-control-pad-md)\",\n  \"text-base leading-(--leading-normal) cursor-pointer\",\n  \"[&_svg]:pointer-events-none [&_svg]:shrink-0\",\n  \"[&_svg:not([class*='size-'])]:size-(--icon-sm)\",\n]);\n\nexport const selectPopoverVariants = cva([\n  // --trigger-width is set inline by React Aria, so the list matches the\n  // control it came from rather than guessing a width.\n  \"w-(--trigger-width) min-w-32 overflow-y-auto\",\n  \"rounded-md border-(length:--border-width) border-border p-1\",\n  \"bg-card text-card-foreground shadow-floating\",\n  \"box-border font-sans text-sm leading-(--leading-normal)\",\n]);\n\nexport const selectItemVariants = cva([\n  \"relative flex cursor-pointer select-none items-center gap-2\",\n  \"rounded-2xs py-1.5 pe-2 ps-8\",\n  \"box-border text-sm leading-(--leading-normal) text-card-foreground\",\n  // data-focused, not :hover. React Aria drives one highlight from both\n  // pointer and keyboard, so the row under the mouse and the row the\n  // arrows reached are the same row.\n  \"outline-none data-[focused]:bg-muted\",\n  \"data-[focus-visible]:outline-solid\",\n  \"data-[focus-visible]:outline-(length:--focus-ring-width)\",\n  \"data-[focus-visible]:outline-offset-(--focus-ring-offset)\",\n  \"data-[focus-visible]:outline-(--color-ring)\",\n  \"data-[disabled]:cursor-not-allowed data-[disabled]:opacity-(--opacity-disabled)\",\n]);\n\n/**\n * A single-choice picker.\n *\n * @example\n * <Select label=\"Country\" placeholder=\"Pick one\"\n *         selectedKey={code} onSelectionChange={setCode}>\n *   <SelectItem id=\"gb\">United Kingdom</SelectItem>\n *   <SelectItem id=\"us\">United States</SelectItem>\n * </Select>\n */\nexport interface SelectProps\n  extends Omit<AriaSelectProps<object>, \"className\" | \"style\" | \"children\" | \"items\"> {\n  /** `SelectItem` children. */\n  children?: ReactNode;\n  /**\n   * What is being chosen, and the control's accessible name.\n   *\n   * **Required.** All 15 legacy selects are unnamed: the legacy exports a\n   * `SelectLabel` that nobody renders and passes no `aria-label`.\n   */\n  label: ReactNode;\n  /** Render the label for screen readers only. */\n  labelHidden?: boolean;\n  /** Shown while nothing is selected. */\n  placeholder?: string;\n  /**\n   * Why the selection is wrong. Rendered under the control, and it is what\n   * makes `isInvalid` reach a screen reader.\n   *\n   * React Aria marks the ROOT `data-invalid` and leaves the button untouched,\n   * and an `aria-invalid` handed to that button is dropped by\n   * `filterDOMProps`, whose allowlist stops at the labelling attributes -- the\n   * same silent loss as `aria-current` on a pagination button. So without a\n   * message, an invalid select is invalid only in colour, which is WCAG 1.4.1\n   * on its own. React Aria wires this into `aria-describedby` for us.\n   */\n  errorMessage?: ReactNode;\n  /** Extra classes for the wrapper. Merged last. */\n  className?: string;\n}\n\nexport function Select({\n  children,\n  label,\n  labelHidden,\n  placeholder,\n  errorMessage,\n  className,\n  ...props\n}: SelectProps) {\n  return (\n    <AriaSelect {...props} data-slot=\"select\" className={cn(selectVariants(), className)}>\n      <AriaLabel\n        data-slot=\"select-label\"\n        className={cn(\n          \"text-sm leading-(--leading-normal) text-foreground\",\n          labelHidden && \"sr-only\",\n        )}\n      >\n        {label}\n      </AriaLabel>\n\n      <AriaButton data-slot=\"select-trigger\" className={selectTriggerVariants()}>\n        <AriaSelectValue data-slot=\"select-value\">\n          {({ isPlaceholder, selectedText }) =>\n            isPlaceholder ? (\n              <span data-slot=\"select-placeholder\" className=\"text-muted-foreground\">\n                {placeholder}\n              </span>\n            ) : (\n              selectedText\n            )\n          }\n        </AriaSelectValue>\n        {/*\n          aria-hidden: the chevron is decoration. The button already\n          announces itself as a combobox, and a second name source only\n          makes it announce twice.\n        */}\n        <svg\n          aria-hidden=\"true\"\n          viewBox=\"0 0 16 16\"\n          fill=\"none\"\n          stroke=\"currentColor\"\n          strokeWidth=\"1.75\"\n          strokeLinecap=\"round\"\n          strokeLinejoin=\"round\"\n          className=\"text-muted-foreground\"\n        >\n          <path d=\"m4 6 4 4 4-4\" />\n        </svg>\n      </AriaButton>\n\n      {errorMessage == null ? null : (\n        // Not conditional on isInvalid: React Aria renders FieldError only\n        // while the field IS invalid, so gating it here as well would just be\n        // two sources of truth for one state.\n        <AriaFieldError\n          data-slot=\"select-error\"\n          className=\"text-sm leading-(--leading-normal) text-destructive-strong\"\n        >\n          {errorMessage}\n        </AriaFieldError>\n      )}\n\n      <AriaPopover data-slot=\"select-popover\" className={selectPopoverVariants()}>\n        <AriaListBox data-slot=\"select-list\" className=\"outline-none\">\n          {children}\n        </AriaListBox>\n      </AriaPopover>\n    </AriaSelect>\n  );\n}\n\n/**\n * One option. Its `id` is the value.\n *\n * @example\n * <SelectItem id=\"gb\">United Kingdom</SelectItem>\n */\nexport interface SelectItemProps\n  extends Omit<AriaListBoxItemProps, \"className\" | \"style\" | \"children\"> {\n  children?: ReactNode;\n  /**\n   * The option's text, for the trigger and for typeahead.\n   *\n   * Derived from `children` when they are a string. Pass it explicitly\n   * when the option renders anything richer than text.\n   */\n  textValue?: string;\n  /** Extra classes. Merged last, so they win conflicts with ours. */\n  className?: string;\n}\n\nexport function SelectItem({ className, children, textValue, ...props }: SelectItemProps) {\n  return (\n    <AriaListBoxItem\n      {...props}\n      /*\n        textValue, derived from string children.\n        React Aria infers an item's text from its children -- but ONLY\n        when they are a string. This item uses FUNCTION children so the\n        tick can be rendered in JS, which defeats that inference: the\n        trigger showed an empty value after selecting, and typeahead had\n        nothing to match on. Neither is visible in the type system.\n      */\n      textValue={textValue ?? (typeof children === \"string\" ? children : undefined)}\n      data-slot=\"select-item\"\n      className={cn(selectItemVariants(), className)}\n    >\n      {({ isSelected }) => (\n        <>\n          {/*\n            The tick is rendered in JS rather than toggled with CSS, so\n            the precedence is explicit and a test can read it from the\n            DOM. ps-8 above reserves the gutter, so selecting an option\n            does not shift its label.\n          */}\n          {isSelected ? (\n            <svg\n              data-slot=\"select-item-check\"\n              aria-hidden=\"true\"\n              viewBox=\"0 0 16 16\"\n              fill=\"none\"\n              stroke=\"currentColor\"\n              strokeWidth=\"2\"\n              strokeLinecap=\"round\"\n              strokeLinejoin=\"round\"\n              className=\"absolute start-2 size-3.5\"\n            >\n              <path d=\"m3.5 8.5 3 3 6-6\" />\n            </svg>\n          ) : null}\n          {children}\n        </>\n      )}\n    </AriaListBoxItem>\n  );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAmDA,MAAa,iBAAiB,IAAI,CAAC,yDAAyD,CAAC;AAE7F,MAAa,wBAAwB,IAAI;CAGvC;CACA,qBAAqB;CACrB;CACA;CACA;CACA;CACA;AACF,CAAC;AAED,MAAa,wBAAwB,IAAI;CAGvC;CACA;CACA;CACA;AACF,CAAC;AAED,MAAa,qBAAqB,IAAI;CACpC;CACA;CACA;CAIA;CACA;CACA;CACA;CACA;CACA;AACF,CAAC;AA2CD,SAAgBA,SAAO,EACrB,UACA,OACA,aACA,aACA,cACA,WACA,GAAG,SACW;CACd,OACE,qBAACC,QAAD;EAAY,GAAI;EAAO,aAAU;EAAS,WAAW,GAAG,eAAe,GAAG,SAAS;EAAnF,UAAA;GACE,oBAACC,OAAD;IACE,aAAU;IACV,WAAW,GACT,sDACA,eAAe,SACjB;IAEC,UAAA;GACQ,CAAA;GAEX,qBAACC,QAAD;IAAY,aAAU;IAAiB,WAAW,sBAAsB;IAAxE,UAAA,CACE,oBAACC,aAAD;KAAiB,aAAU;KACvB,WAAA,EAAE,eAAe,mBACjB,gBACE,oBAAC,QAAD;MAAM,aAAU;MAAqB,WAAU;MAC5C,UAAA;KACG,CAAA,IAEN;IAGW,CAAA,GAMjB,oBAAC,OAAD;KACE,eAAY;KACZ,SAAQ;KACR,MAAK;KACL,QAAO;KACP,aAAY;KACZ,eAAc;KACd,gBAAe;KACf,WAAU;KAEV,UAAA,oBAAC,QAAD,EAAM,GAAE,eAAgB,CAAA;IACrB,CAAA,CACK;;GAEX,gBAAgB,OAAO,OAItB,oBAACC,YAAD;IACE,aAAU;IACV,WAAU;IAET,UAAA;GACa,CAAA;GAGlB,oBAACC,SAAD;IAAa,aAAU;IAAiB,WAAW,sBAAsB;IACvE,UAAA,oBAACC,SAAD;KAAa,aAAU;KAAc,WAAU;KAC5C;IACU,CAAA;GACF,CAAA;EACH;;AAEhB;AAsBA,SAAgB,WAAW,EAAE,WAAW,UAAU,WAAW,GAAG,SAA0B;CACxF,OACE,oBAACC,aAAD;EACE,GAAI;EASJ,WAAW,cAAc,OAAO,aAAa,WAAW,WAAW,KAAA;EACnE,aAAU;EACV,WAAW,GAAG,mBAAmB,GAAG,SAAS;EAE3C,WAAA,EAAE,iBACF,qBAAA,UAAA,EAAA,UAAA,CAOG,aACC,oBAAC,OAAD;GACE,aAAU;GACV,eAAY;GACZ,SAAQ;GACR,MAAK;GACL,QAAO;GACP,aAAY;GACZ,eAAc;GACd,gBAAe;GACf,WAAU;GAEV,UAAA,oBAAC,QAAD,EAAM,GAAE,mBAAoB,CAAA;EACzB,CAAA,IACH,MACH,QACD,EAAA,CAAA;CAEW,CAAA;AAErB"}

package/dist/separator/index.d.ts

@@ -0,0 +1,2 @@
+import { Separator, SeparatorProps, separatorVariants } from "./separator.js";
+export { Separator, type SeparatorProps, separatorVariants };

package/dist/separator/index.js

@@ -0,0 +1,2 @@
+import { Separator, separatorVariants } from "./separator.js";
+export { Separator, separatorVariants };

package/dist/separator/separator.d.ts

@@ -0,0 +1,42 @@
+import { SeparatorProps } from "react-aria-components";
+//#region src/separator/separator.d.ts
+/**
+ * Separator, ported from the legacy component onto React Aria's Separator.
+ *
+ * Census: 7 files, 6 uses, one of them `orientation="vertical"`. No other
+ * prop is ever passed.
+ *
+ * `decorative` is NOT ported -- zero call sites pass it, and React Aria has
+ * no equivalent. That does change the semantics of all six existing uses,
+ * which is worth saying out loud rather than burying: the legacy defaulted
+ * to `decorative: true` and therefore rendered `role="none"`, so every
+ * divider in the app is currently invisible to assistive technology. React
+ * Aria renders an `<hr>` for a horizontal separator, whose implicit role IS
+ * separator. A visible line between two groups of content is a separator;
+ * announcing it is the correct behaviour, and it is what the element the
+ * legacy chose (a `div`) was pretending not to be.
+ *
+ * Every string in the cva blocks below is a STATIC literal. Tailwind scans
+ * source text, so a class assembled at runtime is invisible to it and would
+ * simply never be emitted.
+ */
+export declare const separatorVariants: (props?: ({
+  orientation?: "horizontal" | "vertical" | null | undefined;
+} & import("class-variance-authority/types").ClassProp) | undefined) => string;
+/**
+ * A visual divider between two groups of content.
+ *
+ * @example
+ * <Separator />
+ * <Separator orientation="vertical" />
+ */
+interface SeparatorProps$1 extends Omit<SeparatorProps, "className" | "style"> {
+  /** @default "horizontal" */
+  orientation?: "horizontal" | "vertical";
+  /** Extra classes. Merged last, so they win conflicts with ours. */
+  className?: string;
+}
+declare function Separator$1({ className, orientation, ...props }: SeparatorProps$1): import("react").JSX.Element;
+//#endregion
+export { Separator$1 as Separator, SeparatorProps$1 as SeparatorProps };
+//# sourceMappingURL=separator.d.ts.map

package/dist/separator/separator.js

@@ -0,0 +1,49 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { cva } from "class-variance-authority";
+import { Separator } from "react-aria-components";
+import { jsx } from "react/jsx-runtime";
+//#region src/separator/separator.tsx
+/**
+* Separator, ported from the legacy component onto React Aria's Separator.
+*
+* Census: 7 files, 6 uses, one of them `orientation="vertical"`. No other
+* prop is ever passed.
+*
+* `decorative` is NOT ported -- zero call sites pass it, and React Aria has
+* no equivalent. That does change the semantics of all six existing uses,
+* which is worth saying out loud rather than burying: the legacy defaulted
+* to `decorative: true` and therefore rendered `role="none"`, so every
+* divider in the app is currently invisible to assistive technology. React
+* Aria renders an `<hr>` for a horizontal separator, whose implicit role IS
+* separator. A visible line between two groups of content is a separator;
+* announcing it is the correct behaviour, and it is what the element the
+* legacy chose (a `div`) was pretending not to be.
+*
+* Every string in the cva blocks below is a STATIC literal. Tailwind scans
+* source text, so a class assembled at runtime is invisible to it and would
+* simply never be emitted.
+*/
+const separatorVariants = cva([
+	"shrink-0 bg-border border-none",
+	"m-0",
+	"box-border"
+], {
+	variants: { orientation: {
+		horizontal: "h-px w-full",
+		vertical: "h-full w-px"
+	} },
+	defaultVariants: { orientation: "horizontal" }
+});
+function Separator$1({ className, orientation = "horizontal", ...props }) {
+	return /* @__PURE__ */ jsx(Separator, {
+		...props,
+		orientation,
+		"data-slot": "separator",
+		className: cn(separatorVariants({ orientation }), className)
+	});
+}
+//#endregion
+export { Separator$1 as Separator, separatorVariants };
+
+//# sourceMappingURL=separator.js.map

package/dist/separator/separator.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"separator.js","names":["Separator","AriaSeparator"],"sources":["../../src/separator/separator.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva } from \"class-variance-authority\";\nimport {\n  Separator as AriaSeparator,\n  type SeparatorProps as AriaSeparatorProps,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\n\n/**\n * Separator, ported from the legacy component onto React Aria's Separator.\n *\n * Census: 7 files, 6 uses, one of them `orientation=\"vertical\"`. No other\n * prop is ever passed.\n *\n * `decorative` is NOT ported -- zero call sites pass it, and React Aria has\n * no equivalent. That does change the semantics of all six existing uses,\n * which is worth saying out loud rather than burying: the legacy defaulted\n * to `decorative: true` and therefore rendered `role=\"none\"`, so every\n * divider in the app is currently invisible to assistive technology. React\n * Aria renders an `<hr>` for a horizontal separator, whose implicit role IS\n * separator. A visible line between two groups of content is a separator;\n * announcing it is the correct behaviour, and it is what the element the\n * legacy chose (a `div`) was pretending not to be.\n *\n * Every string in the cva blocks below is a STATIC literal. Tailwind scans\n * source text, so a class assembled at runtime is invisible to it and would\n * simply never be emitted.\n */\nexport const separatorVariants = cva(\n  [\n    // border-none, not border-0. `border-0` sets the WIDTH to zero but leaves\n    // border-style at solid, so the computed style still claims a border that\n    // simply measures nothing -- the same bookkeeping the Checkbox parity run\n    // turned up on the legacy input. `border-none` says what is true.\n    \"shrink-0 bg-border border-none\",\n    // The user-agent <hr> ships a block margin and a 1px inset border, and\n    // React Aria renders an <hr> for the horizontal case. The reset in\n    // @seekalfred/styles is OPT-IN, so a consumer may load none -- unreset,\n    // every divider is a grooved double line with space around it.\n    \"m-0\",\n    \"box-border\",\n  ],\n  {\n    variants: {\n      orientation: {\n        // h-px / w-px, not the legacy h-[1px] / w-[1px]. Those are bracket\n        // values that check:hardcoding rejects, and `px` is a first-class\n        // Tailwind step rather than an arbitrary one.\n        horizontal: \"h-px w-full\",\n        vertical: \"h-full w-px\",\n      },\n    },\n    defaultVariants: { orientation: \"horizontal\" },\n  },\n);\n\n/**\n * A visual divider between two groups of content.\n *\n * @example\n * <Separator />\n * <Separator orientation=\"vertical\" />\n */\nexport interface SeparatorProps extends Omit<AriaSeparatorProps, \"className\" | \"style\"> {\n  /** @default \"horizontal\" */\n  orientation?: \"horizontal\" | \"vertical\";\n  /** Extra classes. Merged last, so they win conflicts with ours. */\n  className?: string;\n}\n\nexport function Separator({ className, orientation = \"horizontal\", ...props }: SeparatorProps) {\n  return (\n    <AriaSeparator\n      {...props}\n      orientation={orientation}\n      data-slot=\"separator\"\n      className={cn(separatorVariants({ orientation }), className)}\n    />\n  );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AA8BA,MAAa,oBAAoB,IAC/B;CAKE;CAKA;CACA;AACF,GACA;CACE,UAAU,EACR,aAAa;EAIX,YAAY;EACZ,UAAU;CACZ,EACF;CACA,iBAAiB,EAAE,aAAa,aAAa;AAC/C,CACF;AAgBA,SAAgBA,YAAU,EAAE,WAAW,cAAc,cAAc,GAAG,SAAyB;CAC7F,OACE,oBAACC,WAAD;EACE,GAAI;EACS;EACb,aAAU;EACV,WAAW,GAAG,kBAAkB,EAAE,YAAY,CAAC,GAAG,SAAS;CAC5D,CAAA;AAEL"}

package/dist/sheet/index.d.ts

@@ -0,0 +1,2 @@
+import { Sheet, SheetProps, sheetOverlayVariants, sheetPanelVariants } from "./sheet.js";
+export { Sheet, type SheetProps, sheetOverlayVariants, sheetPanelVariants };

package/dist/sheet/index.js

@@ -0,0 +1,2 @@
+import { Sheet, sheetOverlayVariants, sheetPanelVariants } from "./sheet.js";
+export { Sheet, sheetOverlayVariants, sheetPanelVariants };

package/dist/sheet/sheet.d.ts

@@ -0,0 +1,96 @@
+import { DialogProps } from "../dialog/dialog.js";
+//#region src/sheet/sheet.d.ts
+/**
+ * Sheet: a dialog that arrives from an edge.
+ *
+ * A PRESET over `Dialog`, like `AlertDialog`. The legacy `sheet.tsx` is
+ * `@radix-ui/react-dialog` again -- the same import, the same parts, the
+ * same close button -- with one prop changing where it sits. Keeping a
+ * second copy is how the legacy `dialog.tsx` and `alert-dialog.tsx`
+ * drifted, and this is the same file for the third time.
+ *
+ * Census: 2 files, 3 uses. `side="right"` twice, `side="left"` once, and
+ * `className` four times. `SheetHeader`, `SheetFooter`, `SheetTitle`,
+ * `SheetDescription` and `SheetClose` are exported by the legacy and used
+ * by NOBODY -- so all three sheets in the app render a `role="dialog"`
+ * with no title at all. Radix even warns about it in the console.
+ *
+ * `title` is required here, inherited from Dialog, so that is no longer
+ * expressible.
+ *
+ * `side` is `"left" | "right"` only. The legacy also offers `"top"` and
+ * `"bottom"`; both have zero call sites, and each is two lines to add the
+ * day something needs one.
+ *
+ * A REAL BUG THE PORT FIXES: the legacy panel is `w-3/4 sm:max-w-sm`, and
+ * `sm:max-w-sm` names `--container-sm`, which this repo does not define --
+ * so in Alfred it would compile to NOTHING and the sheet would be 75% of
+ * the viewport at every width, on a phone and on a 4K monitor alike. The
+ * width here is a spacing-scale step that actually resolves.
+ *
+ * NOT PORTED: the slide-in animation. It comes from tailwindcss-animate,
+ * which this repo does not ship. React Aria exposes `data-entering` and
+ * `data-exiting`, and `--animate-*` tokens now exist, so it is a small
+ * follow-up rather than a blocker.
+ */
+export declare const sheetOverlayVariants: (props?: ({
+  side?: "left" | "right" | null | undefined;
+} & import("class-variance-authority/types").ClassProp) | undefined) => string;
+export declare const sheetPanelVariants: (props?: ({
+  side?: "left" | "right" | null | undefined;
+} & import("class-variance-authority/types").ClassProp) | undefined) => string;
+/**
+ * A panel that arrives from the side.
+ *
+ * @example
+ * <Sheet isOpen={open} onOpenChange={setOpen} title="Filters">
+ *   ...
+ * </Sheet>
+ */
+export interface SheetProps extends Omit<DialogProps, "overlayClassName"> {
+  /**
+   * Which edge it is attached to.
+   *
+   * `"top"` and `"bottom"` exist in the legacy and have zero call sites.
+   *
+   * @default "right"
+   */
+  side?: "left" | "right";
+  /**
+   * Show a back control, and what it does.
+   *
+   * A side panel that goes a level deeper REPLACES its own contents rather
+   * than stacking a second modal on top, so the browser's back affordance and
+   * the escape key both do the wrong thing -- they close the whole panel
+   * instead of returning one level. The product's own note calls this the
+   * thing that "makes items 119 and 120 one change rather than two".
+   */
+  onBack?: () => void;
+  /** Accessible name and label for the back control. @default "Back" */
+  backLabel?: string;
+  /**
+   * Change this when the panel's contents change, and the body scrolls back
+   * to the top.
+   *
+   * Going a level deeper and landing halfway down the new view is
+   * disorienting, and it is the kind of thing every call site forgets --
+   * which is why it belongs here rather than in each of them.
+   */
+  scrollResetKey?: string | number;
+  /** Extra classes for the scrolling body region. */
+  bodyClassName?: string;
+  /**
+   * Names the scrolling body region. Defaults to `title` when that is a
+   * string, which it is at every call site in the product.
+   *
+   * The body is a `ScrollArea`, so it is focusable -- a scrollable region that
+   * is not reachable by keyboard is WCAG 2.1.1, and axe caught exactly that
+   * when this was a plain div. The product's own `SidePanelBody` still is one.
+   * A focusable element needs a role and a role needs a name, so this is the
+   * only combination that is actually correct.
+   */
+  bodyLabel?: string;
+}
+export declare function Sheet({ side, className, onBack, backLabel, scrollResetKey, bodyClassName, bodyLabel, title, children, ...props }: SheetProps): import("react").JSX.Element;
+//#endregion
+//# sourceMappingURL=sheet.d.ts.map