@seekalfred/primitives 0.2.0 → 0.4.0

package/dist/tabs/tabs.d.ts

@@ -0,0 +1,79 @@
+import { TabListProps, TabPanelProps, TabProps, TabsProps } from "react-aria-components";
+//#region src/tabs/tabs.d.ts
+/**
+ * Tabs, ported from the legacy shadcn/Radix component.
+ *
+ * The largest legacy surface in this migration: 18 files, `TabsTrigger`
+ * 51, `TabsContent` 31, `Tabs` 17, `TabsList` 17. Props: `value` 88,
+ * `className` 76, `defaultValue` 12, `onValueChange` 10, `disabled` 6.
+ *
+ * The rename is mechanical but it touches every one of those:
+ * `value` -> `selectedKey`, `defaultValue` -> `defaultSelectedKey`,
+ * `onValueChange` -> `onSelectionChange`, and the `value` on each trigger
+ * and panel becomes `id`. React Aria pairs a Tab to its TabPanel by that
+ * id, exactly as Radix paired them by value.
+ *
+ * THE SELECTED TAB GAINS A BORDER, and that is a contrast fix rather than
+ * a decoration. The legacy marks the selected tab with `bg-background` on
+ * a `bg-muted` list -- 1.13:1, which is not a boundary anybody can see --
+ * and leans on `shadow-sm` to carry the rest. Under WCAG 1.4.11 the thing
+ * telling you which tab is active has to clear 3:1. `border-border` on
+ * `muted` is 4.65:1 and is already in the contrast contract.
+ *
+ * Two bracket values are gone because check:hardcoding rejects them:
+ * `p-[3px]` on the list and `h-[calc(100%-1px)]` on the trigger. The list
+ * is `p-1` and the trigger sizes to the list rather than to a value one
+ * pixel short of it.
+ *
+ * ONE BEHAVIOUR DIFFERS AND IS WORTH KNOWING. Radix keeps every mounted
+ * TabsContent in the DOM and hides the inactive ones; React Aria renders
+ * ONLY the selected panel. A panel that holds uncommitted form state, a
+ * running video or a scroll position will lose it on tab change. React
+ * Aria's `shouldForceMount` on TabPanel restores the old behaviour where
+ * a call site needs it.
+ */
+export declare const tabsVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const tabListVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const tabVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const tabPanelVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+/**
+ * A set of panels, one visible at a time.
+ *
+ * @example
+ * <Tabs defaultSelectedKey="overview">
+ *   <TabList aria-label="Sections">
+ *     <Tab id="overview">Overview</Tab>
+ *     <Tab id="activity">Activity</Tab>
+ *   </TabList>
+ *   <TabPanel id="overview">...</TabPanel>
+ *   <TabPanel id="activity">...</TabPanel>
+ * </Tabs>
+ */
+interface TabsProps$1 extends Omit<TabsProps, "className" | "style"> {
+  /** Extra classes. Merged last, so they win conflicts with ours. */
+  className?: string;
+}
+declare function Tabs$1({ className, ...props }: TabsProps$1): import("react").JSX.Element;
+/**
+ * The row of tabs.
+ *
+ * `aria-label` is worth passing: a tablist is a landmark-ish grouping and
+ * a page with two of them is ambiguous without one.
+ */
+interface TabListProps$1 extends Omit<TabListProps<object>, "className" | "style"> {
+  className?: string;
+}
+declare function TabList$1({ className, ...props }: TabListProps$1): import("react").JSX.Element;
+/** One tab. Its `id` pairs it with the panel of the same `id`. */
+interface TabProps$1 extends Omit<TabProps, "className" | "style"> {
+  className?: string;
+}
+declare function Tab$1({ className, ...props }: TabProps$1): import("react").JSX.Element;
+/** One panel. Its `id` pairs it with the tab of the same `id`. */
+interface TabPanelProps$1 extends Omit<TabPanelProps, "className" | "style"> {
+  className?: string;
+}
+declare function TabPanel$1({ className, ...props }: TabPanelProps$1): import("react").JSX.Element;
+//#endregion
+export { Tab$1 as Tab, TabList$1 as TabList, TabListProps$1 as TabListProps, TabPanel$1 as TabPanel, TabPanelProps$1 as TabPanelProps, TabProps$1 as TabProps, Tabs$1 as Tabs, TabsProps$1 as TabsProps };
+//# sourceMappingURL=tabs.d.ts.map

package/dist/tabs/tabs.js

