bits-ui 0.21.1 → 0.21.3

package/dist/bits/menu/_types.d.ts

@@ -1,82 +0,0 @@
-/**
- * Shared internal types for the various menu components.
- */
-import type { DOMElement, OmitChecked, OmitFloating, OnChangeFn } from "../../internal/index.js";
-import type { CreateContextMenuCheckboxItemProps, CreateContextMenuRadioGroupProps, ContextMenuRadioItemProps, CreateContextSubmenuProps, CreateContextMenuProps } from "@melt-ui/svelte";
-import type { ArrowProps as FloatingArrowProps, ContentProps } from "../floating/_types.js";
-export type Props = Expand<OmitFloating<CreateContextMenuProps> & {
-    /**
-     * The open state of the context menu.
-     * You can bind this to a boolean value to programmatically control the open state.
-     *
-     * @defaultValue false
-     */
-    open?: boolean;
-    /**
-     * A callback function called when the open state changes.
-     */
-    onOpenChange?: OnChangeFn<boolean>;
-}>;
-export type SubTriggerProps = Expand<{
-    /**
-     * Whether the subtrigger is disabled or not.
-     *
-     * @defaultValue false;
-     */
-    disabled?: boolean;
-} & DOMElement>;
-export type CheckboxItemProps = Expand<OmitChecked<CreateContextMenuCheckboxItemProps> & {
-    /**
-     * The checked state of the checkbox item.
-     * You can bind this to a boolean value to programmatically control the checked state.
-     *
-     * @defaultValue false
-     */
-    checked?: boolean | "indeterminate";
-    /**
-     * A callback function called when the checked state changes.
-     */
-    onCheckedChange?: OnChangeFn<boolean | "indeterminate">;
-} & DOMElement>;
-export type RadioGroupProps = Expand<{
-    /**
-     * The value of the radio group.
-     *
-     * @defaultValue undefined
-     */
-    value?: CreateContextMenuRadioGroupProps["defaultValue"] & {};
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<CreateContextMenuRadioGroupProps["defaultValue"]>;
-} & DOMElement>;
-export type RadioItemProps = Expand<ContextMenuRadioItemProps & DOMElement>;
-export type SubProps = Expand<OmitFloating<CreateContextSubmenuProps> & {
-    /**
-     * The open state of the submenu.
-     * You can bind this to a boolean value to programmatically control the open state.
-     *
-     * @defaultValue false
-     */
-    open?: boolean;
-    /**
-     * A callback function called when the open state changes.
-     */
-    onOpenChange?: OnChangeFn<boolean>;
-}>;
-export type ItemProps = Expand<{
-    /**
-     * Whether the item is disabled.
-     *
-     * @defaultValue false
-     */
-    disabled?: boolean;
-} & DOMElement>;
-export type ArrowProps = FloatingArrowProps;
-export type GroupProps = DOMElement;
-export type CheckboxIndicatorProps = DOMElement;
-export type RadioIndicatorProps = DOMElement;
-export type LabelProps = DOMElement;
-export type SeparatorProps = DOMElement;
-export type TriggerProps = DOMElement<HTMLElement>;
-export type { ContentProps, ContentProps as SubContentProps };

package/dist/bits/menu/_types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/menubar/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as MenubarProps, SubProps as MenubarSubProps, MenuProps as MenubarMenuProps, ItemProps as MenubarItemProps, ArrowProps as MenubarArrowProps, GroupProps as MenubarGroupProps, LabelProps as MenubarLabelProps, TriggerProps as MenubarTriggerProps, ContentProps as MenubarContentProps, RadioItemProps as MenubarRadioItemProps, SeparatorProps as MenubarSeparatorProps, RadioGroupProps as MenubarRadioGroupProps, SubContentProps as MenubarSubContentProps, SubTriggerProps as MenubarSubTriggerProps, CheckboxItemProps as MenubarCheckboxItemProps, RadioIndicatorProps as MenubarRadioIndicatorProps, CheckboxIndicatorProps as MenubarCheckboxIndicatorProps, ItemEvents as MenubarItemEvents, TriggerEvents as MenubarTriggerEvents, ContentEvents as MenubarContentEvents, RadioItemEvents as MenubarRadioItemEvents, SubTriggerEvents as MenubarSubTriggerEvents, SubContentEvents as MenubarSubContentEvents, CheckboxItemEvents as MenubarCheckboxItemEvents, } from "./types.js";

