@nextlyhq/ui 0.0.2-alpha.60 → 0.0.2-alpha.64

package/dist/index.d.ts

@@ -1128,7 +1128,30 @@ declare const Tabs: react.ForwardRefExoticComponent<_radix_ui_react_tabs.TabsPro
  */
 declare const TabsList: react.ForwardRefExoticComponent<Omit<_radix_ui_react_tabs.TabsListProps & react.RefAttributes<HTMLDivElement>, "ref"> & VariantProps<(props?: ({
     variant?: "default" | "ghost" | null | undefined;
-} & class_variance_authority_types.ClassProp) | undefined) => string> & react.RefAttributes<HTMLDivElement>>;
+} & class_variance_authority_types.ClassProp) | undefined) => string> & {
+    /**
+     * Let a strip too wide for its container scroll sideways.
+     *
+     * The scroll container is a WRAPPER, never the list, and that is why this
+     * prop exists rather than callers reaching for `overflow-x-auto`
+     * themselves. Two things go wrong when the list is the scroller, and the
+     * second is why the obvious remedy is also wrong:
+     *
+     *  - Per the CSS overflow rules, `visible` computes to `auto` when the
+     *    other axis is neither `visible` nor `clip`, so `overflow-x` alone
+     *    always makes the element a VERTICAL scroll container too.
+     *  - `TabsTrigger` carries `-mb-0.5` so its 2px underline lands ON this
+     *    list's rail rather than below it. That pull-up puts content past the
+     *    content-box edge, which the new scroll container reports as vertical
+     *    overflow — so `overflow-y-hidden` would clip the 2px the underline is
+     *    made of, silencing a scrollbar by deleting the indicator.
+     *
+     * With the wrapper scrolling instead, the list keeps its rail and
+     * `w-max min-w-full` makes that rail span the full scroll width rather
+     * than stopping where the triggers do.
+     */
+    scrollable?: boolean;
+} & react.RefAttributes<HTMLDivElement>>;
 /**
  * TabsTrigger - Clickable tab button
  *
@@ -2118,6 +2141,45 @@ declare const CommandShortcut: react.ForwardRefExoticComponent<CommandShortcutPr
  * @experimental
  */
 declare const commandDefaultFilter: (value: string, search: string, keywords?: string[]) => number;
+/**
+ * The value of the item the palette has HIGHLIGHTED, from a component inside
+ * it.
+ *
+ * The palette owns which item is highlighted, and it moves that highlight for
+ * reasons a caller never sees: a pointer crossing an item, an arrow key, and a
+ * filter that removes the item the highlight was on. Anything outside wanting
+ * to follow it — a preview pane, a description strip, a status line — needs to
+ * read that rather than keep a copy.
+ *
+ * Reading beats mirroring here for a specific reason rather than on principle.
+ * The palette's controlled `value` sets which item is MARKED, and does not move
+ * the internal cursor that `aria-activedescendant` and the scroll follow. So a
+ * caller that writes the value to steer the highlight desynchronises the two:
+ * the item drawn as current and the option announced as current stop agreeing,
+ * and after a filter the announcement can name an element that has been
+ * removed. A read leaves one owner and takes a derived view.
+ *
+ * NARROWED to the one field deliberately. The underlying library exposes its
+ * whole store through a selector — the raw search text, its internal item and
+ * group maps, the id it uses for `aria-activedescendant` — and publishing that
+ * selector would make every one of those part of this kit's public API and its
+ * generated declarations. A dependency upgrade could then reshape what callers
+ * can reach without any export changing name, which is exactly what the
+ * surface snapshot cannot see. This returns a string.
+ *
+ * Empty string means nothing is highlighted, which is the library's own
+ * spelling and a different answer from "an item whose value is unknown".
+ *
+ * Must be called from inside the palette, since that is where the state lives.
+ *
+ * Bound to a declaration rather than re-exported with `export { x as y }`: the
+ * bundler keeps a doc comment attached to a declaration and drops one attached
+ * to an export statement, so the release tag would not reach the published
+ * types.
+ *
+ * @experimental
+ */
+declare const useCommandHighlight: () => string;
 
 /**
  * Spinner Component - Design System Specification
@@ -2557,6 +2619,27 @@ declare const ContextMenuShortcut: {
     displayName: string;
 };
 
+/**
+ * A splitter's accessible name, which the caller must supply one way or the
+ * other.
+ *
+ * REQUIRED rather than documented, because the handle is focusable: a keyboard
+ * user lands on it whether or not anyone remembered, and an unnamed separator
+ * announces its position — "74" — with nothing saying what is at 74. The
+ * caller is the only one who can name it, since only the caller knows what the
+ * two panels hold, so the type is the only place the requirement can live.
+ *
+ * Either attribute satisfies it and neither may be paired with the other: two
+ * names on one element is not a stronger label, it is an ambiguity resolved by
+ * precedence rules nobody writing the call site is thinking about.
+ */
+type SplitterName = {
+    "aria-label": string;
+    "aria-labelledby"?: never;
+} | {
+    "aria-labelledby": string;
+    "aria-label"?: never;
+};
 /**
  * A group of resizable panels, laid out horizontally or vertically.
  *
@@ -2578,7 +2661,7 @@ declare const ResizablePanel: typeof ResizablePrimitive.Panel;
  *
  * @experimental
  */