@@ -0,0 +1,103 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { cva } from "class-variance-authority";
+import { Tab, TabList, TabPanel, Tabs } from "react-aria-components";
+import { jsx } from "react/jsx-runtime";
+//#region src/tabs/tabs.tsx
+/**
+* Tabs, ported from the legacy shadcn/Radix component.
+*
+* The largest legacy surface in this migration: 18 files, `TabsTrigger`
+* 51, `TabsContent` 31, `Tabs` 17, `TabsList` 17. Props: `value` 88,
+* `className` 76, `defaultValue` 12, `onValueChange` 10, `disabled` 6.
+*
+* The rename is mechanical but it touches every one of those:
+* `value` -> `selectedKey`, `defaultValue` -> `defaultSelectedKey`,
+* `onValueChange` -> `onSelectionChange`, and the `value` on each trigger
+* and panel becomes `id`. React Aria pairs a Tab to its TabPanel by that
+* id, exactly as Radix paired them by value.
+*
+* THE SELECTED TAB GAINS A BORDER, and that is a contrast fix rather than
+* a decoration. The legacy marks the selected tab with `bg-background` on
+* a `bg-muted` list -- 1.13:1, which is not a boundary anybody can see --
+* and leans on `shadow-sm` to carry the rest. Under WCAG 1.4.11 the thing
+* telling you which tab is active has to clear 3:1. `border-border` on
+* `muted` is 4.65:1 and is already in the contrast contract.
+*
+* Two bracket values are gone because check:hardcoding rejects them:
+* `p-[3px]` on the list and `h-[calc(100%-1px)]` on the trigger. The list
+* is `p-1` and the trigger sizes to the list rather than to a value one
+* pixel short of it.
+*
+* ONE BEHAVIOUR DIFFERS AND IS WORTH KNOWING. Radix keeps every mounted
+* TabsContent in the DOM and hides the inactive ones; React Aria renders
+* ONLY the selected panel. A panel that holds uncommitted form state, a
+* running video or a scroll position will lose it on tab change. React
+* Aria's `shouldForceMount` on TabPanel restores the old behaviour where
+* a call site needs it.
+*/
+const tabsVariants = cva(["flex flex-col gap-2 box-border font-sans"]);
+const tabListVariants = cva([
+	"inline-flex w-fit items-center justify-center gap-1",
+	"rounded-lg p-1",
+	"bg-muted text-muted-foreground",
+	"box-border"
+]);
+const tabVariants = cva([
+	"inline-flex flex-1 items-center justify-center gap-1.5 whitespace-nowrap",
+	"rounded-md px-2 py-1",
+	"text-sm leading-(--leading-normal) font-medium text-foreground",
+	"cursor-pointer select-none box-border",
+	"border-(length:--border-width) border-transparent",
+	"motion-safe:transition-colors motion-safe:duration-(--duration-fast) motion-safe:ease-standard",
+	"data-[selected]:bg-background data-[selected]:border-border",
+	"data-[selected]:shadow-surface",
+	"outline-none",
+	"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 tabPanelVariants = cva([
+	"flex-1 box-border font-sans text-foreground",
+	"outline-none",
+	"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)"
+]);
+function Tabs$1({ className, ...props }) {
+	return /* @__PURE__ */ jsx(Tabs, {
+		...props,
+		"data-slot": "tabs",
+		className: cn(tabsVariants(), className)
+	});
+}
+function TabList$1({ className, ...props }) {
+	return /* @__PURE__ */ jsx(TabList, {
+		...props,
+		"data-slot": "tab-list",
+		className: cn(tabListVariants(), className)
+	});
+}
+function Tab$1({ className, ...props }) {
+	return /* @__PURE__ */ jsx(Tab, {
+		...props,
+		"data-slot": "tab",
+		className: cn(tabVariants(), className)
+	});
+}
+function TabPanel$1({ className, ...props }) {
+	return /* @__PURE__ */ jsx(TabPanel, {
+		...props,
+		"data-slot": "tab-panel",
+		className: cn(tabPanelVariants(), className)
+	});
+}
+//#endregion
+export { Tab$1 as Tab, TabList$1 as TabList, TabPanel$1 as TabPanel, Tabs$1 as Tabs, tabListVariants, tabPanelVariants, tabVariants, tabsVariants };
+
+//# sourceMappingURL=tabs.js.map