package/dist/bits/menubar/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/menubar/_types.d.ts

@@ -1,9 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { DOMElement, Expand, OmitIds } from "../../internal/index.js";
-import type { CreateMenubarProps } from "@melt-ui/svelte";
-type Props = Expand<OmitIds<CreateMenubarProps> & DOMElement>;
-export type { Props };

package/dist/bits/menubar/_types.js

@@ -1,6 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-export {};

package/dist/bits/pagination/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as PaginationProps, PrevButtonProps as PaginationPrevButtonProps, NextButtonProps as PaginationNextButtonProps, PageProps as PaginationPageProps, Events as PaginationEvents, PrevButtonEvents as PaginationPrevButtonEvents, NextButtonEvents as PaginationNextButtonEvents, PageEvents as PaginationPageEvents, } from "./types.js";

package/dist/bits/pagination/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/pagination/_types.d.ts

@@ -1,26 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { DOMElement, Expand, OnChangeFn } from "../../internal/index.js";
-import type { CreatePaginationProps, Page } from "@melt-ui/svelte";
-type OmitPaginationProps<T> = Omit<T, "page" | "defaultPage" | "onPageChange">;
-type Props = Expand<OmitPaginationProps<CreatePaginationProps> & {
-    /**
-     * The selected page. This updates as the users selects new pages.
-     *
-     * You can bind this to a value to programmatically control the value state.
-     */
-    page?: number;
-    /**
-     * A callback function called when the page changes.
-     */
-    onPageChange?: OnChangeFn<number>;
-} & DOMElement>;
-type PageProps = {
-    page: Page;
-} & DOMElement<HTMLButtonElement>;
-type PrevButtonProps = DOMElement<HTMLButtonElement>;
-type NextButtonProps = DOMElement<HTMLButtonElement>;
-export type { Props, PrevButtonProps, NextButtonProps, PageProps };

package/dist/bits/pagination/_types.js

@@ -1,6 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-export {};

package/dist/bits/pin-input/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props, InputProps as PinInputProps, HiddenInputProps as PinInputHiddenInputProps, } from "./types.js";

package/dist/bits/pin-input/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/pin-input/_types.d.ts

@@ -1,22 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { CreatePinInputProps } from "@melt-ui/svelte";
-import type { DOMElement, Expand, OmitIds, OmitValue, OnChangeFn } from "../../internal/index.js";
-type Props = Expand<OmitIds<OmitValue<CreatePinInputProps> & {
-    /**
-     * The value pin-input, which is an array of strings.
-     *
-     * You can bind to this to programmatically control the value.
-     */
-    value?: CreatePinInputProps["defaultValue"];
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<CreatePinInputProps["defaultValue"]>;
-} & DOMElement>>;
-type InputProps = DOMElement<HTMLInputElement>;
-type HiddenInputProps = DOMElement<HTMLInputElement>;
-export type { Props, InputProps, HiddenInputProps };

package/dist/bits/pin-input/_types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/popover/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as PopoverProps, ArrowProps as PopoverArrowProps, CloseProps as PopoverCloseProps, ContentProps as PopoverContentProps, TriggerProps as PopoverTriggerProps, TriggerEvents as PopoverTriggerEvents, CloseEvents as PopoverCloseEvents, } from "./types.js";

package/dist/bits/popover/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/popover/_types.d.ts

@@ -1,24 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { Expand, OnChangeFn, OmitFloating, DOMElement } from "../../internal/index.js";
-import type { ArrowProps, ContentProps } from "../floating/_types.js";
-import type { CreatePopoverProps } from "@melt-ui/svelte";
-type Props = Expand<OmitFloating<CreatePopoverProps> & {
-    /**
-     * The open state of the popover.
-     * You can bind this to a boolean value to programmatically control the open state.
-     *
-     * @defaultValue false
-     */
-    open?: boolean;
-    /**
-     * A callback function called when the open state changes.
-     */
-    onOpenChange?: OnChangeFn<boolean>;
-}>;
-type TriggerProps = DOMElement<HTMLButtonElement>;
-type CloseProps = DOMElement<HTMLButtonElement>;
-export type { Props, CloseProps, ArrowProps, ContentProps, TriggerProps };