-declare const ResizableHandle: ({ withGrip, className, children, ...props }: react.ComponentProps<typeof ResizablePrimitive.Separator> & {
+declare const ResizableHandle: ({ withGrip, className, children, ...props }: Omit<react.ComponentProps<typeof ResizablePrimitive.Separator>, "aria-label" | "aria-labelledby"> & SplitterName & {
     withGrip?: boolean;
 }) => react_jsx_runtime.JSX.Element;
 
@@ -2664,6 +2747,21 @@ interface TreeNode {
     /** Skipped by every keyboard move and not selectable. */
     disabled?: boolean;
 }
+/**
+ * Which gesture a row's modifiers meant.
+ *
+ * Named by the same three words the rest of the system uses, so a caller maps
+ * them onto its own selection rules without translating. Both Meta and Control
+ * mean toggle: a Mac author presses Command and a Windows author presses
+ * Control, and neither ever presses the other's.
+ *
+ * Shift outranks the toggle modifier — a shift+mod click is a slip rather than
+ * a fourth gesture, and extending is the one whose result is visible and undone
+ * by a plain click.
+ *
+ * @experimental
+ */
+type TreeSelectionMode = "replace" | "toggle" | "extend";
 /** @experimental */
 interface TreeViewProps extends Omit<react.HTMLAttributes<HTMLDivElement>, "onSelect"> {
     /** The roots of the tree. */
@@ -2674,12 +2772,27 @@ interface TreeViewProps extends Omit<react.HTMLAttributes<HTMLDivElement>, "onSe
     defaultExpandedIds?: readonly string[];
     /** Called with the full next set whenever a branch opens or closes. */
     onExpandedChange?: (ids: string[]) => void;
-    /** The selected node id, if the caller owns it. */
+    /**
+     * The selected node id, if the caller owns it.
+     *
+     * With `selectedIds` also supplied this is the PRIMARY — the row a detail
+     * panel answers for. Drawn at a heavier weight so a reader can tell which
+     * member of a multi-row selection the rest of the screen describes.
+     */
     selectedId?: string | null;
+    /**
+     * Every selected id, when the caller holds more than one.
+     *
+     * Additive: omit it and the tree behaves exactly as it did. Supplying it also
+     * makes the tree announce itself as `aria-multiselectable`, which is why it
+     * is a separate prop rather than inferred — a single-select tree claiming to
+     * be multi-selectable is wrong in a way a screen-reader user acts on.
+     */
+    selectedIds?: readonly string[];
     /** Which id starts selected when the caller does not own selection. */
     defaultSelectedId?: string | null;
     /** Called when a row is chosen, by pointer or by Enter. */
-    onSelectedChange?: (id: string) => void;
+    onSelectedChange?: (id: string, mode: TreeSelectionMode) => void;
     /**
      * Names the tree for a screen reader. One of this or `aria-labelledby` is required: a tree
      * announced only as "tree" tells a user nothing about which one they are in.
@@ -2882,8 +2995,10 @@ interface ShortcutLayerOptions {
      * Fixing it needs the manager to record when a layer is ACTIVATED, which registration order
      * does not capture: `useShortcuts` registers once at mount and updates its options in place, so
      * a layer enabled later still carries its mount-time sequence. Not attempted here because
-     * nothing reaches it yet — `priority` is new and one layer sets it, so no two layers currently
-     * share a nonzero value.
+     * nothing reaches it yet: the layers that raise priority are modal HOLDS, and a hold blocks the
+     * keystroke that would open the next one — the command palette cannot be summoned over a dialog
+     * that is already holding, so two of them are not both active for a keystroke to be resolved
+     * between.
      */
     priority?: number;
     /** Whether the layer participates at all. A disabled layer neither matches nor blocks. */
@@ -3046,6 +3161,27 @@ declare function useShortcutManager(): ShortcutManager;
  */
 declare function useActiveShortcuts(): readonly ActiveShortcut[];
 
+/**
+ * A layout effect in the browser, a plain effect where there is no DOM.
+ *
+ * These components are client code, but a consumer may still PRERENDER them,
+ * and React warns that `useLayoutEffect` does nothing on the server. Layout
+ * timing is what the browser needs wherever an effect has to be settled before
+ * anything else can observe it — a registration that must exist before the
+ * first frame, or a native listener that must be the current one before the
+ * next event reaches it. Neither effect runs during a server render, so
+ * choosing between them by environment loses nothing and silences a warning
+ * that reports no real problem.
+ *
+ * Published rather than kept beside its first caller, because a second one
+ * arrived: two spellings of this choice would drift the first time either
+ * learned something about a new environment. A third now lives in another
+ * package, which is why it leaves this one through the barrel.
+ *
+ * @experimental
+ */
+declare const useIsomorphicLayoutEffect: typeof react.useEffect;
+
 /**
  * Parsing and matching for keyboard shortcut specifications.
  *
@@ -3094,6 +3230,43 @@ type KeySequence = readonly KeyChord[];
  * @experimental
  */
 declare function parseKeys(spec: string): KeySequence;
+/**
+ * The modifier state an event carries, with `mod` already resolved for the platform.
+ *
+ * @experimental
+ */
+interface ModifierState {
+    readonly ctrlKey: boolean;
+    readonly metaKey: boolean;
+    readonly altKey: boolean;
+    readonly shiftKey: boolean;
+    /** Optional, so a caller driving the matcher by hand need not synthesise one. */
+    readonly getModifierState?: (key: string) => boolean;
+}
+/**
+ * Whether a chord describes the given keystroke.
+ *
+ * Modifiers are matched EXACTLY rather than as a minimum: a binding for `s` must not fire on
+ * `mod+s`, which is a different shortcut and very often a destructive one.
+ *
+ * @param chord - The chord to test.
+ * @param key - The event's `key`.
+ * @param state - The event's modifier flags.
+ * @param isApple - Whether `mod` should resolve to Command rather than Control.
+ *
+ * @experimental
+ */
+declare function chordMatches(chord: KeyChord, key: string, state: ModifierState, isApple: boolean): boolean;
+/**
+ * Whether this platform uses Command as its primary modifier.
+ *
+ * Reads the modern `userAgentData` hint before the deprecated `navigator.platform`, and answers
+ * `false` when neither exists — the non-Apple default is also the correct answer for a server
+ * render, where no keystroke can arrive.
+ *
+ * @experimental
+ */
+declare function detectApplePlatform(): boolean;
 
 /**
  * How wide a field's CONTROL may grow.
@@ -3160,17 +3333,6 @@ interface FieldShellProps {
      */
     children: React.ReactElement | ((field: FieldShellRenderProps) => React.ReactNode);
 }
-/**
- * The page measure. "form" suits most pages; "wide" is opt-in for dense ones.
- * @experimental
- */
-type FormMeasure = "form" | "wide";
-/** @experimental */
-interface FormLayoutProps {
-    width?: FormMeasure;
-    className?: string;
-    children: React.ReactNode;
-}
 /** @experimental */
 interface FormActionsProps {
     /**
@@ -3207,11 +3369,7 @@ interface FormSectionProps {
 declare function FormSection({ label, description, className, children, }: FormSectionProps): react_jsx_runtime.JSX.Element;
 
 /**
- * @experimental
- */
-declare function FormLayout({ width, className, children, }: FormLayoutProps): react_jsx_runtime.JSX.Element;
-/**
- * One action bar per form, at the end of the measure.
+ * One action bar per form, at the end of the page's measure.
  *
  * A form commits as a single document, so there is one place to commit it. The
  * dirty flag arrives from the page because the form state already answers that
@@ -3221,4 +3379,124 @@ declare function FormLayout({ width, className, children, }: FormLayoutProps): r
  */
 declare function FormActions({ dirty, className, children }: FormActionsProps): react_jsx_runtime.JSX.Element;
 
-export { Accordion, AccordionContent, type AccordionContentProps, AccordionItem, type AccordionItemProps, type AccordionProps, AccordionTrigger, type AccordionTriggerProps, type ActionCallbacks, type ActiveShortcut, Alert, AlertDescription, type AlertDescriptionProps, AlertDialog, AlertDialogAction, type AlertDialogActionProps, AlertDialogCancel, type AlertDialogCancelProps, AlertDialogContent, type AlertDialogContentProps, AlertDialogDescription, type AlertDialogDescriptionProps, AlertDialogFooter, type AlertDialogFooterProps, AlertDialogHeader, type AlertDialogHeaderProps, AlertDialogOverlay, type AlertDialogOverlayProps, AlertDialogPortal, AlertDialogTitle, type AlertDialogTitleProps, AlertDialogTrigger, type AlertProps, AlertTitle, type AlertTitleProps, Avatar, AvatarFallback, type AvatarFallbackProps, AvatarImage, type AvatarImageProps, type AvatarProps, Badge, type BadgeProps, Button, type ButtonProps, Card, CardAction, type CardActionProps, CardContent, type CardContentProps, CardDescription, type CardDescriptionProps, CardFooter, type CardFooterProps, CardHeader, type CardHeaderProps, type CardProps, CardTitle, type CardTitleProps, Checkbox, Collapsible, CollapsibleContent, CollapsibleTrigger, ColorPicker, type ColorPickerProps, type ColorSwatch, Command, CommandDialog, type CommandDialogProps, CommandEmpty, type CommandEmptyProps, CommandGroup, type CommandGroupProps, CommandInput, type CommandInputProps, CommandItem, type CommandItemProps, CommandList, type CommandListProps, type CommandProps, CommandSeparator, type CommandSeparatorProps, CommandShortcut, type CommandShortcutProps, ContextMenu, ContextMenuCheckboxItem, ContextMenuContent, ContextMenuGroup, ContextMenuItem, ContextMenuLabel, ContextMenuRadioGroup, ContextMenuRadioItem, ContextMenuSeparator, ContextMenuShortcut, ContextMenuSub, ContextMenuSubContent, ContextMenuSubTrigger, ContextMenuTrigger, type DataFetcher, Dialog, DialogClose, DialogContent, type DialogContentProps, DialogDescription, type DialogDescriptionProps, DialogFooter, type DialogFooterProps, DialogHeader, type DialogHeaderProps, DialogOverlay, type DialogOverlayProps, DialogPortal, DialogTitle, type DialogTitleProps, DialogTrigger, DropdownMenu, DropdownMenuCheckboxItem, type DropdownMenuCheckboxItemProps, DropdownMenuContent, type DropdownMenuContentProps, DropdownMenuGroup, DropdownMenuItem, type DropdownMenuItemProps, DropdownMenuLabel, type DropdownMenuLabelProps, DropdownMenuPortal, DropdownMenuRadioGroup, DropdownMenuRadioItem, type DropdownMenuRadioItemProps, DropdownMenuSeparator, type DropdownMenuSeparatorProps, DropdownMenuShortcut, type DropdownMenuShortcutProps, DropdownMenuSub, DropdownMenuSubContent, type DropdownMenuSubContentProps, DropdownMenuSubTrigger, type DropdownMenuSubTriggerProps, DropdownMenuTrigger, FieldShell, type FieldShellProps, type FieldShellRenderProps, type FieldWidth, type FilterInfo, FormActions, type FormActionsProps, FormLabelWithTooltip, type FormLabelWithTooltipProps, FormLayout, type FormLayoutProps, type FormMeasure, FormSection, type FormSectionProps, Grid, type GridProps, Input, type InputProps, type KeyChord, type KeySequence, Label, type ListResponse, type PaginationConfig, type PaginationMeta, Popover, PopoverAnchor, PopoverContent, PopoverTrigger, PortalProvider, Progress, type ProgressProps, RadioGroup, RadioGroupItem, ResizableHandle, ResizablePanel, ResizablePanelGroup, Select, SelectContent, SelectGroup, SelectItem, SelectLabel, SelectScrollDownButton, SelectScrollUpButton, SelectSeparator, SelectTrigger, type SelectTriggerProps, SelectValue, Separator, Sheet, SheetClose, type SheetCloseProps, SheetContent, type SheetContentProps, type SheetContentRef, SheetDescription, type SheetDescriptionProps, type SheetDescriptionRef, SheetFooter, type SheetFooterProps, SheetHeader, type SheetHeaderProps, SheetOverlay, type SheetOverlayProps, type SheetOverlayRef, SheetPortal, type SheetProps, SheetTitle, type SheetTitleProps, type SheetTitleRef, SheetTrigger, type SheetTriggerProps, type ShortcutBinding, type ShortcutLayerOptions, type ShortcutManager, type ShortcutManagerOptions, ShortcutProvider, type ShortcutProviderProps, type ShortcutRegistration, ShortcutScope, Skeleton, type SkeletonProps, Slider, type SliderProps, type SliderThumbProps, type SortInfo, Spinner, type SpinnerProps, Stack, type StackProps, Stat, type StatProps, Switch, Table, TableBody, TableCaption, TableCell, TableEmpty, type TableEmptyProps, TableError, type TableErrorProps, TableFooter, TableHead, TableHeader, TableLoading, type TableParams, TableRow, TableSearch, type TableSearchProps, TableSkeleton, type TableSkeletonProps, Tabs, TabsContent, type TabsContentProps, TabsList, type TabsListProps, type TabsProps, TabsTrigger, type TabsTriggerProps, Textarea, Toaster, Tooltip, TooltipContent, TooltipProvider, TooltipTrigger, type TreeNode, TreeView, type TreeViewProps, type UseShortcutsOptions, alertVariants, avatarVariants, badgeVariants, buttonVariants, cardVariants, commandDefaultFilter, createShortcutManager, dialogContentVariants, inputVariants, parseKeys, progressVariants, selectTriggerVariants, sheetVariants, spinnerVariants, useActiveShortcuts, usePortalContainer, useShortcutManager, useShortcuts };
+/** @experimental */
+interface PageShellProps extends HTMLAttributes<HTMLDivElement> {
+    /**
+     * Which measure the content column is bounded to. `full` removes the cap so
+     * the column takes whatever the panel gives it, while KEEPING the gutter — a
+     * full-width page is still inset from the panel's edge.
+     */
+    width?: "form" | "wide" | "full";
+}
+/**
+ * What each named width resolves to, owned here because this is what applies it.
+ *
+ * Declared as a lookup rather than branched at the call site so the three arms
+ * are one list. A `switch` here would let a fourth width be added to the type
+ * and forgotten in the mapping, which the checker cannot see through a
+ * `default` arm.
+ *
+ * Exported because a caller whose CONTENT carries the measure needs the same
+ * value as a length, and the alternative is a second table naming the same
+ * tokens — which drifts silently, since both look correct beside their own
+ * neighbours. Reading it here means there is one answer rather than two that
+ * agree today.
+ *
+ * @experimental
+ */
+declare const SHELL_MEASURE: Record<NonNullable<PageShellProps["width"]>, string>;
+/**
+ * The page's inset and measure, owned in one place and spent as GRID COLUMNS.
+ *
+ * This replaces a pairing in which an outer container padded the panel and an
+ * inner one padded again while capping the width. That shape had three
+ * defects, and all three are structural rather than cosmetic:
+ *
+ *  - The two insets ADDED, because padding is not something a descendant can
+ *    cancel. Measured on the settings page, the header sat at x=360 and the
+ *    form card at x=384 — a 24px disagreement between two elements that are
+ *    supposed to share a left edge. Here the inset is a column, so there is one
+ *    declaration and no second site to disagree with it.
+ *  - A measure applied INSIDE a form component lets anything the page renders
+ *    beside that form escape it. With the page owning the shell, a sibling is
+ *    inside the measure by default and leaves it only by saying `Bleed`.
+ *  - Centring by `mx-auto` on a max-width box does nothing at panel widths
+ *    where the cap does not bind. Here the two outer tracks are equal and
+ *    flexible, so the content column is centred at every width and no
+ *    `justify-content` is declared — with flexible tracks the grid fills its
+ *    container and there is no free space for one to distribute.
+ *
+ * Vertical padding stays ordinary `padding-block`: it is not in tension with
+ * the columns, and keeping it here means one component answers the whole of
+ * "how far is content from the panel's edge".
+ * @experimental
+ */
+declare const PageShell: react.ForwardRefExoticComponent<PageShellProps & react.RefAttributes<HTMLDivElement>>;
+/** @experimental */
+type BleedProps = HTMLAttributes<HTMLDivElement>;
+/**
+ * Opts one child out of the measure, edge to edge across the shell's gutter.
+ *
+ * The sanctioned form of something that previously only happened by accident.
+ * A wide data table, a delivery log or a toolbar declares that it wants the
+ * full panel, so a reviewer can see the intent — and, just as usefully, a block
+ * that is merely in the wrong place no longer LOOKS like a deliberate
+ * full-bleed.
+ *
+ * Valid only as a DIRECT child of `PageShell`. The `full-start`/`full-end`
+ * lines are named on the shell's own grid, so they are in scope for its
+ * children and nowhere else; nested inside a `FormSection` this renders a plain
+ * block and the `grid-column` is inert. That is a real constraint rather than a
+ * stylistic preference, and `page-shell.test.tsx` pins both halves: that a
+ * `Bleed` rendered directly under the shell is its child, and that one nested a
+ * level deeper does NOT receive the full column.
+ *
+ * It forwards its ref and any div attributes for the same reason: a consumer
+ * cannot reach for the usual remedy of wrapping it, because a wrapper is
+ * precisely what makes it stop working.
+ * @experimental
+ */
+declare const Bleed: react.ForwardRefExoticComponent<BleedProps & react.RefAttributes<HTMLDivElement>>;
+
+/** @experimental */
+interface PageHeaderProps extends Omit<HTMLAttributes<HTMLElement>, "title"> {
+    /** The page's name, rendered as its `h1`. */
+    title: string;
+    /**
+     * A sentence under the title. A `ReactNode` rather than a string because a
+     * description carrying a link or an inline code span is ordinary here, and
+     * typing it narrowly would push those pages back to hand-rolling the header.
+     */
+    description?: ReactNode;
+    /** The trail above the title. The page supplies it; this only places it. */
+    breadcrumbs?: ReactNode;
+    /** Page-level actions, trailing the title on one line where there is room. */
+    actions?: ReactNode;
+}
+/**
+ * A page's own identity — its trail, its name, its one-line summary and its
+ * actions — rendered once instead of at every page that needs one.
+ *
+ * Every value arrives as a PROP, and that is the point rather than an
+ * implementation detail. The markup this replaces was written out by hand on 22
+ * pages, and the settings pages took their title from a ~130-line chain that
+ * matched `window.location.pathname` in a file none of them import. Both are
+ * the same defect from opposite ends: a page knows what it is, and nothing let
+ * it say so — so the title lived either in 22 copies or in one foreign file
+ * that had to be edited whenever a route was added.
+ *
+ * The route registry already made this decision for the sidebar. A private
+ * route must DECLARE the rail section it belongs to, because the sidebar reads
+ * that declaration rather than matching the URL, which makes a route added
+ * without one a compile error instead of a page that silently highlights the
+ * wrong entry. A title derived from a pathname is the same defect in the half
+ * nobody had covered.
+ *
+ * It also makes a plugin's page indistinguishable from a first-party one: a
+ * plugin cannot add a branch to an if-chain it does not ship, but it can pass a
+ * prop.
+ * @experimental
+ */
+declare const PageHeader: react.ForwardRefExoticComponent<PageHeaderProps & react.RefAttributes<HTMLElement>>;
+
+export { Accordion, AccordionContent, type AccordionContentProps, AccordionItem, type AccordionItemProps, type AccordionProps, AccordionTrigger, type AccordionTriggerProps, type ActionCallbacks, type ActiveShortcut, Alert, AlertDescription, type AlertDescriptionProps, AlertDialog, AlertDialogAction, type AlertDialogActionProps, AlertDialogCancel, type AlertDialogCancelProps, AlertDialogContent, type AlertDialogContentProps, AlertDialogDescription, type AlertDialogDescriptionProps, AlertDialogFooter, type AlertDialogFooterProps, AlertDialogHeader, type AlertDialogHeaderProps, AlertDialogOverlay, type AlertDialogOverlayProps, AlertDialogPortal, AlertDialogTitle, type AlertDialogTitleProps, AlertDialogTrigger, type AlertProps, AlertTitle, type AlertTitleProps, Avatar, AvatarFallback, type AvatarFallbackProps, AvatarImage, type AvatarImageProps, type AvatarProps, Badge, type BadgeProps, Bleed, type BleedProps, Button, type ButtonProps, Card, CardAction, type CardActionProps, CardContent, type CardContentProps, CardDescription, type CardDescriptionProps, CardFooter, type CardFooterProps, CardHeader, type CardHeaderProps, type CardProps, CardTitle, type CardTitleProps, Checkbox, Collapsible, CollapsibleContent, CollapsibleTrigger, ColorPicker, type ColorPickerProps, type ColorSwatch, Command, CommandDialog, type CommandDialogProps, CommandEmpty, type CommandEmptyProps, CommandGroup, type CommandGroupProps, CommandInput, type CommandInputProps, CommandItem, type CommandItemProps, CommandList, type CommandListProps, type CommandProps, CommandSeparator, type CommandSeparatorProps, CommandShortcut, type CommandShortcutProps, ContextMenu, ContextMenuCheckboxItem, ContextMenuContent, ContextMenuGroup, ContextMenuItem, ContextMenuLabel, ContextMenuRadioGroup, ContextMenuRadioItem, ContextMenuSeparator, ContextMenuShortcut, ContextMenuSub, ContextMenuSubContent, ContextMenuSubTrigger, ContextMenuTrigger, type DataFetcher, Dialog, DialogClose, DialogContent, type DialogContentProps, DialogDescription, type DialogDescriptionProps, DialogFooter, type DialogFooterProps, DialogHeader, type DialogHeaderProps, DialogOverlay, type DialogOverlayProps, DialogPortal, DialogTitle, type DialogTitleProps, DialogTrigger, DropdownMenu, DropdownMenuCheckboxItem, type DropdownMenuCheckboxItemProps, DropdownMenuContent, type DropdownMenuContentProps, DropdownMenuGroup, DropdownMenuItem, type DropdownMenuItemProps, DropdownMenuLabel, type DropdownMenuLabelProps, DropdownMenuPortal, DropdownMenuRadioGroup, DropdownMenuRadioItem, type DropdownMenuRadioItemProps, DropdownMenuSeparator, type DropdownMenuSeparatorProps, DropdownMenuShortcut, type DropdownMenuShortcutProps, DropdownMenuSub, DropdownMenuSubContent, type DropdownMenuSubContentProps, DropdownMenuSubTrigger, type DropdownMenuSubTriggerProps, DropdownMenuTrigger, FieldShell, type FieldShellProps, type FieldShellRenderProps, type FieldWidth, type FilterInfo, FormActions, type FormActionsProps, FormLabelWithTooltip, type FormLabelWithTooltipProps, FormSection, type FormSectionProps, Grid, type GridProps, Input, type InputProps, type KeyChord, type KeySequence, Label, type ListResponse, type ModifierState, PageHeader, type PageHeaderProps, PageShell, type PageShellProps, type PaginationConfig, type PaginationMeta, Popover, PopoverAnchor, PopoverContent, PopoverTrigger, PortalProvider, Progress, type ProgressProps, RadioGroup, RadioGroupItem, ResizableHandle, ResizablePanel, ResizablePanelGroup, SHELL_MEASURE, Select, SelectContent, SelectGroup, SelectItem, SelectLabel, SelectScrollDownButton, SelectScrollUpButton, SelectSeparator, SelectTrigger, type SelectTriggerProps, SelectValue, Separator, Sheet, SheetClose, type SheetCloseProps, SheetContent, type SheetContentProps, type SheetContentRef, SheetDescription, type SheetDescriptionProps, type SheetDescriptionRef, SheetFooter, type SheetFooterProps, SheetHeader, type SheetHeaderProps, SheetOverlay, type SheetOverlayProps, type SheetOverlayRef, SheetPortal, type SheetProps, SheetTitle, type SheetTitleProps, type SheetTitleRef, SheetTrigger, type SheetTriggerProps, type ShortcutBinding, type ShortcutLayerOptions, type ShortcutManager, type ShortcutManagerOptions, ShortcutProvider, type ShortcutProviderProps, type ShortcutRegistration, ShortcutScope, Skeleton, type SkeletonProps, Slider, type SliderProps, type SliderThumbProps, type SortInfo, Spinner, type SpinnerProps, Stack, type StackProps, Stat, type StatProps, Switch, Table, TableBody, TableCaption, TableCell, TableEmpty, type TableEmptyProps, TableError, type TableErrorProps, TableFooter, TableHead, TableHeader, TableLoading, type TableParams, TableRow, TableSearch, type TableSearchProps, TableSkeleton, type TableSkeletonProps, Tabs, TabsContent, type TabsContentProps, TabsList, type TabsListProps, type TabsProps, TabsTrigger, type TabsTriggerProps, Textarea, Toaster, Tooltip, TooltipContent, TooltipProvider, TooltipTrigger, type TreeNode, TreeView, type TreeViewProps, type UseShortcutsOptions, alertVariants, avatarVariants, badgeVariants, buttonVariants, cardVariants, chordMatches, commandDefaultFilter, createShortcutManager, detectApplePlatform, dialogContentVariants, inputVariants, parseKeys, progressVariants, selectTriggerVariants, sheetVariants, spinnerVariants, useActiveShortcuts, useCommandHighlight, useIsomorphicLayoutEffect, usePortalContainer, useShortcutManager, useShortcuts };