package/dist/tabs/tabs.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"tabs.js","names":["Tabs","AriaTabs","TabList","AriaTabList","Tab","AriaTab","TabPanel","AriaTabPanel"],"sources":["../../src/tabs/tabs.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva } from \"class-variance-authority\";\nimport {\n  Tab as AriaTab,\n  TabList as AriaTabList,\n  TabPanel as AriaTabPanel,\n  Tabs as AriaTabs,\n  type TabListProps as AriaTabListProps,\n  type TabPanelProps as AriaTabPanelProps,\n  type TabProps as AriaTabProps,\n  type TabsProps as AriaTabsProps,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\n\n/**\n * Tabs, ported from the legacy shadcn/Radix component.\n *\n * The largest legacy surface in this migration: 18 files, `TabsTrigger`\n * 51, `TabsContent` 31, `Tabs` 17, `TabsList` 17. Props: `value` 88,\n * `className` 76, `defaultValue` 12, `onValueChange` 10, `disabled` 6.\n *\n * The rename is mechanical but it touches every one of those:\n * `value` -> `selectedKey`, `defaultValue` -> `defaultSelectedKey`,\n * `onValueChange` -> `onSelectionChange`, and the `value` on each trigger\n * and panel becomes `id`. React Aria pairs a Tab to its TabPanel by that\n * id, exactly as Radix paired them by value.\n *\n * THE SELECTED TAB GAINS A BORDER, and that is a contrast fix rather than\n * a decoration. The legacy marks the selected tab with `bg-background` on\n * a `bg-muted` list -- 1.13:1, which is not a boundary anybody can see --\n * and leans on `shadow-sm` to carry the rest. Under WCAG 1.4.11 the thing\n * telling you which tab is active has to clear 3:1. `border-border` on\n * `muted` is 4.65:1 and is already in the contrast contract.\n *\n * Two bracket values are gone because check:hardcoding rejects them:\n * `p-[3px]` on the list and `h-[calc(100%-1px)]` on the trigger. The list\n * is `p-1` and the trigger sizes to the list rather than to a value one\n * pixel short of it.\n *\n * ONE BEHAVIOUR DIFFERS AND IS WORTH KNOWING. Radix keeps every mounted\n * TabsContent in the DOM and hides the inactive ones; React Aria renders\n * ONLY the selected panel. A panel that holds uncommitted form state, a\n * running video or a scroll position will lose it on tab change. React\n * Aria's `shouldForceMount` on TabPanel restores the old behaviour where\n * a call site needs it.\n */\nexport const tabsVariants = cva([\"flex flex-col gap-2 box-border font-sans\"]);\n\nexport const tabListVariants = cva([\n  \"inline-flex w-fit items-center justify-center gap-1\",\n  // p-1, not the legacy p-[3px]: a bracket value check:hardcoding rejects.\n  \"rounded-lg p-1\",\n  \"bg-muted text-muted-foreground\",\n  \"box-border\",\n]);\n\nexport const tabVariants = cva([\n  \"inline-flex flex-1 items-center justify-center gap-1.5 whitespace-nowrap\",\n  \"rounded-md px-2 py-1\",\n  \"text-sm leading-(--leading-normal) font-medium text-foreground\",\n  \"cursor-pointer select-none box-border\",\n  // A transparent border at rest so selecting one does not move the text.\n  \"border-(length:--border-width) border-transparent\",\n  \"motion-safe:transition-colors motion-safe:duration-(--duration-fast) motion-safe:ease-standard\",\n\n  // The selected tab. bg-background on a muted list is 1.13:1 -- invisible\n  // as a boundary -- so the border is what satisfies WCAG 1.4.11 at\n  // 4.65:1. The fill and the shadow are the polish on top of it.\n  \"data-[selected]:bg-background data-[selected]:border-border\",\n  \"data-[selected]:shadow-surface\",\n\n  // outline-solid is load-bearing: outline-none sets --tw-outline-style to\n  // none and the width utility resolves its style from that same variable,\n  // so a focus rule can apply a width and a colour and paint nothing.\n  \"outline-none\",\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 tabPanelVariants = cva([\n  \"flex-1 box-border font-sans text-foreground\",\n  // React Aria gives the panel tabindex=0 when it holds no focusable\n  // child, so it can take a ring it does not want at rest.\n  \"outline-none\",\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\n/**\n * A set of panels, one visible at a time.\n *\n * @example\n * <Tabs defaultSelectedKey=\"overview\">\n *   <TabList aria-label=\"Sections\">\n *     <Tab id=\"overview\">Overview</Tab>\n *     <Tab id=\"activity\">Activity</Tab>\n *   </TabList>\n *   <TabPanel id=\"overview\">...</TabPanel>\n *   <TabPanel id=\"activity\">...</TabPanel>\n * </Tabs>\n */\nexport interface TabsProps extends Omit<AriaTabsProps, \"className\" | \"style\"> {\n  /** Extra classes. Merged last, so they win conflicts with ours. */\n  className?: string;\n}\n\nexport function Tabs({ className, ...props }: TabsProps) {\n  return <AriaTabs {...props} data-slot=\"tabs\" className={cn(tabsVariants(), className)} />;\n}\n\n/**\n * The row of tabs.\n *\n * `aria-label` is worth passing: a tablist is a landmark-ish grouping and\n * a page with two of them is ambiguous without one.\n */\nexport interface TabListProps extends Omit<AriaTabListProps<object>, \"className\" | \"style\"> {\n  className?: string;\n}\n\nexport function TabList({ className, ...props }: TabListProps) {\n  return (\n    <AriaTabList {...props} data-slot=\"tab-list\" className={cn(tabListVariants(), className)} />\n  );\n}\n\n/** One tab. Its `id` pairs it with the panel of the same `id`. */\nexport interface TabProps extends Omit<AriaTabProps, \"className\" | \"style\"> {\n  className?: string;\n}\n\nexport function Tab({ className, ...props }: TabProps) {\n  return <AriaTab {...props} data-slot=\"tab\" className={cn(tabVariants(), className)} />;\n}\n\n/** One panel. Its `id` pairs it with the tab of the same `id`. */\nexport interface TabPanelProps extends Omit<AriaTabPanelProps, \"className\" | \"style\"> {\n  className?: string;\n}\n\nexport function TabPanel({ className, ...props }: TabPanelProps) {\n  return (\n    <AriaTabPanel {...props} data-slot=\"tab-panel\" className={cn(tabPanelVariants(), className)} />\n  );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAgDA,MAAa,eAAe,IAAI,CAAC,0CAA0C,CAAC;AAE5E,MAAa,kBAAkB,IAAI;CACjC;CAEA;CACA;CACA;AACF,CAAC;AAED,MAAa,cAAc,IAAI;CAC7B;CACA;CACA;CACA;CAEA;CACA;CAKA;CACA;CAKA;CACA;CACA;CACA;CACA;CAEA;CACA;CACA;AACF,CAAC;AAED,MAAa,mBAAmB,IAAI;CAClC;CAGA;CACA;CACA;CACA;CACA;AACF,CAAC;AAoBD,SAAgBA,OAAK,EAAE,WAAW,GAAG,SAAoB;CACvD,OAAO,oBAACC,MAAD;EAAU,GAAI;EAAO,aAAU;EAAO,WAAW,GAAG,aAAa,GAAG,SAAS;CAAI,CAAA;AAC1F;AAYA,SAAgBC,UAAQ,EAAE,WAAW,GAAG,SAAuB;CAC7D,OACE,oBAACC,SAAD;EAAa,GAAI;EAAO,aAAU;EAAW,WAAW,GAAG,gBAAgB,GAAG,SAAS;CAAI,CAAA;AAE/F;AAOA,SAAgBC,MAAI,EAAE,WAAW,GAAG,SAAmB;CACrD,OAAO,oBAACC,KAAD;EAAS,GAAI;EAAO,aAAU;EAAM,WAAW,GAAG,YAAY,GAAG,SAAS;CAAI,CAAA;AACvF;AAOA,SAAgBC,WAAS,EAAE,WAAW,GAAG,SAAwB;CAC/D,OACE,oBAACC,UAAD;EAAc,GAAI;EAAO,aAAU;EAAY,WAAW,GAAG,iBAAiB,GAAG,SAAS;CAAI,CAAA;AAElG"}

package/dist/textarea/index.d.ts

@@ -0,0 +1,2 @@
+import { Textarea, TextareaProps, textareaVariants } from "./textarea.js";
+export { Textarea, type TextareaProps, textareaVariants };

package/dist/textarea/index.js

@@ -0,0 +1,2 @@
+import { Textarea, textareaVariants } from "./textarea.js";
+export { Textarea, textareaVariants };

package/dist/textarea/textarea.d.ts

@@ -0,0 +1,27 @@
+import { TextAreaProps } from "react-aria-components";
+//#region src/textarea/textarea.d.ts
+/**
+ * Textarea, ported from the legacy component onto React Aria's TextArea.
+ *
+ * Census: 3 files, 3 uses -- `value`, `onChange`, `placeholder`, `id`,
+ * `ref`. All native props, all still native here.
+ *
+ * The surface comes from `fieldSurfaceVariants`, shared with Input. The two
+ * legacy files styled it separately and had already drifted -- different
+ * background, different focus ring, invalid styling on one and not the
+ * other -- and none of those differences was a decision anyone made.
+ */
+export declare const textareaVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+/**
+ * A multi-line text field.
+ *
+ * @example
+ * <Textarea placeholder="Tell us more" value={v} onChange={e => set(e.target.value)} />
+ */
+export interface TextareaProps extends Omit<TextAreaProps, "className" | "style"> {
+  /** Extra classes. Merged last, so they win conflicts with ours. */
+  className?: string;
+}
+export declare function Textarea({ className, ...props }: TextareaProps): import("react").JSX.Element;
+//#endregion
+//# sourceMappingURL=textarea.d.ts.map

package/dist/textarea/textarea.js