package/dist/bits/popover/_types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/progress/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as ProgressProps } from "./types.js";

package/dist/bits/progress/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/progress/_types.d.ts

@@ -1,19 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { DOMElement, Expand, OmitValue, OnChangeFn } from "../../internal/index.js";
-import type { CreateProgressProps } from "@melt-ui/svelte";
-type Props = Expand<OmitValue<CreateProgressProps> & {
-    /**
-     * The value of the progress bar.
-     * You can bind this to a number value to programmatically control the value.
-     */
-    value?: CreateProgressProps["defaultValue"];
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<number | null>;
-} & DOMElement>;
-export type { Props };

package/dist/bits/progress/_types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/radio-group/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as RadioGroupProps, InputProps as RadioGroupInputProps, ItemProps as RadioGroupItemProps, ItemIndicatorProps as RadioGroupItemIndicatorProps, ItemEvents as RadioGroupItemEvents, } from "./types.js";

package/dist/bits/radio-group/_export.types.js

@@ -1 +0,0 @@
-export {};

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

@@ -1,24 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { Expand, OmitValue, OnChangeFn, ObjectVariation, DOMElement } from "../../internal/index.js";
-import type { CreateRadioGroupProps, RadioGroupItemProps } from "@melt-ui/svelte";
-type Props = Expand<OmitValue<CreateRadioGroupProps> & {
-    /**
-     * The value of the radio group.
-     * You can bind this to a value to programmatically control the value.
-     *
-     * @defaultValue undefined
-     */
-    value?: CreateRadioGroupProps["defaultValue"] & {};
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<CreateRadioGroupProps["defaultValue"] & {}>;
-} & DOMElement>;
-type InputProps = DOMElement<HTMLInputElement>;
-type ItemProps = Expand<ObjectVariation<RadioGroupItemProps> & DOMElement<HTMLButtonElement>>;
-type ItemIndicatorProps = DOMElement;
-export type { Props, InputProps, ItemProps, ItemIndicatorProps };

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

@@ -1 +0,0 @@
-export {};

package/dist/bits/range-calendar/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as RangeCalendarProps, PrevButtonProps as RangeCalendarPrevButtonProps, NextButtonProps as RangeCalendarNextButtonProps, HeadingProps as RangeCalendarHeadingProps, HeaderProps as RangeCalendarHeaderProps, GridProps as RangeCalendarGridProps, GridHeadProps as RangeCalendarGridHeadProps, HeadCellProps as RangeCalendarHeadCellProps, GridBodyProps as RangeCalendarGridBodyProps, CellProps as RangeCalendarCellProps, GridRowProps as RangeCalendarGridRowProps, DayProps as RangeCalendarDayProps, Events as RangeCalendarEvents, PrevButtonEvents as RangeCalendarPrevButtonEvents, NextButtonEvents as RangeCalendarNextButtonEvents, DayEvents as RangeCalendarDayEvents, } from "./types.js";

package/dist/bits/range-calendar/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/range-calendar/_types.d.ts

