@seekalfred/primitives 0.2.0 → 0.3.0

package/dist/menu/menu.js

@@ -0,0 +1,99 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { cva } from "class-variance-authority";
+import { Menu, MenuItem, MenuTrigger, Popover, Separator } from "react-aria-components";
+import { jsx } from "react/jsx-runtime";
+//#region src/menu/menu.tsx
+/**
+* Menu, ported from the legacy shadcn/Radix `dropdown-menu` onto React
+* Aria's Menu collection.
+*
+* FIFTEEN EXPORTS BECOME FOUR, and the census is unambiguous about it. Ten
+* files import the legacy component but only EIGHT render anything --
+* `header.tsx` and `PollQuizCreator.tsx` import parts and use none. Across
+* those eight: `DropdownMenuItem` 42, `DropdownMenu` 13,
+* `DropdownMenuTrigger` 13, `DropdownMenuContent` 13,
+* `DropdownMenuSeparator` 2.
+*
+* Everything else is ZERO: `Group`, `CheckboxItem`, `RadioGroup`,
+* `RadioItem`, `Label`, `Shortcut`, `Sub`, `SubTrigger`, `SubContent`,
+* `Portal`. Nine exports, no call sites. React Aria has `MenuSection`,
+* `Header` and selection modes ready if any of them turns out to be
+* wanted -- they are one component each, added the day something needs one.
+*
+* `variant="destructive"` is also never passed, which resolves a real
+* problem rather than dodging one: `destructive-strong` on a `muted` hover
+* fill measures 4.29:1 against a 4.5 floor. The legacy has the same defect
+* unmeasured and worse (its `destructive/10` composite gives 4.01:1). With
+* no call site there is nothing to ship and nothing to weaken the contract
+* for.
+*
+* The surface is `card`, not a `popover` role: in the legacy theme
+* `--popover` is byte-identical to `--card` in both themes. Item hover is
+* `muted`, not `accent`: `--accent` is byte-identical to `--muted`. Two
+* more of the migration plan's proposed roles that already exist.
+*
+* Every string in the cva blocks below is a STATIC literal.
+*/
+const menuPopoverVariants = cva([
+	"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 menuVariants = cva(["flex flex-col outline-none"]);
+const menuItemVariants = cva([
+	"relative flex cursor-pointer select-none items-center gap-2",
+	"rounded-2xs px-2 py-1.5",
+	"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)",
+	"[&_svg]:pointer-events-none [&_svg]:shrink-0",
+	"[&_svg:not([class*='size-'])]:size-(--icon-sm)"
+]);
+const menuSeparatorVariants = cva(["-mx-1 my-1 h-px bg-border border-none"]);
+function Menu$1({ children, className, placement = "bottom start", offset = 4, ...props }) {
+	return /* @__PURE__ */ jsx(Popover, {
+		placement,
+		offset,
+		"data-slot": "menu-popover",
+		className: cn(menuPopoverVariants(), className),
+		children: /* @__PURE__ */ jsx(Menu, {
+			...props,
+			"data-slot": "menu",
+			className: menuVariants(),
+			children
+		})
+	});
+}
+function MenuItem$1({ className, ...props }) {
+	return /* @__PURE__ */ jsx(MenuItem, {
+		...props,
+		"data-slot": "menu-item",
+		className: cn(menuItemVariants(), className)
+	});
+}
+/**
+* A divider between groups of items.
+*
+* A real collection child: React Aria's `Separator` is a `SeparatorNode`,
+* so unlike an arbitrary element it is legal inside a Menu. Inside one it
+* renders `<div role="separator">` rather than the `<hr>` it uses
+* standalone, because `MenuInner` supplies `elementType: 'div'` -- an
+* `<hr>` is not valid inside a `role="menu"` container.
+*/
+function MenuSeparator({ className }) {
+	return /* @__PURE__ */ jsx(Separator, {
+		"data-slot": "menu-separator",
+		className: cn(menuSeparatorVariants(), className)
+	});
+}
+//#endregion
+export { Menu$1 as Menu, MenuItem$1 as MenuItem, MenuSeparator, MenuTrigger, menuItemVariants, menuPopoverVariants, menuSeparatorVariants, menuVariants };
+
+//# sourceMappingURL=menu.js.map

package/dist/menu/menu.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"menu.js","names":["Menu","AriaPopover","AriaMenu","MenuItem","AriaMenuItem","AriaSeparator"],"sources":["../../src/menu/menu.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva } from \"class-variance-authority\";\nimport type { ReactNode } from \"react\";\nimport {\n  Menu as AriaMenu,\n  MenuItem as AriaMenuItem,\n  Popover as AriaPopover,\n  Separator as AriaSeparator,\n  type MenuItemProps as AriaMenuItemProps,\n  type MenuProps as AriaMenuProps,\n  type PopoverProps as AriaPopoverProps,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\n\n/**\n * Menu, ported from the legacy shadcn/Radix `dropdown-menu` onto React\n * Aria's Menu collection.\n *\n * FIFTEEN EXPORTS BECOME FOUR, and the census is unambiguous about it. Ten\n * files import the legacy component but only EIGHT render anything --\n * `header.tsx` and `PollQuizCreator.tsx` import parts and use none. Across\n * those eight: `DropdownMenuItem` 42, `DropdownMenu` 13,\n * `DropdownMenuTrigger` 13, `DropdownMenuContent` 13,\n * `DropdownMenuSeparator` 2.\n *\n * Everything else is ZERO: `Group`, `CheckboxItem`, `RadioGroup`,\n * `RadioItem`, `Label`, `Shortcut`, `Sub`, `SubTrigger`, `SubContent`,\n * `Portal`. Nine exports, no call sites. React Aria has `MenuSection`,\n * `Header` and selection modes ready if any of them turns out to be\n * wanted -- they are one component each, added the day something needs one.\n *\n * `variant=\"destructive\"` is also never passed, which resolves a real\n * problem rather than dodging one: `destructive-strong` on a `muted` hover\n * fill measures 4.29:1 against a 4.5 floor. The legacy has the same defect\n * unmeasured and worse (its `destructive/10` composite gives 4.01:1). With\n * no call site there is nothing to ship and nothing to weaken the contract\n * for.\n *\n * The surface is `card`, not a `popover` role: in the legacy theme\n * `--popover` is byte-identical to `--card` in both themes. Item hover is\n * `muted`, not `accent`: `--accent` is byte-identical to `--muted`. Two\n * more of the migration plan's proposed roles that already exist.\n *\n * Every string in the cva blocks below is a STATIC literal.\n */\nexport const menuPopoverVariants = cva([\n  // min-w-32 is 8rem, the legacy min-w-[8rem] -- but as a spacing-scale\n  // step rather than a bracket value that check:hardcoding rejects.\n  \"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 menuVariants = cva([\n  \"flex flex-col outline-none\",\n]);\n\nexport const menuItemVariants = cva([\n  \"relative flex cursor-pointer select-none items-center gap-2\",\n  \"rounded-2xs px-2 py-1.5\",\n  \"box-border text-sm leading-(--leading-normal) text-card-foreground\",\n  \"outline-none\",\n\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 arrow\n  // keys reached are the same row -- the legacy used `focus:` for the\n  // keyboard and nothing for hover, so a mouse user saw no highlight at all\n  // until the item took focus.\n  \"data-[focused]:bg-muted\",\n\n  // The focus ring goes on the ITEM, and it is an outline rather than a\n  // background alone: a highlight made only of colour disappears under\n  // forced-colors, and axe has no rule that would notice.\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\n  \"data-[disabled]:cursor-not-allowed data-[disabled]:opacity-(--opacity-disabled)\",\n  \"[&_svg]:pointer-events-none [&_svg]:shrink-0\",\n  \"[&_svg:not([class*='size-'])]:size-(--icon-sm)\",\n]);\n\nexport const menuSeparatorVariants = cva([\"-mx-1 my-1 h-px bg-border border-none\"]);\n\n/**\n * A dropdown menu.\n *\n * @example\n * <MenuTrigger>\n *   <Button>Actions</Button>\n *   <Menu onAction={(key) => run(key)}>\n *     <MenuItem id=\"edit\">Edit</MenuItem>\n *     <MenuSeparator />\n *     <MenuItem id=\"delete\">Delete</MenuItem>\n *   </Menu>\n * </MenuTrigger>\n */\nexport interface MenuProps\n  extends Omit<AriaMenuProps<object>, \"className\" | \"style\" | \"children\" | \"items\"> {\n  /** `MenuItem` and `MenuSeparator` children. */\n  children?: ReactNode;\n  /** Extra classes for the popover. Merged last, so they win conflicts. */\n  className?: string;\n  /**\n   * Where the menu opens, as React Aria's single `placement` string.\n   *\n   * The legacy split this across `side`, `align`, `sideOffset` and\n   * `alignOffset`. Its census reads `align=\"end\"` 10 and `align=\"center\"`\n   * 2, always with the default bottom side -- so `\"bottom end\"` covers ten\n   * of the twelve.\n   *\n   * @default \"bottom start\"\n   */\n  placement?: AriaPopoverProps[\"placement\"];\n  /** Gap between the trigger and the menu. @default 4 */\n  offset?: number;\n}\n\nexport function Menu({\n  children,\n  className,\n  placement = \"bottom start\",\n  offset = 4,\n  ...props\n}: MenuProps) {\n  return (\n    <AriaPopover\n      placement={placement}\n      offset={offset}\n      data-slot=\"menu-popover\"\n      className={cn(menuPopoverVariants(), className)}\n    >\n      <AriaMenu {...props} data-slot=\"menu\" className={menuVariants()}>\n        {children}\n      </AriaMenu>\n    </AriaPopover>\n  );\n}\n\n/**\n * One menu row.\n *\n * @example\n * <MenuItem id=\"edit\">Edit</MenuItem>\n * <MenuItem href=\"/settings\">Settings</MenuItem>\n */\nexport interface MenuItemProps extends Omit<AriaMenuItemProps, \"className\" | \"style\"> {\n  /** Extra classes. Merged last, so they win conflicts with ours. */\n  className?: string;\n}\n\nexport function MenuItem({ className, ...props }: MenuItemProps) {\n  return (\n    <AriaMenuItem {...props} data-slot=\"menu-item\" className={cn(menuItemVariants(), className)} />\n  );\n}\n\n/**\n * A divider between groups of items.\n *\n * A real collection child: React Aria's `Separator` is a `SeparatorNode`,\n * so unlike an arbitrary element it is legal inside a Menu. Inside one it\n * renders `<div role=\"separator\">` rather than the `<hr>` it uses\n * standalone, because `MenuInner` supplies `elementType: 'div'` -- an\n * `<hr>` is not valid inside a `role=\"menu\"` container.\n */\nexport function MenuSeparator({ className }: { className?: string }) {\n  return (\n    <AriaSeparator\n      data-slot=\"menu-separator\"\n      className={cn(menuSeparatorVariants(), className)}\n    />\n  );\n}\n\n/**\n * Pairs a trigger with a menu and owns the open state.\n *\n * Re-exported from React Aria unchanged. It takes the trigger element\n * directly as its first child, which is what `asChild` was doing on all 13\n * legacy call sites.\n */\nexport { MenuTrigger } from \"react-aria-components\";\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA+CA,MAAa,sBAAsB,IAAI;CAGrC;CACA;CACA;CACA;AACF,CAAC;AAED,MAAa,eAAe,IAAI,CAC9B,4BACF,CAAC;AAED,MAAa,mBAAmB,IAAI;CAClC;CACA;CACA;CACA;CAOA;CAKA;CACA;CACA;CACA;CAEA;CACA;CACA;AACF,CAAC;AAED,MAAa,wBAAwB,IAAI,CAAC,uCAAuC,CAAC;AAoClF,SAAgBA,OAAK,EACnB,UACA,WACA,YAAY,gBACZ,SAAS,GACT,GAAG,SACS;CACZ,OACE,oBAACC,SAAD;EACa;EACH;EACR,aAAU;EACV,WAAW,GAAG,oBAAoB,GAAG,SAAS;EAE9C,UAAA,oBAACC,MAAD;GAAU,GAAI;GAAO,aAAU;GAAO,WAAW,aAAa;GAC3D;EACO,CAAA;CACC,CAAA;AAEjB;AAcA,SAAgBC,WAAS,EAAE,WAAW,GAAG,SAAwB;CAC/D,OACE,oBAACC,UAAD;EAAc,GAAI;EAAO,aAAU;EAAY,WAAW,GAAG,iBAAiB,GAAG,SAAS;CAAI,CAAA;AAElG;;;;;;;;;;AAWA,SAAgB,cAAc,EAAE,aAAqC;CACnE,OACE,oBAACC,WAAD;EACE,aAAU;EACV,WAAW,GAAG,sBAAsB,GAAG,SAAS;CACjD,CAAA;AAEL"}

package/dist/popover/index.d.ts

@@ -0,0 +1,2 @@
+import { Popover, PopoverProps, PopoverTrigger, popoverVariants } from "./popover.js";
+export { Popover, type PopoverProps, PopoverTrigger, popoverVariants };

package/dist/popover/index.js

@@ -0,0 +1,2 @@
+import { Popover, PopoverTrigger, popoverVariants } from "./popover.js";
+export { Popover, PopoverTrigger, popoverVariants };

package/dist/popover/popover.d.ts

@@ -0,0 +1,50 @@
+import { DialogTrigger as PopoverTrigger, PopoverProps } from "react-aria-components";
+import { ReactNode } from "react";
+//#region src/popover/popover.d.ts
+/**
+ * Popover, ported from the legacy shadcn/Radix component.
+ *
+ * Census: 2 files, 2 uses. `asChild` on the trigger twice, `className`
+ * twice, `align="start"` once. `PopoverAnchor` is exported by the legacy
+ * and imported by nobody, so it is not ported; neither are `side`,
+ * `sideOffset`, `alignOffset`, `open` / `onOpenChange`, `modal`,
+ * `collisionPadding` or `avoidCollisions` -- zero call sites each. Both
+ * existing uses are uncontrolled.
+ *
+ * IT GAINS AN ACCESSIBLE NAME. The legacy renders `role="dialog"` with no
+ * `aria-label` and no `aria-labelledby`, so both call sites announce an
+ * unnamed dialog. React Aria labels the popover from its trigger
+ * automatically once the two are paired, which is the only way to build
+ * one here.
+ *
+ * The surface is `card`: in the legacy theme `--popover` is byte-identical
+ * to `--card` in both themes, so the role the migration plan proposed
+ * already exists under another name.
+ */
+export declare const popoverVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+/**
+ * Content anchored to a trigger.
+ *
+ * @example
+ * <PopoverTrigger>
+ *   <Button>Pick a date</Button>
+ *   <Popover placement="bottom start">...</Popover>
+ * </PopoverTrigger>
+ */
+interface PopoverProps$1 extends Omit<PopoverProps, "className" | "style" | "children"> {
+  children?: ReactNode;
+  /** Extra classes. Merged last, so they win conflicts with ours. */
+  className?: string;
+  /**
+   * Where it opens, as React Aria's single `placement` string. The legacy
+   * split this across `side` and `align`; its one non-default call site is
+   * `align="start"`, which is `"bottom start"` here.
+   *
+   * @default "bottom"
+   */
+  placement?: PopoverProps["placement"];
+}
+declare function Popover$1({ children, className, placement, offset, ...props }: PopoverProps$1): import("react").JSX.Element;
+//#endregion
+export { Popover$1 as Popover, PopoverProps$1 as PopoverProps, PopoverTrigger };
+//# sourceMappingURL=popover.d.ts.map

package/dist/popover/popover.js

@@ -0,0 +1,46 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { cva } from "class-variance-authority";
+import { DialogTrigger as PopoverTrigger, Popover } from "react-aria-components";
+import { jsx } from "react/jsx-runtime";
+//#region src/popover/popover.tsx
+/**
+* Popover, ported from the legacy shadcn/Radix component.
+*
+* Census: 2 files, 2 uses. `asChild` on the trigger twice, `className`
+* twice, `align="start"` once. `PopoverAnchor` is exported by the legacy
+* and imported by nobody, so it is not ported; neither are `side`,
+* `sideOffset`, `alignOffset`, `open` / `onOpenChange`, `modal`,
+* `collisionPadding` or `avoidCollisions` -- zero call sites each. Both
+* existing uses are uncontrolled.
+*
+* IT GAINS AN ACCESSIBLE NAME. The legacy renders `role="dialog"` with no
+* `aria-label` and no `aria-labelledby`, so both call sites announce an
+* unnamed dialog. React Aria labels the popover from its trigger
+* automatically once the two are paired, which is the only way to build
+* one here.
+*
+* The surface is `card`: in the legacy theme `--popover` is byte-identical
+* to `--card` in both themes, so the role the migration plan proposed
+* already exists under another name.
+*/
+const popoverVariants = cva([
+	"w-72 rounded-md border-(length:--border-width) border-border p-4",
+	"bg-card text-card-foreground shadow-floating",
+	"box-border font-sans text-sm leading-(--leading-normal)",
+	"outline-none"
+]);
+function Popover$1({ children, className, placement = "bottom", offset = 4, ...props }) {
+	return /* @__PURE__ */ jsx(Popover, {
+		...props,
+		placement,
+		offset,
+		"data-slot": "popover",
+		className: cn(popoverVariants(), className),
+		children
+	});
+}
+//#endregion
+export { Popover$1 as Popover, PopoverTrigger, popoverVariants };
+
+//# sourceMappingURL=popover.js.map

package/dist/popover/popover.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"popover.js","names":["Popover","AriaPopover"],"sources":["../../src/popover/popover.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva } from \"class-variance-authority\";\nimport type { ReactNode } from \"react\";\nimport {\n  Popover as AriaPopover,\n  type PopoverProps as AriaPopoverProps,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\n\n/**\n * Popover, ported from the legacy shadcn/Radix component.\n *\n * Census: 2 files, 2 uses. `asChild` on the trigger twice, `className`\n * twice, `align=\"start\"` once. `PopoverAnchor` is exported by the legacy\n * and imported by nobody, so it is not ported; neither are `side`,\n * `sideOffset`, `alignOffset`, `open` / `onOpenChange`, `modal`,\n * `collisionPadding` or `avoidCollisions` -- zero call sites each. Both\n * existing uses are uncontrolled.\n *\n * IT GAINS AN ACCESSIBLE NAME. The legacy renders `role=\"dialog\"` with no\n * `aria-label` and no `aria-labelledby`, so both call sites announce an\n * unnamed dialog. React Aria labels the popover from its trigger\n * automatically once the two are paired, which is the only way to build\n * one here.\n *\n * The surface is `card`: in the legacy theme `--popover` is byte-identical\n * to `--card` in both themes, so the role the migration plan proposed\n * already exists under another name.\n */\nexport const popoverVariants = cva([\n  // w-72 (288px) is the legacy default width, as a spacing-scale step.\n  \"w-72 rounded-md border-(length:--border-width) border-border p-4\",\n  \"bg-card text-card-foreground shadow-floating\",\n  // The reset in @seekalfred/styles is OPT-IN, so a consumer may load\n  // none: an unstyled document renders text in a serif, and content-box\n  // would add the 16px padding on top of the width.\n  \"box-border font-sans text-sm leading-(--leading-normal)\",\n  // React Aria gives the popover tabindex=-1 and focuses it on open, so it\n  // can take a focus ring it does not want.\n  \"outline-none\",\n]);\n\n/**\n * Content anchored to a trigger.\n *\n * @example\n * <PopoverTrigger>\n *   <Button>Pick a date</Button>\n *   <Popover placement=\"bottom start\">...</Popover>\n * </PopoverTrigger>\n */\nexport interface PopoverProps\n  extends Omit<AriaPopoverProps, \"className\" | \"style\" | \"children\"> {\n  children?: ReactNode;\n  /** Extra classes. Merged last, so they win conflicts with ours. */\n  className?: string;\n  /**\n   * Where it opens, as React Aria's single `placement` string. The legacy\n   * split this across `side` and `align`; its one non-default call site is\n   * `align=\"start\"`, which is `\"bottom start\"` here.\n   *\n   * @default \"bottom\"\n   */\n  placement?: AriaPopoverProps[\"placement\"];\n}\n\nexport function Popover({\n  children,\n  className,\n  placement = \"bottom\",\n  offset = 4,\n  ...props\n}: PopoverProps) {\n  return (\n    <AriaPopover\n      {...props}\n      placement={placement}\n      offset={offset}\n      data-slot=\"popover\"\n      className={cn(popoverVariants(), className)}\n    >\n      {/*\n        No inner Dialog. Wrapping the content in one is the common React\n        Aria idiom and it was in the first draft here -- but deleting it\n        broke no assertion, so it was doing nothing: a Popover under a\n        DialogTrigger already gets role=\"dialog\", a focus scope, and\n        aria-labelledby pointing at the trigger. The wrapper was one more\n        element and one more className to explain.\n      */}\n      {children}\n    </AriaPopover>\n  );\n}\n\n/**\n * Pairs a trigger with a popover and owns the open state.\n *\n * React Aria's `DialogTrigger`, renamed for the migration: it takes the\n * trigger element directly as its first child, which is what `asChild` was\n * doing on both legacy call sites.\n */\nexport { DialogTrigger as PopoverTrigger } from \"react-aria-components\";\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AA+BA,MAAa,kBAAkB,IAAI;CAEjC;CACA;CAIA;CAGA;AACF,CAAC;AA0BD,SAAgBA,UAAQ,EACtB,UACA,WACA,YAAY,UACZ,SAAS,GACT,GAAG,SACY;CACf,OACE,oBAACC,SAAD;EACE,GAAI;EACO;EACH;EACR,aAAU;EACV,WAAW,GAAG,gBAAgB,GAAG,SAAS;EAUzC;CACU,CAAA;AAEjB"}

package/dist/progress/index.d.ts

@@ -0,0 +1,2 @@
+import { Progress, ProgressProps, progressFillVariants, progressTrackVariants, progressVariants } from "./progress.js";
+export { Progress, type ProgressProps, progressFillVariants, progressTrackVariants, progressVariants };

package/dist/progress/index.js

@@ -0,0 +1,2 @@
+import { Progress, progressFillVariants, progressTrackVariants, progressVariants } from "./progress.js";
+export { Progress, progressFillVariants, progressTrackVariants, progressVariants };

package/dist/progress/progress.d.ts

@@ -0,0 +1,82 @@
+import { VariantProps } from "class-variance-authority";
+import { ProgressBarProps } from "react-aria-components";
+import { ReactNode } from "react";
+//#region src/progress/progress.d.ts
+/**
+ * Progress, ported from the legacy shadcn/Radix component.
+ *
+ * Census: seven files import it and only TWO render anything --
+ * `ResponseOption.tsx` and `LiveQA.tsx`. Both pass `value` and
+ * `className` and nothing else.
+ *
+ * `label` IS REQUIRED, and that is the point. Neither live call site
+ * passes `aria-label`, `aria-labelledby` or an `id` a label targets, and
+ * `role="progressbar"` does not take its name from content -- so both
+ * rendered progress bars are announced as an unnamed progressbar. React
+ * Aria supplies the plumbing for three naming routes but no name of its
+ * own: `<ProgressBar value={60}/>` is just as nameless there. Making the
+ * prop required is what turns it into something you cannot forget.
+ *
+ * The migration plan said this component "adds the missing
+ * aria-valuenow". That is wrong -- Radix already supplies `aria-valuenow`,
+ * `aria-valuemin`, `aria-valuemax` and `aria-valuetext`. The missing thing
+ * was always the NAME.
+ *
+ * THE COLOURS ARE NOT THE LEGACY'S. Its track is `bg-primary/20`, an alpha
+ * fill that composites against unknown page content and therefore has no
+ * fixed contrast pair at all -- over white it is roughly 1.05:1, an
+ * invisible boundary. Its indicator is `bg-primary`, 2.44:1 on the page.
+ * Here the track is `muted` with a `border` boundary and the fill is
+ * `primary-strong`, which puts the fill against the track at 4.61:1 and
+ * the track against the page at 5.25:1.
+ *
+ * Both are in the build-failing contrast contract.
+ */
+export declare const progressVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const progressTrackVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const progressFillVariants: (props?: ({
+  tone?: "neutral" | "success" | "warning" | "danger" | "info" | null | undefined;
+} & import("class-variance-authority/types").ClassProp) | undefined) => string;
+/**
+ * A determinate or indeterminate progress bar.
+ *
+ * @example
+ * <Progress label="Upload" value={62} />
+ * <Progress label="Loading results" />
+ */
+export interface ProgressProps extends Omit<ProgressBarProps, "className" | "style" | "children">, VariantProps<typeof progressFillVariants> {
+  /**
+   * What is progressing, and the bar's accessible name.
+   *
+   * **Required.** Both legacy call sites render an unnamed progressbar.
+   * Pass `labelHidden` when the surrounding UI already says it.
+   */
+  label: ReactNode;
+  /**
+   * Render the label for screen readers only.
+   *
+   * Both legacy call sites sit beside visible text that was never
+   * associated with the bar -- this is how that text becomes the name
+   * without printing it twice.
+   */
+  labelHidden?: boolean;
+  /**
+   * Print the value beside the label.
+   *
+   * The text itself comes from React Aria, which already formats it from
+   * `value`/`minValue`/`maxValue` and honours `formatOptions` and
+   * `valueLabel` -- so a percentage, a currency or "3 of 7" are all reachable
+   * without a second prop here. It was never RENDERED before: the bar
+   * announced its value to assistive tech and showed a sighted reader nothing.
+   */
+  showValue?: boolean;
+  /** Extra classes for the track. */
+  trackClassName?: string;
+  /** Extra classes for the fill -- a per-call-site colour the tone axis cannot express. */
+  fillClassName?: string;
+  /** Extra classes. Merged last, so they win conflicts with ours. */
+  className?: string;
+}
+export declare function Progress({ label, labelHidden, showValue, tone, trackClassName, fillClassName, className, ...props }: ProgressProps): import("react").JSX.Element;
+//#endregion
+//# sourceMappingURL=progress.d.ts.map

package/dist/progress/progress.js

@@ -0,0 +1,82 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { cva } from "class-variance-authority";
+import { Label, ProgressBar } from "react-aria-components";
+import { Fragment, jsx, jsxs } from "react/jsx-runtime";
+//#region src/progress/progress.tsx
+/**
+* Progress, ported from the legacy shadcn/Radix component.
+*
+* Census: seven files import it and only TWO render anything --
+* `ResponseOption.tsx` and `LiveQA.tsx`. Both pass `value` and
+* `className` and nothing else.
+*
+* `label` IS REQUIRED, and that is the point. Neither live call site
+* passes `aria-label`, `aria-labelledby` or an `id` a label targets, and
+* `role="progressbar"` does not take its name from content -- so both
+* rendered progress bars are announced as an unnamed progressbar. React
+* Aria supplies the plumbing for three naming routes but no name of its
+* own: `<ProgressBar value={60}/>` is just as nameless there. Making the
+* prop required is what turns it into something you cannot forget.
+*
+* The migration plan said this component "adds the missing
+* aria-valuenow". That is wrong -- Radix already supplies `aria-valuenow`,
+* `aria-valuemin`, `aria-valuemax` and `aria-valuetext`. The missing thing
+* was always the NAME.
+*
+* THE COLOURS ARE NOT THE LEGACY'S. Its track is `bg-primary/20`, an alpha
+* fill that composites against unknown page content and therefore has no
+* fixed contrast pair at all -- over white it is roughly 1.05:1, an
+* invisible boundary. Its indicator is `bg-primary`, 2.44:1 on the page.
+* Here the track is `muted` with a `border` boundary and the fill is
+* `primary-strong`, which puts the fill against the track at 4.61:1 and
+* the track against the page at 5.25:1.
+*
+* Both are in the build-failing contrast contract.
+*/
+const progressVariants = cva(["flex w-full flex-col gap-1.5 box-border font-sans"]);
+const progressTrackVariants = cva(["relative h-2 w-full overflow-hidden rounded-pill box-border", "bg-muted border-(length:--border-width) border-border"]);
+const progressFillVariants = cva(["h-full rounded-pill", "motion-safe:transition-[width] motion-safe:duration-(--duration-base) motion-safe:ease-standard"], {
+	variants: { tone: {
+		neutral: "bg-primary-strong",
+		success: "bg-success-strong",
+		warning: "bg-warning-strong",
+		danger: "bg-destructive-strong",
+		info: "bg-info-strong"
+	} },
+	defaultVariants: { tone: "neutral" }
+});
+function Progress({ label, labelHidden, showValue, tone, trackClassName, fillClassName, className, ...props }) {
+	return /* @__PURE__ */ jsx(ProgressBar, {
+		...props,
+		"data-slot": "progress",
+		className: cn(progressVariants(), className),
+		children: ({ percentage, isIndeterminate, valueText }) => /* @__PURE__ */ jsxs(Fragment, { children: [/* @__PURE__ */ jsxs("div", {
+			"data-slot": "progress-header",
+			className: cn(showValue && "flex items-baseline justify-between gap-2"),
+			children: [/* @__PURE__ */ jsx(Label, {
+				"data-slot": "progress-label",
+				className: cn("text-sm leading-(--leading-normal) text-foreground", labelHidden && "sr-only"),
+				children: label
+			}), showValue ? /* @__PURE__ */ jsx("span", {
+				"data-slot": "progress-value",
+				"aria-hidden": "true",
+				className: "text-sm leading-(--leading-normal) text-muted-foreground tabular-nums",
+				children: valueText
+			}) : null]
+		}), /* @__PURE__ */ jsx("div", {
+			"data-slot": "progress-track",
+			className: cn(progressTrackVariants(), trackClassName),
+			children: /* @__PURE__ */ jsx("div", {
+				"data-slot": "progress-fill",
+				"data-indeterminate": isIndeterminate || void 0,
+				className: cn(progressFillVariants({ tone }), fillClassName),
+				style: { width: isIndeterminate ? "0%" : `${percentage ?? 0}%` }
+			})
+		})] })
+	});
+}
+//#endregion
+export { Progress, progressFillVariants, progressTrackVariants, progressVariants };
+
+//# sourceMappingURL=progress.js.map

package/dist/progress/progress.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"progress.js","names":["AriaProgressBar","AriaLabel"],"sources":["../../src/progress/progress.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva, type VariantProps } from \"class-variance-authority\";\nimport type { ReactNode } from \"react\";\nimport {\n  Label as AriaLabel,\n  ProgressBar as AriaProgressBar,\n  type ProgressBarProps as AriaProgressBarProps,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\n\n/**\n * Progress, ported from the legacy shadcn/Radix component.\n *\n * Census: seven files import it and only TWO render anything --\n * `ResponseOption.tsx` and `LiveQA.tsx`. Both pass `value` and\n * `className` and nothing else.\n *\n * `label` IS REQUIRED, and that is the point. Neither live call site\n * passes `aria-label`, `aria-labelledby` or an `id` a label targets, and\n * `role=\"progressbar\"` does not take its name from content -- so both\n * rendered progress bars are announced as an unnamed progressbar. React\n * Aria supplies the plumbing for three naming routes but no name of its\n * own: `<ProgressBar value={60}/>` is just as nameless there. Making the\n * prop required is what turns it into something you cannot forget.\n *\n * The migration plan said this component \"adds the missing\n * aria-valuenow\". That is wrong -- Radix already supplies `aria-valuenow`,\n * `aria-valuemin`, `aria-valuemax` and `aria-valuetext`. The missing thing\n * was always the NAME.\n *\n * THE COLOURS ARE NOT THE LEGACY'S. Its track is `bg-primary/20`, an alpha\n * fill that composites against unknown page content and therefore has no\n * fixed contrast pair at all -- over white it is roughly 1.05:1, an\n * invisible boundary. Its indicator is `bg-primary`, 2.44:1 on the page.\n * Here the track is `muted` with a `border` boundary and the fill is\n * `primary-strong`, which puts the fill against the track at 4.61:1 and\n * the track against the page at 5.25:1.\n *\n * Both are in the build-failing contrast contract.\n */\nexport const progressVariants = cva([\"flex w-full flex-col gap-1.5 box-border font-sans\"]);\n\nexport const progressTrackVariants = cva([\n  \"relative h-2 w-full overflow-hidden rounded-pill box-border\",\n  // muted, NOT `border` as the Switch uses. A switch has no fill; a\n  // progress bar does, and primary-strong on a `border` track is 1.01:1 --\n  // the two halves are the same grey and the value disappears.\n  \"bg-muted border-(length:--border-width) border-border\",\n]);\n\nexport const progressFillVariants = cva(\n  [\n    \"h-full rounded-pill\",\n    \"motion-safe:transition-[width] motion-safe:duration-(--duration-base) motion-safe:ease-standard\",\n  ],\n  {\n    variants: {\n      /*\n       * What the value MEANS, which for a progress bar is usually a score\n       * rather than a completion. The product's bar carried exactly this axis\n       * (`default`/`success`/`warning`/`error`/`info`) and reached for it to\n       * colour performance metrics.\n       *\n       * `-strong` throughout: the fill sits on the `muted` track and has to\n       * clear the 3:1 non-text floor of WCAG 1.4.11 against it, which is the\n       * same reason the track is muted rather than `border` -- primary-strong\n       * on a `border` track measures 1.01:1 and the value disappears.\n       */\n      tone: {\n        neutral: \"bg-primary-strong\",\n        success: \"bg-success-strong\",\n        warning: \"bg-warning-strong\",\n        danger: \"bg-destructive-strong\",\n        info: \"bg-info-strong\",\n      },\n    },\n    defaultVariants: { tone: \"neutral\" },\n  },\n);\n\n/**\n * A determinate or indeterminate progress bar.\n *\n * @example\n * <Progress label=\"Upload\" value={62} />\n * <Progress label=\"Loading results\" />\n */\nexport interface ProgressProps\n  extends Omit<AriaProgressBarProps, \"className\" | \"style\" | \"children\">,\n    VariantProps<typeof progressFillVariants> {\n  /**\n   * What is progressing, and the bar's accessible name.\n   *\n   * **Required.** Both legacy call sites render an unnamed progressbar.\n   * Pass `labelHidden` when the surrounding UI already says it.\n   */\n  label: ReactNode;\n  /**\n   * Render the label for screen readers only.\n   *\n   * Both legacy call sites sit beside visible text that was never\n   * associated with the bar -- this is how that text becomes the name\n   * without printing it twice.\n   */\n  labelHidden?: boolean;\n  /**\n   * Print the value beside the label.\n   *\n   * The text itself comes from React Aria, which already formats it from\n   * `value`/`minValue`/`maxValue` and honours `formatOptions` and\n   * `valueLabel` -- so a percentage, a currency or \"3 of 7\" are all reachable\n   * without a second prop here. It was never RENDERED before: the bar\n   * announced its value to assistive tech and showed a sighted reader nothing.\n   */\n  showValue?: boolean;\n  /** Extra classes for the track. */\n  trackClassName?: string;\n  /** Extra classes for the fill -- a per-call-site colour the tone axis cannot express. */\n  fillClassName?: string;\n  /** Extra classes. Merged last, so they win conflicts with ours. */\n  className?: string;\n}\n\nexport function Progress({\n  label,\n  labelHidden,\n  showValue,\n  tone,\n  trackClassName,\n  fillClassName,\n  className,\n  ...props\n}: ProgressProps) {\n  return (\n    <AriaProgressBar\n      {...props}\n      data-slot=\"progress\"\n      className={cn(progressVariants(), className)}\n    >\n      {({ percentage, isIndeterminate, valueText }) => (\n        <>\n          {/*\n            The row exists only when the value is printed. Wrapping the label\n            in a flex row unconditionally would change the label's box for\n            every existing consumer to no purpose.\n          */}\n          <div\n            data-slot=\"progress-header\"\n            className={cn(showValue && \"flex items-baseline justify-between gap-2\")}\n          >\n            <AriaLabel\n              data-slot=\"progress-label\"\n              className={cn(\n                \"text-sm leading-(--leading-normal) text-foreground\",\n                labelHidden && \"sr-only\",\n              )}\n            >\n              {label}\n            </AriaLabel>\n            {showValue ? (\n              <span\n                data-slot=\"progress-value\"\n                // aria-hidden: React Aria already announces the value on the\n                // progressbar itself. Without this a screen reader reads it\n                // twice, once as the widget's value and once as loose text.\n                aria-hidden=\"true\"\n                className=\"text-sm leading-(--leading-normal) text-muted-foreground tabular-nums\"\n              >\n                {valueText}\n              </span>\n            ) : null}\n          </div>\n          <div\n            data-slot=\"progress-track\"\n            className={cn(progressTrackVariants(), trackClassName)}\n          >\n            {/*\n              width, not the legacy translateX(-(100 - value)%). That\n              overflowed for value > 100 -- a positive translate slid the\n              indicator off to the right, while the announced value stayed\n              whatever was passed. React Aria clamps the value, so the two\n              can no longer disagree.\n\n              An indeterminate bar renders no fill rather than the\n              legacy's silent 0%: `value={undefined}` became `(value || 0)`\n              there, so a sighted user saw \"0% done\" while a screen reader\n              said \"indeterminate\".\n            */}\n            <div\n              data-slot=\"progress-fill\"\n              data-indeterminate={isIndeterminate || undefined}\n              className={cn(progressFillVariants({ tone }), fillClassName)}\n              style={{ width: isIndeterminate ? \"0%\" : `${percentage ?? 0}%` }}\n            />\n          </div>\n        </>\n      )}\n    </AriaProgressBar>\n  );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA0CA,MAAa,mBAAmB,IAAI,CAAC,mDAAmD,CAAC;AAEzF,MAAa,wBAAwB,IAAI,CACvC,+DAIA,uDACF,CAAC;AAED,MAAa,uBAAuB,IAClC,CACE,uBACA,iGACF,GACA;CACE,UAAU,EAYR,MAAM;EACJ,SAAS;EACT,SAAS;EACT,SAAS;EACT,QAAQ;EACR,MAAM;CACR,EACF;CACA,iBAAiB,EAAE,MAAM,UAAU;AACrC,CACF;AA6CA,SAAgB,SAAS,EACvB,OACA,aACA,WACA,MACA,gBACA,eACA,WACA,GAAG,SACa;CAChB,OACE,oBAACA,aAAD;EACE,GAAI;EACJ,aAAU;EACV,WAAW,GAAG,iBAAiB,GAAG,SAAS;EAEzC,WAAA,EAAE,YAAY,iBAAiB,gBAC/B,qBAAA,UAAA,EAAA,UAAA,CAME,qBAAC,OAAD;GACE,aAAU;GACV,WAAW,GAAG,aAAa,2CAA2C;GAFxE,UAAA,CAIE,oBAACC,OAAD;IACE,aAAU;IACV,WAAW,GACT,sDACA,eAAe,SACjB;IAEC,UAAA;GACQ,CAAA,GACV,YACC,oBAAC,QAAD;IACE,aAAU;IAIV,eAAY;IACZ,WAAU;IAET,UAAA;GACG,CAAA,IACJ,IACD;EACL,CAAA,GAAA,oBAAC,OAAD;GACE,aAAU;GACV,WAAW,GAAG,sBAAsB,GAAG,cAAc;GAcrD,UAAA,oBAAC,OAAD;IACE,aAAU;IACV,sBAAoB,mBAAmB,KAAA;IACvC,WAAW,GAAG,qBAAqB,EAAE,KAAK,CAAC,GAAG,aAAa;IAC3D,OAAO,EAAE,OAAO,kBAAkB,OAAO,GAAG,cAAc,EAAE,GAAG;GAChE,CAAA;EACE,CAAA,CACL,EAAA,CAAA;CAEW,CAAA;AAErB"}

package/dist/radio-group/index.d.ts

@@ -0,0 +1,2 @@
+import { Radio, RadioGroup, RadioGroupProps, RadioProps, radioGroupVariants, radioVariants } from "./radio-group.js";
+export { Radio, RadioGroup, type RadioGroupProps, type RadioProps, radioGroupVariants, radioVariants };

package/dist/radio-group/index.js

@@ -0,0 +1,2 @@
+import { Radio, RadioGroup, radioGroupVariants, radioVariants } from "./radio-group.js";
+export { Radio, RadioGroup, radioGroupVariants, radioVariants };

package/dist/radio-group/radio-group.d.ts

@@ -0,0 +1,53 @@
+import { RadioGroupProps, RadioProps } from "react-aria-components";
+import { ReactNode } from "react";
+//#region src/radio-group/radio-group.d.ts
+/**
+ * RadioGroup, ported from the legacy shadcn/Radix component onto React Aria.
+ *
+ * Census: 1 file, 3 uses -- `RadioGroup` 1, `RadioGroupItem` 2. The
+ * smallest real surface in the migration, so the port is deliberately plain.
+ *
+ * THE LABEL MOVES INSIDE THE ITEM. Radix's `RadioGroupItem` is a bare
+ * button and the caller pairs it with a separate `<Label htmlFor>`; React
+ * Aria's `Radio` takes its label as `children` and wires the association
+ * itself. That is the one rename a call site has to make, and it removes
+ * the id bookkeeping.
+ *
+ * `border-primary` becomes `border-border` for the same reason it did on
+ * Checkbox: brand orange is 2.44:1 on white and cannot legally be the only
+ * thing describing a control's edge (WCAG 1.4.11). Selected reuses
+ * Checkbox's exact pair -- `bg-primary` with a `primary-strong` boundary --
+ * so a radio and a checkbox in the same form agree.
+ */
+export declare const radioGroupVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const radioVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+/**
+ * A set of mutually exclusive choices.
+ *
+ * @example
+ * <RadioGroup value={plan} onChange={setPlan} aria-label="Plan">
+ *   <Radio value="free">Free</Radio>
+ *   <Radio value="pro">Pro</Radio>
+ * </RadioGroup>
+ */
+interface RadioGroupProps$1 extends Omit<RadioGroupProps, "className" | "style"> {
+  /** Extra classes. Merged last, so they win conflicts with ours. */
+  className?: string;
+}
+declare function RadioGroup$1({ className, ...props }: RadioGroupProps$1): import("react").JSX.Element;
+/**
+ * One choice.
+ *
+ * @example
+ * <Radio value="pro">Pro</Radio>
+ */
+interface RadioProps$1 extends Omit<RadioProps, "className" | "style" | "children"> {
+  /** The label, and this option's accessible name. */
+  children?: ReactNode;
+  /** Extra classes for the label. Merged last, so they win conflicts. */
+  className?: string;
+}
+declare function Radio$1({ className, children, ...props }: RadioProps$1): import("react").JSX.Element;
+//#endregion
+export { Radio$1 as Radio, RadioGroup$1 as RadioGroup, RadioGroupProps$1 as RadioGroupProps, RadioProps$1 as RadioProps };
+//# sourceMappingURL=radio-group.d.ts.map

package/dist/radio-group/radio-group.js

@@ -0,0 +1,65 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { selectionLabelVariants, selectionRingVariants } from "../lib/selection-control.js";
+import { cva } from "class-variance-authority";
+import { Radio, RadioGroup } from "react-aria-components";
+import { Fragment, jsx, jsxs } from "react/jsx-runtime";
+//#region src/radio-group/radio-group.tsx
+/**
+* RadioGroup, ported from the legacy shadcn/Radix component onto React Aria.
+*
+* Census: 1 file, 3 uses -- `RadioGroup` 1, `RadioGroupItem` 2. The
+* smallest real surface in the migration, so the port is deliberately plain.
+*
+* THE LABEL MOVES INSIDE THE ITEM. Radix's `RadioGroupItem` is a bare
+* button and the caller pairs it with a separate `<Label htmlFor>`; React
+* Aria's `Radio` takes its label as `children` and wires the association
+* itself. That is the one rename a call site has to make, and it removes
+* the id bookkeeping.
+*
+* `border-primary` becomes `border-border` for the same reason it did on
+* Checkbox: brand orange is 2.44:1 on white and cannot legally be the only
+* thing describing a control's edge (WCAG 1.4.11). Selected reuses
+* Checkbox's exact pair -- `bg-primary` with a `primary-strong` boundary --
+* so a radio and a checkbox in the same form agree.
+*/
+const radioGroupVariants = cva(["flex flex-col gap-2", "box-border font-sans"]);
+const radioVariants = cva([
+	"inline-flex size-4 shrink-0 items-center justify-center",
+	"rounded-full border-(length:--border-width) box-border",
+	"bg-background border-border",
+	"motion-safe:transition-colors motion-safe:duration-(--duration-fast) motion-safe:ease-standard",
+	"group-data-[selected]:bg-primary group-data-[selected]:border-primary-strong",
+	"group-data-[selected]:text-primary-foreground",
+	selectionRingVariants()
+]);
+function RadioGroup$1({ className, ...props }) {
+	return /* @__PURE__ */ jsx(RadioGroup, {
+		...props,
+		"data-slot": "radio-group",
+		className: cn(radioGroupVariants(), className)
+	});
+}
+function Radio$1({ className, children, ...props }) {
+	return /* @__PURE__ */ jsx(Radio, {
+		...props,
+		"data-slot": "radio",
+		className: cn(selectionLabelVariants(), "justify-start", className),
+		children: ({ isSelected }) => /* @__PURE__ */ jsxs(Fragment, { children: [/* @__PURE__ */ jsx("span", {
+			"aria-hidden": "true",
+			"data-slot": "radio-dot",
+			className: radioVariants(),
+			children: isSelected ? /* @__PURE__ */ jsx("span", {
+				"data-slot": "radio-indicator",
+				className: "size-1.5 rounded-full bg-current"
+			}) : null
+		}), children == null ? null : /* @__PURE__ */ jsx("span", {
+			"data-slot": "radio-label",
+			children
+		})] })
+	});
+}
+//#endregion
+export { Radio$1 as Radio, RadioGroup$1 as RadioGroup, radioGroupVariants, radioVariants };
+
+//# sourceMappingURL=radio-group.js.map

package/dist/radio-group/radio-group.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"radio-group.js","names":["RadioGroup","AriaRadioGroup","Radio","AriaRadio"],"sources":["../../src/radio-group/radio-group.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva } from \"class-variance-authority\";\nimport type { ReactNode } from \"react\";\nimport {\n  Radio as AriaRadio,\n  RadioGroup as AriaRadioGroup,\n  type RadioGroupProps as AriaRadioGroupProps,\n  type RadioProps as AriaRadioProps,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\nimport { selectionLabelVariants, selectionRingVariants } from \"../lib/selection-control.js\";\n\n/**\n * RadioGroup, ported from the legacy shadcn/Radix component onto React Aria.\n *\n * Census: 1 file, 3 uses -- `RadioGroup` 1, `RadioGroupItem` 2. The\n * smallest real surface in the migration, so the port is deliberately plain.\n *\n * THE LABEL MOVES INSIDE THE ITEM. Radix's `RadioGroupItem` is a bare\n * button and the caller pairs it with a separate `<Label htmlFor>`; React\n * Aria's `Radio` takes its label as `children` and wires the association\n * itself. That is the one rename a call site has to make, and it removes\n * the id bookkeeping.\n *\n * `border-primary` becomes `border-border` for the same reason it did on\n * Checkbox: brand orange is 2.44:1 on white and cannot legally be the only\n * thing describing a control's edge (WCAG 1.4.11). Selected reuses\n * Checkbox's exact pair -- `bg-primary` with a `primary-strong` boundary --\n * so a radio and a checkbox in the same form agree.\n */\nexport const radioGroupVariants = cva([\n  \"flex flex-col gap-2\",\n  \"box-border font-sans\",\n]);\n\nexport const radioVariants = cva([\n  \"inline-flex size-4 shrink-0 items-center justify-center\",\n  \"rounded-full border-(length:--border-width) box-border\",\n  \"bg-background border-border\",\n  \"motion-safe:transition-colors motion-safe:duration-(--duration-fast) motion-safe:ease-standard\",\n  \"group-data-[selected]:bg-primary group-data-[selected]:border-primary-strong\",\n  \"group-data-[selected]:text-primary-foreground\",\n  selectionRingVariants(),\n]);\n\n/**\n * A set of mutually exclusive choices.\n *\n * @example\n * <RadioGroup value={plan} onChange={setPlan} aria-label=\"Plan\">\n *   <Radio value=\"free\">Free</Radio>\n *   <Radio value=\"pro\">Pro</Radio>\n * </RadioGroup>\n */\nexport interface RadioGroupProps extends Omit<AriaRadioGroupProps, \"className\" | \"style\"> {\n  /** Extra classes. Merged last, so they win conflicts with ours. */\n  className?: string;\n}\n\nexport function RadioGroup({ className, ...props }: RadioGroupProps) {\n  return (\n    <AriaRadioGroup\n      {...props}\n      data-slot=\"radio-group\"\n      className={cn(radioGroupVariants(), className)}\n    />\n  );\n}\n\n/**\n * One choice.\n *\n * @example\n * <Radio value=\"pro\">Pro</Radio>\n */\nexport interface RadioProps extends Omit<AriaRadioProps, \"className\" | \"style\" | \"children\"> {\n  /** The label, and this option's accessible name. */\n  children?: ReactNode;\n  /** Extra classes for the label. Merged last, so they win conflicts. */\n  className?: string;\n}\n\nexport function Radio({ className, children, ...props }: RadioProps) {\n  return (\n    <AriaRadio\n      {...props}\n      data-slot=\"radio\"\n      // justify-start, overriding the shared label's centring: a radio sits\n      // in a vertical list where every label must start on the same line,\n      // not centre itself in a 24px box.\n      className={cn(selectionLabelVariants(), \"justify-start\", className)}\n    >\n      {({ isSelected }) => (\n        <>\n          <span aria-hidden=\"true\" data-slot=\"radio-dot\" className={radioVariants()}>\n            {isSelected ? (\n              // Rendered in JS rather than toggled with CSS, so the\n              // precedence is explicit and a test can read it from the DOM.\n              <span data-slot=\"radio-indicator\" className=\"size-1.5 rounded-full bg-current\" />\n            ) : null}\n          </span>\n          {children == null ? null : <span data-slot=\"radio-label\">{children}</span>}\n        </>\n      )}\n    </AriaRadio>\n  );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;AAgCA,MAAa,qBAAqB,IAAI,CACpC,uBACA,sBACF,CAAC;AAED,MAAa,gBAAgB,IAAI;CAC/B;CACA;CACA;CACA;CACA;CACA;CACA,sBAAsB;AACxB,CAAC;AAgBD,SAAgBA,aAAW,EAAE,WAAW,GAAG,SAA0B;CACnE,OACE,oBAACC,YAAD;EACE,GAAI;EACJ,aAAU;EACV,WAAW,GAAG,mBAAmB,GAAG,SAAS;CAC9C,CAAA;AAEL;AAeA,SAAgBC,QAAM,EAAE,WAAW,UAAU,GAAG,SAAqB;CACnE,OACE,oBAACC,OAAD;EACE,GAAI;EACJ,aAAU;EAIV,WAAW,GAAG,uBAAuB,GAAG,iBAAiB,SAAS;EAEhE,WAAA,EAAE,iBACF,qBAAA,UAAA,EAAA,UAAA,CACE,oBAAC,QAAD;GAAM,eAAY;GAAO,aAAU;GAAY,WAAW,cAAc;GACrE,UAAA,aAGC,oBAAC,QAAD;IAAM,aAAU;IAAkB,WAAU;GAAoC,CAAA,IAC9E;EACA,CAAA,GACL,YAAY,OAAO,OAAO,oBAAC,QAAD;GAAM,aAAU;GAAe;EAAe,CAAA,CACzE,EAAA,CAAA;CAEK,CAAA;AAEf"}

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

@@ -0,0 +1,2 @@
+import { ScrollArea, ScrollAreaProps, scrollAreaVariants } from "./scroll-area.js";
+export { ScrollArea, type ScrollAreaProps, scrollAreaVariants };

package/dist/scroll-area/index.js

@@ -0,0 +1,2 @@
+import { ScrollArea, scrollAreaVariants } from "./scroll-area.js";
+export { ScrollArea, scrollAreaVariants };