@@ -0,0 +1,37 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { fieldSurfaceVariants } from "../lib/field-surface.js";
+import { cva } from "class-variance-authority";
+import { TextArea } from "react-aria-components";
+import { jsx } from "react/jsx-runtime";
+//#region src/textarea/textarea.tsx
+/**
+* Textarea, ported from the legacy component onto React Aria's TextArea.
+*
+* Census: 3 files, 3 uses -- `value`, `onChange`, `placeholder`, `id`,
+* `ref`. All native props, all still native here.
+*
+* The surface comes from `fieldSurfaceVariants`, shared with Input. The two
+* legacy files styled it separately and had already drifted -- different
+* background, different focus ring, invalid styling on one and not the
+* other -- and none of those differences was a decision anyone made.
+*/
+const textareaVariants = cva([
+	fieldSurfaceVariants(),
+	"min-h-20",
+	"px-(--density-control-pad-md) py-(--density-control-pad-sm)",
+	"text-base",
+	"resize-y",
+	"leading-(--leading-normal)"
+]);
+function Textarea({ className, ...props }) {
+	return /* @__PURE__ */ jsx(TextArea, {
+		...props,
+		"data-slot": "textarea",
+		className: cn(textareaVariants(), className)
+	});
+}
+//#endregion
+export { Textarea, textareaVariants };
+
+//# sourceMappingURL=textarea.js.map

package/dist/textarea/textarea.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"textarea.js","names":["AriaTextArea"],"sources":["../../src/textarea/textarea.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva } from \"class-variance-authority\";\nimport {\n  TextArea as AriaTextArea,\n  type TextAreaProps as AriaTextAreaProps,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\nimport { fieldSurfaceVariants } from \"../lib/field-surface.js\";\n\n/**\n * Textarea, ported from the legacy component onto React Aria's TextArea.\n *\n * Census: 3 files, 3 uses -- `value`, `onChange`, `placeholder`, `id`,\n * `ref`. All native props, all still native here.\n *\n * The surface comes from `fieldSurfaceVariants`, shared with Input. The two\n * legacy files styled it separately and had already drifted -- different\n * background, different focus ring, invalid styling on one and not the\n * other -- and none of those differences was a decision anyone made.\n */\nexport const textareaVariants = cva([\n  fieldSurfaceVariants(),\n\n  // min-h-20 is 80px, the legacy min-h-[80px] -- but as a spacing-scale step\n  // rather than a bracket value, which check:hardcoding rejects.\n  \"min-h-20\",\n  \"px-(--density-control-pad-md) py-(--density-control-pad-sm)\",\n  \"text-base\",\n\n  // A textarea is resizable by the user agent, and horizontal resize breaks\n  // any layout it sits in. Vertical only.\n  \"resize-y\",\n  // Height is content, not a control slot, so the line-height has to be set\n  // explicitly -- unset it computes to `normal`, which varies with the\n  // font's own metrics.\n  \"leading-(--leading-normal)\",\n]);\n\n/**\n * A multi-line text field.\n *\n * @example\n * <Textarea placeholder=\"Tell us more\" value={v} onChange={e => set(e.target.value)} />\n */\nexport interface TextareaProps extends Omit<AriaTextAreaProps, \"className\" | \"style\"> {\n  /** Extra classes. Merged last, so they win conflicts with ours. */\n  className?: string;\n}\n\nexport function Textarea({ className, ...props }: TextareaProps) {\n  return (\n    <AriaTextArea {...props} data-slot=\"textarea\" className={cn(textareaVariants(), className)} />\n  );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;AAsBA,MAAa,mBAAmB,IAAI;CAClC,qBAAqB;CAIrB;CACA;CACA;CAIA;CAIA;AACF,CAAC;AAaD,SAAgB,SAAS,EAAE,WAAW,GAAG,SAAwB;CAC/D,OACE,oBAACA,UAAD;EAAc,GAAI;EAAO,aAAU;EAAW,WAAW,GAAG,iBAAiB,GAAG,SAAS;CAAI,CAAA;AAEjG"}

package/dist/toast/index.d.ts

@@ -0,0 +1,2 @@
+import { ToastContent, ToastRegion, ToastRegionProps, toast, toastCloseVariants, toastQueue, toastRegionVariants, toastVariants } from "./toast.js";
+export { type ToastContent, ToastRegion, type ToastRegionProps, toast, toastCloseVariants, toastQueue, toastRegionVariants, toastVariants };

package/dist/toast/index.js

@@ -0,0 +1,2 @@
+import { ToastRegion, toast, toastCloseVariants, toastQueue, toastRegionVariants, toastVariants } from "./toast.js";
+export { ToastRegion, toast, toastCloseVariants, toastQueue, toastRegionVariants, toastVariants };

package/dist/toast/toast.d.ts