@@ -1,83 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { DOMElement, OnChangeFn } from "../../internal/index.js";
-import type { DateRange } from "../../shared/index.js";
-import type { DateValue } from "@internationalized/date";
-import type { CreateRangeCalendarProps } from "@melt-ui/svelte";
-type Props = Expand<Omit<CreateRangeCalendarProps, "placeholder" | "defaultPlaceholder" | "value" | "defaultValue" | "onPlaceholderChange" | "onValueChange" | "ids"> & {
-    /**
-     * The selected date range. This updates as the user selects
-     * date ranges in the calendar.
-     *
-     * You can bind this to a value to programmatically control the
-     * value state.
-     */
-    value?: DateRange;
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<DateRange>;
-    /**
-     * The placeholder date, used to display the calendar when no
-     * date is selected. This updates as the user navigates
-     * the calendar.
-     *
-     * You can bind this to a value to programmatically control the
-     * placeholder state.
-     */
-    placeholder?: DateValue;
-    /**
-     * A callback function called when the placeholder changes.
-     */
-    onPlaceholderChange?: OnChangeFn<DateValue>;
-    /**
-     * If `true`, the calendar will focus the selected day,
-     * today, or the first day of the month in that order depending
-     * on what is visible when the calendar is mounted.
-     *
-     * @default false
-     */
-    initialFocus?: boolean;
-    /**
-     * The `start` value of the date range, which can exist prior
-     * to the `value` being set. The `value` is only set once a `start`
-     * and `end` value are selected.
-     *
-     * You can `bind:startValue` to a value to receive updates outside
-     * this component when the user selects a `start` value.
-     *
-     * Modifying this value outside the component will have no effect.
-     * To programmatically control the `start` value, use `bind:value`
-     * and update the `start` property of the `DateRange` object.
-     *
-     * This is provided as a convenience for use cases where you want
-     * to display the selected `start` value outside the component before
-     * the `value` is set.
-     */
-    startValue?: DateValue | undefined;
-} & DOMElement>;
-type PrevButtonProps = DOMElement<HTMLButtonElement>;
-type NextButtonProps = DOMElement<HTMLButtonElement>;
-type HeadingProps = DOMElement;
-type HeaderProps = DOMElement<HTMLElement>;
-type GridHeadProps = DOMElement<HTMLTableSectionElement>;
-type HeadCellProps = DOMElement<HTMLTableCellElement>;
-type GridProps = DOMElement<HTMLTableElement>;
-type GridBodyProps = DOMElement<HTMLTableSectionElement>;
-type GridRowProps = DOMElement<HTMLTableRowElement>;
-type BaseDayProps = Expand<{
-    /**
-     * The date value of the cell.
-     */
-    date: DateValue;
-    /**
-     * The month value that the cell belongs to.
-     */
-    month: DateValue;
-}>;
-type CellProps = Expand<Omit<BaseDayProps, "month"> & DOMElement<HTMLTableCellElement>>;
-type DayProps = Expand<BaseDayProps & DOMElement>;
-export type { Props, PrevButtonProps, NextButtonProps, HeadingProps, HeaderProps, GridProps, GridHeadProps, HeadCellProps, GridBodyProps, GridRowProps, CellProps, DayProps, };

package/dist/bits/range-calendar/_types.js

@@ -1,6 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-export {};

package/dist/bits/scroll-area/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as ScrollAreaProps, ViewportProps as ScrollAreaViewportProps, ContentProps as ScrollAreaContentProps, ScrollbarProps as ScrollAreaScrollbarProps, ThumbProps as ScrollAreaThumbProps, CornerProps as ScrollAreaCornerProps, } from "./types.js";

package/dist/bits/scroll-area/_export.types.js

@@ -1 +0,0 @@
-export {};

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

@@ -1,12 +0,0 @@
-import type { Expand, DOMElement } from "../../internal/types.js";
-import type { CreateScrollAreaProps } from "@melt-ui/svelte";
-type Props = Expand<Omit<CreateScrollAreaProps, "ids">> & DOMElement<HTMLDivElement>;
-type BaseDivProps = DOMElement<HTMLDivElement>;
-type ScrollbarProps = BaseDivProps & {
-    orientation: "horizontal" | "vertical";
-};
-type ThumbProps = BaseDivProps;
-type ViewportProps = BaseDivProps;
-type ContentProps = BaseDivProps;
-type CornerProps = BaseDivProps;
-export type { Props, ViewportProps, ContentProps, ScrollbarProps, ThumbProps, CornerProps };

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

@@ -1 +0,0 @@
-export {};

package/dist/bits/select/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as SelectProps, ArrowProps as SelectArrowProps, ContentProps as SelectContentProps, GroupProps as SelectGroupProps, InputProps as SelectInputProps, LabelProps as SelectLabelProps, ItemProps as SelectItemProps, IndicatorProps as SelectIndicatorProps, SeparatorProps as SelectSeparatorProps, TriggerProps as SelectTriggerProps, ValueProps as SelectValueProps, ItemEvents as SelectItemEvents, ContentEvents as SelectContentEvents, TriggerEvents as SelectTriggerEvents, LabelEvents as SelectLabelEvents, } from "./types.js";