@@ -0,0 +1,93 @@
+import { VariantProps } from "class-variance-authority";
+import { UNSTABLE_ToastQueue } from "react-aria-components";
+import { ReactNode } from "react";
+//#region src/toast/toast.d.ts
+/**
+ * Toast: a transient message, announced without stealing focus.
+ *
+ * Maturity: **experimental**, and the reason is upstream rather than here.
+ * React Aria ships this API as `UNSTABLE_Toast*` in 1.21.1, so a RAC minor
+ * bump can rename or reshape it. The alternative was hand-rolling the live
+ * region, the queue, the timers and the focus behaviour, which is how every
+ * toast implementation acquires its accessibility bugs -- so this takes the
+ * upstream one and labels the risk instead of hiding it.
+ *
+ * THE PRODUCT HAS 30 FILES CALLING `useToast` AND 67 `toast(...)` CALLS, and
+ * its implementation is the shadcn reducer with both of its known defects
+ * still in place:
+ *
+ *   TOAST_LIMIT = 1          -- a second toast REPLACES the first, so a
+ *                               burst of results shows only the last one.
+ *   TOAST_REMOVE_DELAY = 1e6 -- sixteen minutes. Nothing auto-dismisses;
+ *                               every toast waits to be closed by hand.
+ *
+ * Neither is ported. `maxVisibleToasts` defaults to 3 and `timeout` to 5s,
+ * which is the WCAG 2.2.1 floor React Aria enforces -- it REFUSES a timeout
+ * under 5000ms, because a message that vanishes faster cannot be read by
+ * someone using a screen magnifier.
+ *
+ * The queue is a module singleton on purpose. The product's `toast()` is
+ * importable from anywhere and called from API error handlers and effects
+ * that have no component to hang a hook off, and a context-based queue would
+ * have made those 67 call sites into 67 refactors.
+ */
+/** Where the region sits. Fixed, above everything, out of the way of content. */
+export declare const toastRegionVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+export declare const toastVariants: (props?: ({
+  tone?: "neutral" | "success" | "warning" | "danger" | "info" | null | undefined;
+} & import("class-variance-authority/types").ClassProp) | undefined) => string;
+export declare const toastCloseVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+/** What a toast carries. `title` is required: an unnamed toast announces nothing. */
+export interface ToastContent extends VariantProps<typeof toastVariants> {
+  /** The message. Required -- a toast with only a description announces as loose text. */
+  title: ReactNode;
+  /** Secondary detail, beneath the title. */
+  description?: ReactNode;
+}
+/**
+ * The queue every `toast()` call feeds.
+ *
+ * Exported so a consumer can read `visibleToasts` in a test, or dismiss them
+ * on a route change -- there is no `clear()` upstream, so that is
+ * `[...toastQueue.visibleToasts].forEach((t) => toastQueue.close(t.key))`.
+ * Not something to touch in normal use.
+ */
+export declare const toastQueue: UNSTABLE_ToastQueue<ToastContent>;
+/**
+ * Show a toast.
+ *
+ * @example
+ * toast({ title: "Report saved" });
+ * toast({ title: "Upload failed", description: err.message, tone: "danger" });
+ *
+ * @param timeout - ms before it dismisses itself. React Aria REFUSES anything
+ * under 5000 and anything at all while the region is focused, because a
+ * message that disappears before it can be read fails WCAG 2.2.1. Pass 0 to
+ * require a manual dismiss, which is right for an error a user must act on.
+ */
+export declare function toast(content: ToastContent, timeout?: number): string;
+export interface ToastRegionProps {
+  /**
+   * Names the region for assistive tech.
+   *
+   * **Required.** React Aria renders the region as a labelled landmark, and
+   * an unnamed one is announced as "region" with no indication of what just
+   * arrived. It is a prop rather than a default string because
+   * ARCHITECTURE section 7 rule 9 routes user-visible copy through the
+   * consumer until `useMessages()` exists.
+   */
+  label: string;
+  /** Accessible name for each toast's dismiss control. */
+  closeLabel?: string;
+  /** Extra classes for the region. Merged last. */
+  className?: string;
+}
+/**
+ * Renders the queue. Mount ONCE, near the root.
+ *
+ * React Aria only renders the landmark while something is queued, so this
+ * costs nothing on a quiet screen.
+ */
+export declare function ToastRegion({ label, closeLabel, className }: ToastRegionProps): import("react").JSX.Element;
+//#endregion
+//# sourceMappingURL=toast.d.ts.map

package/dist/toast/toast.js

@@ -0,0 +1,145 @@
+"use client";
+import { cn } from "../lib/cn.js";
+import { cva } from "class-variance-authority";
+import { Button, Text, UNSTABLE_Toast, UNSTABLE_ToastContent, UNSTABLE_ToastQueue, UNSTABLE_ToastRegion } from "react-aria-components";
+import { jsx, jsxs } from "react/jsx-runtime";
+//#region src/toast/toast.tsx
+/**
+* Toast: a transient message, announced without stealing focus.
+*
+* Maturity: **experimental**, and the reason is upstream rather than here.
+* React Aria ships this API as `UNSTABLE_Toast*` in 1.21.1, so a RAC minor
+* bump can rename or reshape it. The alternative was hand-rolling the live
+* region, the queue, the timers and the focus behaviour, which is how every
+* toast implementation acquires its accessibility bugs -- so this takes the
+* upstream one and labels the risk instead of hiding it.
+*
+* THE PRODUCT HAS 30 FILES CALLING `useToast` AND 67 `toast(...)` CALLS, and
+* its implementation is the shadcn reducer with both of its known defects
+* still in place:
+*
+*   TOAST_LIMIT = 1          -- a second toast REPLACES the first, so a
+*                               burst of results shows only the last one.
+*   TOAST_REMOVE_DELAY = 1e6 -- sixteen minutes. Nothing auto-dismisses;
+*                               every toast waits to be closed by hand.
+*
+* Neither is ported. `maxVisibleToasts` defaults to 3 and `timeout` to 5s,
+* which is the WCAG 2.2.1 floor React Aria enforces -- it REFUSES a timeout
+* under 5000ms, because a message that vanishes faster cannot be read by
+* someone using a screen magnifier.
+*
+* The queue is a module singleton on purpose. The product's `toast()` is
+* importable from anywhere and called from API error handlers and effects
+* that have no component to hang a hook off, and a context-based queue would
+* have made those 67 call sites into 67 refactors.
+*/
+/** Where the region sits. Fixed, above everything, out of the way of content. */
+const toastRegionVariants = cva([
+	"fixed z-50 flex flex-col gap-2 box-border",
+	"bottom-(--density-bar-pad-y) end-(--density-bar-pad-x)",
+	"w-[min(24rem,calc(100vw-2rem))]",
+	"outline-none"
+]);
+const toastVariants = cva([
+	"flex items-start gap-3 box-border w-full",
+	"rounded-md border-(length:--border-width) p-(--density-bar-pad-x)",
+	"font-sans shadow-surface",
+	"motion-safe:transition-opacity motion-safe:duration-(--duration-fast) motion-safe:ease-standard",
+	"data-[animation=exiting]:opacity-0"
+], {
+	variants: { tone: {
+		neutral: "bg-background border-separator text-foreground",
+		success: "bg-success-subtle border-success-strong text-success-foreground",
+		warning: "bg-warning-subtle border-warning-strong text-warning-foreground",
+		danger: "bg-destructive-subtle border-destructive-strong text-destructive-subtle-foreground",
+		info: "bg-info-subtle border-info-strong text-info-foreground"
+	} },
+	defaultVariants: { tone: "neutral" }
+});
+const toastCloseVariants = cva([
+	"ms-auto shrink-0 rounded-sm cursor-pointer",
+	"text-current opacity-70 data-[hovered]:opacity-100",
+	"outline-none",
+	"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)"
+]);
+/**
+* The queue every `toast()` call feeds.
+*
+* Exported so a consumer can read `visibleToasts` in a test, or dismiss them
+* on a route change -- there is no `clear()` upstream, so that is
+* `[...toastQueue.visibleToasts].forEach((t) => toastQueue.close(t.key))`.
+* Not something to touch in normal use.
+*/
+const toastQueue = new UNSTABLE_ToastQueue({ maxVisibleToasts: 3 });
+/**
+* Show a toast.
+*
+* @example
+* toast({ title: "Report saved" });
+* toast({ title: "Upload failed", description: err.message, tone: "danger" });
+*
+* @param timeout - ms before it dismisses itself. React Aria REFUSES anything
+* under 5000 and anything at all while the region is focused, because a
+* message that disappears before it can be read fails WCAG 2.2.1. Pass 0 to
+* require a manual dismiss, which is right for an error a user must act on.
+*/
+function toast(content, timeout = 5e3) {
+	return toastQueue.add(content, timeout === 0 ? void 0 : { timeout });
+}
+/**
+* Renders the queue. Mount ONCE, near the root.
+*
+* React Aria only renders the landmark while something is queued, so this
+* costs nothing on a quiet screen.
+*/
+function ToastRegion({ label, closeLabel = "Dismiss", className }) {
+	return /* @__PURE__ */ jsx(UNSTABLE_ToastRegion, {
+		queue: toastQueue,
+		"aria-label": label,
+		"data-slot": "toast-region",
+		className: cn(toastRegionVariants(), className),
+		children: ({ toast: queued }) => /* @__PURE__ */ jsxs(UNSTABLE_Toast, {
+			toast: queued,
+			"data-slot": "toast",
+			"data-tone": queued.content.tone ?? "neutral",
+			className: toastVariants({ tone: queued.content.tone }),
+			children: [/* @__PURE__ */ jsxs(UNSTABLE_ToastContent, {
+				"data-slot": "toast-content",
+				className: "flex min-w-0 flex-col gap-1",
+				children: [/* @__PURE__ */ jsx(Text, {
+					slot: "title",
+					"data-slot": "toast-title",
+					className: "text-sm leading-(--leading-snug) font-medium",
+					children: queued.content.title
+				}), queued.content.description == null ? null : /* @__PURE__ */ jsx(Text, {
+					slot: "description",
+					"data-slot": "toast-description",
+					className: "text-sm leading-(--leading-normal) opacity-90",
+					children: queued.content.description
+				})]
+			}), /* @__PURE__ */ jsx(Button, {
+				slot: "close",
+				"aria-label": closeLabel,
+				"data-slot": "toast-close",
+				className: toastCloseVariants(),
+				children: /* @__PURE__ */ jsx("svg", {
+					"aria-hidden": "true",
+					viewBox: "0 0 16 16",
+					fill: "none",
+					stroke: "currentColor",
+					strokeWidth: "1.75",
+					strokeLinecap: "round",
+					className: "size-(--icon-sm)",
+					children: /* @__PURE__ */ jsx("path", { d: "m4 4 8 8M12 4l-8 8" })
+				})
+			})]
+		})
+	});
+}
+//#endregion
+export { ToastRegion, toast, toastCloseVariants, toastQueue, toastRegionVariants, toastVariants };
+
+//# sourceMappingURL=toast.js.map

package/dist/toast/toast.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"toast.js","names":["AriaToastQueue","AriaToastRegion","AriaToast","AriaToastContent","AriaText","AriaButton"],"sources":["../../src/toast/toast.tsx"],"sourcesContent":["\"use client\";\n\nimport { cva, type VariantProps } from \"class-variance-authority\";\nimport type { ReactNode } from \"react\";\nimport {\n  Button as AriaButton,\n  Text as AriaText,\n  UNSTABLE_Toast as AriaToast,\n  UNSTABLE_ToastContent as AriaToastContent,\n  UNSTABLE_ToastQueue as AriaToastQueue,\n  UNSTABLE_ToastRegion as AriaToastRegion,\n} from \"react-aria-components\";\n\nimport { cn } from \"../lib/cn.js\";\n\n/**\n * Toast: a transient message, announced without stealing focus.\n *\n * Maturity: **experimental**, and the reason is upstream rather than here.\n * React Aria ships this API as `UNSTABLE_Toast*` in 1.21.1, so a RAC minor\n * bump can rename or reshape it. The alternative was hand-rolling the live\n * region, the queue, the timers and the focus behaviour, which is how every\n * toast implementation acquires its accessibility bugs -- so this takes the\n * upstream one and labels the risk instead of hiding it.\n *\n * THE PRODUCT HAS 30 FILES CALLING `useToast` AND 67 `toast(...)` CALLS, and\n * its implementation is the shadcn reducer with both of its known defects\n * still in place:\n *\n *   TOAST_LIMIT = 1          -- a second toast REPLACES the first, so a\n *                               burst of results shows only the last one.\n *   TOAST_REMOVE_DELAY = 1e6 -- sixteen minutes. Nothing auto-dismisses;\n *                               every toast waits to be closed by hand.\n *\n * Neither is ported. `maxVisibleToasts` defaults to 3 and `timeout` to 5s,\n * which is the WCAG 2.2.1 floor React Aria enforces -- it REFUSES a timeout\n * under 5000ms, because a message that vanishes faster cannot be read by\n * someone using a screen magnifier.\n *\n * The queue is a module singleton on purpose. The product's `toast()` is\n * importable from anywhere and called from API error handlers and effects\n * that have no component to hang a hook off, and a context-based queue would\n * have made those 67 call sites into 67 refactors.\n */\n\n/** Where the region sits. Fixed, above everything, out of the way of content. */\nexport const toastRegionVariants = cva([\n  \"fixed z-50 flex flex-col gap-2 box-border\",\n  // Logical insets so the stack follows the writing direction.\n  \"bottom-(--density-bar-pad-y) end-(--density-bar-pad-x)\",\n  \"w-[min(24rem,calc(100vw-2rem))]\",\n  \"outline-none\",\n]);\n\nexport const toastVariants = cva(\n  [\n    \"flex items-start gap-3 box-border w-full\",\n    \"rounded-md border-(length:--border-width) p-(--density-bar-pad-x)\",\n    \"font-sans shadow-surface\",\n    \"motion-safe:transition-opacity motion-safe:duration-(--duration-fast) motion-safe:ease-standard\",\n    // Not colour alone: an exiting toast fades AND the region reflows.\n    \"data-[animation=exiting]:opacity-0\",\n  ],\n  {\n    variants: {\n      /*\n       * The same vocabulary as Badge, deliberately. The product's toast had\n       * `default` and `destructive` only, so 38 of its 67 calls pass a variant\n       * that cannot say \"this worked\" -- and a save confirmation styled\n       * identically to a failure is the most common thing a toast gets wrong.\n       */\n      tone: {\n        neutral: \"bg-background border-separator text-foreground\",\n        success: \"bg-success-subtle border-success-strong text-success-foreground\",\n        warning: \"bg-warning-subtle border-warning-strong text-warning-foreground\",\n        danger:\n          \"bg-destructive-subtle border-destructive-strong text-destructive-subtle-foreground\",\n        info: \"bg-info-subtle border-info-strong text-info-foreground\",\n      },\n    },\n    defaultVariants: { tone: \"neutral\" },\n  },\n);\n\nexport const toastCloseVariants = cva([\n  \"ms-auto shrink-0 rounded-sm cursor-pointer\",\n  \"text-current opacity-70 data-[hovered]:opacity-100\",\n  \"outline-none\",\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\n/** What a toast carries. `title` is required: an unnamed toast announces nothing. */\nexport interface ToastContent extends VariantProps<typeof toastVariants> {\n  /** The message. Required -- a toast with only a description announces as loose text. */\n  title: ReactNode;\n  /** Secondary detail, beneath the title. */\n  description?: ReactNode;\n}\n\n/**\n * The queue every `toast()` call feeds.\n *\n * Exported so a consumer can read `visibleToasts` in a test, or dismiss them\n * on a route change -- there is no `clear()` upstream, so that is\n * `[...toastQueue.visibleToasts].forEach((t) => toastQueue.close(t.key))`.\n * Not something to touch in normal use.\n */\nexport const toastQueue = new AriaToastQueue<ToastContent>({\n  /*\n   * Three, against the product's one. Its TOAST_LIMIT of 1 means a second\n   * toast REPLACES the first -- so a page that reports three failed uploads\n   * shows one and silently drops the rest.\n   */\n  maxVisibleToasts: 3,\n});\n\n/**\n * Show a toast.\n *\n * @example\n * toast({ title: \"Report saved\" });\n * toast({ title: \"Upload failed\", description: err.message, tone: \"danger\" });\n *\n * @param timeout - ms before it dismisses itself. React Aria REFUSES anything\n * under 5000 and anything at all while the region is focused, because a\n * message that disappears before it can be read fails WCAG 2.2.1. Pass 0 to\n * require a manual dismiss, which is right for an error a user must act on.\n */\nexport function toast(content: ToastContent, timeout = 5000) {\n  return toastQueue.add(content, timeout === 0 ? undefined : { timeout });\n}\n\nexport interface ToastRegionProps {\n  /**\n   * Names the region for assistive tech.\n   *\n   * **Required.** React Aria renders the region as a labelled landmark, and\n   * an unnamed one is announced as \"region\" with no indication of what just\n   * arrived. It is a prop rather than a default string because\n   * ARCHITECTURE section 7 rule 9 routes user-visible copy through the\n   * consumer until `useMessages()` exists.\n   */\n  label: string;\n  /** Accessible name for each toast's dismiss control. */\n  closeLabel?: string;\n  /** Extra classes for the region. Merged last. */\n  className?: string;\n}\n\n/**\n * Renders the queue. Mount ONCE, near the root.\n *\n * React Aria only renders the landmark while something is queued, so this\n * costs nothing on a quiet screen.\n */\nexport function ToastRegion({ label, closeLabel = \"Dismiss\", className }: ToastRegionProps) {\n  return (\n    <AriaToastRegion\n      queue={toastQueue}\n      aria-label={label}\n      data-slot=\"toast-region\"\n      className={cn(toastRegionVariants(), className)}\n    >\n      {({ toast: queued }) => (\n        <AriaToast\n          toast={queued}\n          data-slot=\"toast\"\n          data-tone={queued.content.tone ?? \"neutral\"}\n          className={toastVariants({ tone: queued.content.tone })}\n        >\n          <AriaToastContent data-slot=\"toast-content\" className=\"flex min-w-0 flex-col gap-1\">\n            {/*\n              slot=\"title\" is what React Aria announces. A plain div here\n              renders identically and leaves the toast unnamed.\n            */}\n            <AriaText\n              slot=\"title\"\n              data-slot=\"toast-title\"\n              className=\"text-sm leading-(--leading-snug) font-medium\"\n            >\n              {queued.content.title}\n            </AriaText>\n            {queued.content.description == null ? null : (\n              <AriaText\n                slot=\"description\"\n                data-slot=\"toast-description\"\n                className=\"text-sm leading-(--leading-normal) opacity-90\"\n              >\n                {queued.content.description}\n              </AriaText>\n            )}\n          </AriaToastContent>\n          <AriaButton\n            slot=\"close\"\n            aria-label={closeLabel}\n            data-slot=\"toast-close\"\n            className={toastCloseVariants()}\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              className=\"size-(--icon-sm)\"\n            >\n              <path d=\"m4 4 8 8M12 4l-8 8\" />\n            </svg>\n          </AriaButton>\n        </AriaToast>\n      )}\n    </AriaToastRegion>\n  );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA8CA,MAAa,sBAAsB,IAAI;CACrC;CAEA;CACA;CACA;AACF,CAAC;AAED,MAAa,gBAAgB,IAC3B;CACE;CACA;CACA;CACA;CAEA;AACF,GACA;CACE,UAAU,EAOR,MAAM;EACJ,SAAS;EACT,SAAS;EACT,SAAS;EACT,QACE;EACF,MAAM;CACR,EACF;CACA,iBAAiB,EAAE,MAAM,UAAU;AACrC,CACF;AAEA,MAAa,qBAAqB,IAAI;CACpC;CACA;CACA;CACA;CACA;CACA;CACA;AACF,CAAC;;;;;;;;;AAkBD,MAAa,aAAa,IAAIA,oBAA6B,EAMzD,kBAAkB,EACpB,CAAC;;;;;;;;;;;;;AAcD,SAAgB,MAAM,SAAuB,UAAU,KAAM;CAC3D,OAAO,WAAW,IAAI,SAAS,YAAY,IAAI,KAAA,IAAY,EAAE,QAAQ,CAAC;AACxE;;;;;;;AAyBA,SAAgB,YAAY,EAAE,OAAO,aAAa,WAAW,aAA+B;CAC1F,OACE,oBAACC,sBAAD;EACE,OAAO;EACP,cAAY;EACZ,aAAU;EACV,WAAW,GAAG,oBAAoB,GAAG,SAAS;EAE5C,WAAA,EAAE,OAAO,aACT,qBAACC,gBAAD;GACE,OAAO;GACP,aAAU;GACV,aAAW,OAAO,QAAQ,QAAQ;GAClC,WAAW,cAAc,EAAE,MAAM,OAAO,QAAQ,KAAK,CAAC;GAJxD,UAAA,CAME,qBAACC,uBAAD;IAAkB,aAAU;IAAgB,WAAU;IAAtD,UAAA,CAKE,oBAACC,MAAD;KACE,MAAK;KACL,aAAU;KACV,WAAU;KAET,UAAA,OAAO,QAAQ;IACR,CAAA,GACT,OAAO,QAAQ,eAAe,OAAO,OACpC,oBAACA,MAAD;KACE,MAAK;KACL,aAAU;KACV,WAAU;KAET,UAAA,OAAO,QAAQ;IACR,CAAA,CAEI;GAClB,CAAA,GAAA,oBAACC,QAAD;IACE,MAAK;IACL,cAAY;IACZ,aAAU;IACV,WAAW,mBAAmB;IAE9B,UAAA,oBAAC,OAAD;KACE,eAAY;KACZ,SAAQ;KACR,MAAK;KACL,QAAO;KACP,aAAY;KACZ,eAAc;KACd,WAAU;KAEV,UAAA,oBAAC,QAAD,EAAM,GAAE,qBAAsB,CAAA;IAC3B,CAAA;GACK,CAAA,CACH;;CAEE,CAAA;AAErB"}