package/dist/bits/select/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/select/_types.d.ts

@@ -1,62 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { CreateSelectProps, SelectOptionProps } from "@melt-ui/svelte";
-import type { DOMElement, Expand, OmitFloating, OnChangeFn } from "../../internal/index.js";
-import type { ContentProps, ArrowProps } from "../floating/_types.js";
-import type { Selected } from "../../index.js";
-export type WhenTrue<TrueOrFalse, IfTrue, IfFalse, IfNeither = IfTrue | IfFalse> = [
-    TrueOrFalse
-] extends [true] ? IfTrue : [TrueOrFalse] extends [false] ? IfFalse : IfNeither;
-type SelectValue<T, Multiple extends boolean> = WhenTrue<Multiple, T[] | undefined, T | undefined>;
-type Props<T = unknown, Multiple extends boolean = false> = Expand<OmitFloating<Omit<CreateSelectProps, "selected" | "defaultSelected" | "onSelectedChange" | "multiple">> & {
-    /**
-     * The selected value of the select.
-     * You can bind this to a value to programmatically control the selected value.
-     *
-     * @defaultValue undefined
-     */
-    selected?: SelectValue<Selected<T>, Multiple> | undefined;
-    /**
-     * A callback function called when the selected value changes.
-     */
-    onSelectedChange?: OnChangeFn<SelectValue<Selected<T>, Multiple>>;
-    /**
-     * The open state of the select menu.
-     * You can bind this to a boolean value to programmatically control the open state.
-     *
-     * @defaultValue false
-     */
-    open?: boolean;
-    /**
-     * A callback function called when the open state changes.
-     */
-    onOpenChange?: OnChangeFn<boolean>;
-    /**
-     * Whether or not multiple values can be selected.
-     */
-    multiple?: Multiple;
-    /**
-     * Optionally provide an array of `Selected<T>` objects to
-     * type the `selected` and `onSelectedChange` props.
-     */
-    items?: Selected<T>[];
-}>;
-type GroupProps = DOMElement;
-type InputProps = DOMElement<HTMLInputElement>;
-type LabelProps = DOMElement;
-type ItemProps = Expand<SelectOptionProps & DOMElement>;
-type SeparatorProps = DOMElement;
-type IndicatorProps = DOMElement;
-type TriggerProps = DOMElement<HTMLButtonElement>;
-type ValueProps = Expand<{
-    /**
-     * The placeholder text to display when there is no value.
-     *
-     * @defaultValue ""
-     */
-    placeholder?: string;
-} & DOMElement<HTMLSpanElement>>;
-export type { Props, ArrowProps, ContentProps, IndicatorProps, GroupProps, InputProps, LabelProps, ItemProps, SeparatorProps, TriggerProps, ValueProps, };

package/dist/bits/select/_types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/separator/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as SeparatorProps } from "./types.js";

package/dist/bits/separator/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/separator/_types.d.ts

@@ -1,9 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { DOMElement, Expand } from "../../internal/index.js";
-import type { CreateSeparatorProps } from "@melt-ui/svelte";
-type Props = Expand<CreateSeparatorProps & DOMElement>;
-export type { Props };

package/dist/bits/separator/_types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/slider/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as SliderProps, RangeProps as SliderRangeProps, ThumbProps as SliderThumbProps, InputProps as SliderInputProps, TickProps as SliderTickProps, ThumbEvents as SliderThumbEvents, } from "./types.js";

package/dist/bits/slider/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/slider/_types.d.ts