package/dist/tooltip/index.d.ts

@@ -0,0 +1,2 @@
+import { Tooltip, TooltipProps, TooltipTrigger, TooltipTriggerProps, tooltipVariants } from "./tooltip.js";
+export { Tooltip, type TooltipProps, TooltipTrigger, type TooltipTriggerProps, tooltipVariants };

package/dist/tooltip/index.js

@@ -0,0 +1,2 @@
+import { Tooltip, TooltipTrigger, tooltipVariants } from "./tooltip.js";
+export { Tooltip, TooltipTrigger, tooltipVariants };

package/dist/tooltip/tooltip.d.ts

@@ -0,0 +1,70 @@
+import { TooltipProps, TooltipTriggerComponentProps } from "react-aria-components";
+import { ReactNode } from "react";
+//#region src/tooltip/tooltip.d.ts
+/**
+ * Tooltip, ported from the legacy shadcn/Radix component.
+ *
+ * Census: ten files import it but only SEVEN render anything -- three
+ * import the parts and use none. Across those seven: `Tooltip` 34,
+ * `TooltipTrigger` 34, `TooltipContent` 34, `TooltipProvider` 23. `side`
+ * is passed 12 times: `"top"` 11, `"bottom"` once.
+ *
+ * `TooltipProvider` IS NOT PORTED, and that removes 23 call sites rather
+ * than renaming them. The legacy `Tooltip` already wraps itself in a
+ * provider, so every explicit `<TooltipProvider>` in app code nested a
+ * second one inside the first -- harmless, but it also meant the
+ * `skipDelayDuration` grouping the provider exists for never spanned two
+ * tooltips. React Aria has no provider at all; that grouping is
+ * module-global.
+ *
+ * THE DELAY IS THE ONE THING THAT WOULD HAVE CHANGED SILENTLY. The legacy
+ * provider hardcodes `delayDuration = 0`, so all 34 tooltips appear
+ * instantly on hover. React Aria's default is 1500ms. Porting without
+ * noticing would have put a 1.5-second warm-up on every tooltip in the
+ * app, and neither the type system nor the test suite would have said a
+ * word -- so `delay` defaults to 0 here, and a story pins the default.
+ */
+export declare const tooltipVariants: (props?: import("class-variance-authority/types").ClassProp | undefined) => string;
+/**
+ * A hover and focus hint.
+ *
+ * @example
+ * <TooltipTrigger>
+ *   <Button aria-label="Mute"><MicOff /></Button>
+ *   <Tooltip>Mute</Tooltip>
+ * </TooltipTrigger>
+ */
+interface TooltipProps$1 extends Omit<TooltipProps, "className" | "style" | "children"> {
+  children?: ReactNode;
+  /** Extra classes. Merged last, so they win conflicts with ours. */
+  className?: string;
+  /**
+   * Where it opens. The legacy `side` prop: `"top"` 11 times, `"bottom"`
+   * once, and the default for the other 22.
+   *
+   * @default "top"
+   */
+  placement?: TooltipProps["placement"];
+}
+declare function Tooltip$1({ children, className, placement, ...props }: TooltipProps$1): import("react").JSX.Element;
+/**
+ * Pairs a trigger with a tooltip.
+ *
+ * React Aria's `TooltipTrigger`, EXCEPT that `delay` and `closeDelay`
+ * default to 0 to match the legacy provider. React Aria ships 1500ms and
+ * 500ms; taking those defaults would have changed all 34 call sites
+ * without a word.
+ *
+ * Focus opens it immediately whatever `delay` says -- React Aria passes
+ * `immediate` on focus -- which is the behaviour a keyboard user needs.
+ */
+export interface TooltipTriggerProps extends TooltipTriggerComponentProps {
+  /** Hover warm-up in ms. @default 0 */
+  delay?: number;
+  /** Hover cool-down in ms. @default 0 */
+  closeDelay?: number;
+}
+declare function TooltipTrigger$1({ delay, closeDelay, ...props }: TooltipTriggerProps): import("react").JSX.Element;
+//#endregion
+export { Tooltip$1 as Tooltip, TooltipProps$1 as TooltipProps, TooltipTrigger$1 as TooltipTrigger };
+//# sourceMappingURL=tooltip.d.ts.map