@@ -1,38 +0,0 @@
-/// <reference types="svelte" />
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { CreateSliderProps, Slider } from "@melt-ui/svelte";
-import type { Expand, OmitValue, OnChangeFn, DOMElement } from "../../internal/index.js";
-import type { StoresValues } from "svelte/store";
-type Props = Expand<OmitValue<CreateSliderProps> & {
-    /**
-     * The value of the slider.
-     * You can bind this to a number value to programmatically control the value.
-     */
-    value?: number[];
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<number[]>;
-} & DOMElement<HTMLSpanElement>>;
-type RangeProps = DOMElement<HTMLSpanElement>;
-type ThumbProps = DOMElement<HTMLSpanElement> & {
-    /**
-     * An individual thumb builder from the `thumbs` slot prop
-     * provided by the `Slider.Root` component.
-     */
-    thumb: Thumb;
-};
-type TickProps = DOMElement<HTMLSpanElement> & {
-    /**
-     * An individual tick builder from the `ticks` slot prop
-     * provided by the `Slider.Root` component.
-     */
-    tick: Tick;
-};
-export type { Props, RangeProps, ThumbProps, TickProps };
-type Tick = StoresValues<Slider["elements"]["ticks"]>[number];
-type Thumb = StoresValues<Slider["elements"]["thumbs"]>[number];

package/dist/bits/slider/_types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/switch/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as SwitchProps, ThumbProps as SwitchThumbProps, InputProps as SwitchInputProps, Events as SwitchEvents, } from "./types.js";

package/dist/bits/switch/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/switch/_types.d.ts

@@ -1,33 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { CreateSwitchProps } from "@melt-ui/svelte";
-import type { DOMElement, Expand, OmitChecked, OnChangeFn } from "../../internal/index.js";
-import type { HTMLInputAttributes } from "svelte/elements";
-type Props = Expand<OmitChecked<CreateSwitchProps> & {
-    /**
-     * The checked state of the switch.
-     * You can bind this to a boolean value to programmatically control the checked state.
-     *
-     * @defaultValue false
-     */
-    checked?: boolean;
-    /**
-     * A callback function called when the checked state changes.
-     */
-    onCheckedChange?: OnChangeFn<boolean>;
-    /**
-     * Whether to include the hidden input element in the DOM.
-     */
-    includeInput?: boolean;
-    /**
-     * Additional input attributes to pass to the hidden input element.
-     * Note, the value, name, type, and checked attributes are derived from the
-     * Switch props and cannot be overridden.
-     */
-    inputAttrs?: Partial<Omit<HTMLInputAttributes, "value" | "name" | "type" | "checked">>;
-} & DOMElement<HTMLButtonElement>>;
-type ThumbProps = DOMElement<HTMLSpanElement>;
-export type { Props, ThumbProps };

package/dist/bits/switch/_types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/tabs/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as TabsProps, ContentProps as TabsContentProps, TriggerProps as TabsTriggerProps, ListProps as TabsListProps, TriggerEvents as TabsTriggerEvents, } from "./types.js";

package/dist/bits/tabs/_export.types.js

@@ -1 +0,0 @@
-export {};

package/dist/bits/tabs/_types.d.ts

@@ -1,30 +0,0 @@
-/**
- * We define prop types without the HTMLAttributes here so that we can use them
- * to type-check our API documentation, which requires we document each prop,
- * but we don't want to document the HTML attributes.
- */
-import type { CreateTabsProps, TabsTriggerProps } from "@melt-ui/svelte";
-import type { DOMElement, Expand, ObjectVariation, OmitValue, OnChangeFn } from "../../internal/index.js";
-type Props = Expand<OmitValue<CreateTabsProps> & {
-    /**
-     * The value of the currently active tab.
-     * You can bind this to a string value to programmatically control the active tab.
-     */
-    value?: CreateTabsProps["defaultValue"] & {};
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<CreateTabsProps["defaultValue"]>;
-    /**
-     * The orientation of the tabs, which determines how keyboard navigation works.
-     *
-     * @defaultValue "horizontal"
-     */
-    orientation?: CreateTabsProps["orientation"] & {};
-} & DOMElement>;
-type ContentProps = Expand<{
-    value: string;
-} & DOMElement>;
-type TriggerProps = Expand<ObjectVariation<TabsTriggerProps> & DOMElement<HTMLButtonElement>>;
-type ListProps = DOMElement;
-export type { Props, ContentProps, TriggerProps, ListProps };