bits-ui 0.21.1 → 0.21.3

package/dist/bits/checkbox/_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 { Expand, OmitChecked, OnChangeFn, DOMElement } from "../../internal/index.js";
-import type { CreateCheckboxProps } from "@melt-ui/svelte";
-type Props = Expand<OmitChecked<CreateCheckboxProps> & {
-    /**
-     * The state of the checkbox.
-     * 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<HTMLButtonElement>>;
-type IndicatorProps = DOMElement;
-export type { Props, IndicatorProps, Props as CheckboxProps, IndicatorProps as CheckboxIndicatorProps, };

package/dist/bits/checkbox/_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/collapsible/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as CollapsibleProps, ContentProps as CollapsibleContentProps, TriggerProps as CollapsibleTriggerProps, TriggerEvents as CollapsibleTriggerEvents, } from "./types.js";

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

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

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

@@ -1,23 +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 { Transition, OmitOpen, OmitForceVisible, Expand, OnChangeFn, TransitionProps, DOMElement } from "../../internal/index.js";
-import type { CreateCollapsibleProps } from "@melt-ui/svelte";
-type Props = Expand<OmitOpen<OmitForceVisible<CreateCollapsibleProps>> & {
-    /**
-     * The open state of the collapsible.
-     * 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>;
-} & DOMElement>;
-type ContentProps<T extends Transition = Transition, In extends Transition = Transition, Out extends Transition = Transition> = Expand<TransitionProps<T, In, Out> & DOMElement>;
-type TriggerProps = DOMElement<HTMLButtonElement>;
-export type { Props, ContentProps, TriggerProps };

package/dist/bits/collapsible/_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/combobox/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as ComboboxProps, ContentProps as ComboboxContentProps, InputProps as ComboboxInputProps, ItemProps as ComboboxItemProps, LabelProps as ComboboxLabelProps, GroupProps as ComboboxGroupProps, GroupLabelProps as ComboboxGroupLabelProps, ArrowProps as ComboboxArrowProps, HiddenInputProps as ComboboxHiddenInputProps, SeparatorProps as ComboboxSeparatorProps, IndicatorProps as ComboboxIndicatorProps, ItemEvents as ComboboxItemEvents, InputEvents as ComboboxInputEvents, GroupLabelEvents as ComboboxGroupLabelEvents, ContentEvents as ComboboxContentEvents, } from "./types.js";

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

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

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

@@ -1,69 +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 { CreateComboboxProps, ComboboxOptionProps } 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<CreateComboboxProps, "selected" | "defaultSelected" | "onSelectedChange" | "multiple">> & {
-    /**
-     * The selected value of the combobox.
-     * 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 combobox 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;
-    /**
-     * The value of the input.
-     * You can bind this to a value to programmatically control the input value.
-     *
-     * @defaultValue ""
-     */
-    inputValue?: string;
-    /**
-     * Optionally provide an array of `Selected<T>` objects to
-     * type the `selected` and `onSelectedChange` props.
-     */
-    items?: Selected<T>[];
-    /**
-     * Whether the input has been touched or not. You can bind to this to
-     * handle filtering the items only when the input has been touched.
-     *
-     * @defaultValue false
-     */
-    touchedInput?: boolean;
-}>;
-type InputProps = DOMElement<HTMLInputElement>;
-type LabelProps = DOMElement<HTMLLabelElement>;
-type GroupProps = DOMElement;
-type GroupLabelProps = DOMElement;
-type ItemProps = Expand<ComboboxOptionProps & DOMElement>;
-type HiddenInputProps = DOMElement;
-type SeparatorProps = DOMElement;
-type IndicatorProps = DOMElement;
-export type { Props, ContentProps, InputProps, ItemProps, LabelProps, GroupProps, GroupLabelProps, ArrowProps, HiddenInputProps, SeparatorProps, IndicatorProps, };

package/dist/bits/combobox/_types.js

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

package/dist/bits/context-menu/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as ContextMenuProps, SubProps as ContextMenuSubProps, ItemProps as ContextMenuItemProps, ArrowProps as ContextMenuArrowProps, GroupProps as ContextMenuGroupProps, LabelProps as ContextMenuLabelProps, ContentProps as ContextMenuContentProps, TriggerProps as ContextMenuTriggerProps, RadioItemProps as ContextMenuRadioItemProps, SeparatorProps as ContextMenuSeparatorProps, RadioGroupProps as ContextMenuRadioGroupProps, SubContentProps as ContextMenuSubContentProps, SubTriggerProps as ContextMenuSubTriggerProps, CheckboxItemProps as ContextMenuCheckboxItemProps, RadioIndicatorProps as ContextMenuRadioIndicatorProps, CheckboxIndicatorProps as ContextMenuCheckboxIndicatorProps, ItemEvents as ContextMenuItemEvents, TriggerEvents as ContextMenuTriggerEvents, ContentEvents as ContextMenuContentEvents, RadioItemEvents as ContextMenuRadioItemEvents, SubContentEvents as ContextMenuSubContentEvents, SubTriggerEvents as ContextMenuSubTriggerEvents, CheckboxItemEvents as ContextMenuCheckboxItemEvents, } from "./types.js";

package/dist/bits/context-menu/_export.types.js

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

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

@@ -1,5 +0,0 @@
-import type { DOMElement, Transition, TransitionProps } from "../../internal/index.js";
-import type { FloatingProps } from "../floating/_types.js";
-type ContextFloatingProps = Omit<FloatingProps, "sameWidth" | "side" | "sideOffset" | "align">;
-export type ContentProps<T extends Transition = Transition, In extends Transition = Transition, Out extends Transition = Transition> = Expand<ContextFloatingProps & TransitionProps<T, In, Out> & DOMElement>;
-export {};

package/dist/bits/context-menu/_types.js

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

package/dist/bits/date-field/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as DateFieldProps, LabelProps as DateFieldLabelProps, DescriptionProps as DateFieldDescriptionProps, InputProps as DateFieldInputProps, SegmentProps as DateFieldSegmentProps, SegmentEvents as DateFieldSegmentEvents, } from "./types.js";

package/dist/bits/date-field/_export.types.js

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

package/dist/bits/date-field/_types.d.ts

@@ -1,45 +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, OmitDates, DOMElement } from "../../internal/index.js";
-import type { SegmentPart } from "../../shared/index.js";
-import type { DateValue } from "@internationalized/date";
-import type { CreateDateFieldProps } from "@melt-ui/svelte";
-type Props = Expand<Omit<OmitDates<CreateDateFieldProps>, "required" | "name"> & {
-    /**
-     * The value of the date field.
-     * You can bind this to a `DateValue` object to programmatically control the value.
-     */
-    value?: DateValue;
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<DateValue | undefined>;
-    /**
-     * The placeholder date used to start the field.
-     */
-    placeholder?: DateValue;
-    /**
-     * A callback function called when the placeholder changes.
-     */
-    onPlaceholderChange?: OnChangeFn<DateValue>;
-    /**
-     * The id of the validation message element which is used to apply the
-     * appropriate `aria-describedby` attribute to the input.
-     */
-    validationId?: string;
-    /**
-     * The id of the description element which is used to describe the input.
-     * This is used to apply the appropriate `aria-describedby` attribute to the input.
-     */
-    descriptionId?: string;
-}>;
-type InputProps = DOMElement;
-type DescriptionProps = DOMElement;
-type LabelProps = DOMElement<HTMLSpanElement>;
-type SegmentProps = Expand<{
-    part: SegmentPart;
-} & DOMElement>;
-export type { Props, LabelProps, DescriptionProps, InputProps, SegmentProps };

package/dist/bits/date-field/_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/date-picker/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as DatePickerProps, CalendarProps as DatePickerCalendarProps, LabelProps as DatePickerLabelProps, DescriptionProps as DatePickerDescriptionProps, InputProps as DatePickerInputProps, SegmentProps as DatePickerSegmentProps, CellProps as DatePickerCellProps, DayProps as DatePickerDayProps, GridBodyProps as DatePickerGridBodyProps, GridHeadProps as DatePickerGridHeadProps, GridRowProps as DatePickerGridRowProps, GridProps as DatePickerGridProps, HeadCellProps as DatePickerHeadCellProps, HeaderProps as DatePickerHeaderProps, HeadingProps as DatePickerHeadingProps, NextButtonProps as DatePickerNextButtonProps, PrevButtonProps as DatePickerPrevButtonProps, TriggerProps as DatePickerTriggerProps, ContentProps as DatePickerContentProps, ArrowProps as DatePickerArrowProps, CloseProps as DatePickerCloseProps, CloseEvents as DatePickerCloseEvents, TriggerEvents as DatePickerTriggerEvents, CalendarEvents as DatePickerCalendarEvents, DayEvents as DatePickerDayEvents, PrevButtonEvents as DatePickerPrevButtonEvents, NextButtonEvents as DatePickerNextButtonEvents, SegmentEvents as DatePickerSegmentEvents, } from "./types.js";

package/dist/bits/date-picker/_export.types.js

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

package/dist/bits/date-picker/_types.d.ts

@@ -1,57 +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, OmitDates, OmitFloating, DOMElement } from "../../internal/index.js";
-import type { SegmentPart } from "../../shared/index.js";
-import type { DateValue } from "@internationalized/date";
-import type { CreateDatePickerProps } from "@melt-ui/svelte";
-type Props = Expand<Omit<OmitFloating<OmitDates<CreateDatePickerProps>>, "required" | "name" | "calendarIds" | "dateFieldIds" | "popoverIds"> & {
-    /**
-     * The open state of the popover.
-     * You can bind this to a boolean value to programmatically control the open state.
-     *
-     * @default false
-     */
-    open?: boolean;
-    /**
-     * A callback function called when the open state changes.
-     */
-    onOpenChange?: OnChangeFn<boolean>;
-    /**
-     * The value of the date field.
-     * You can bind this to a `DateValue` object to programmatically control the value.
-     */
-    value?: DateValue;
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<DateValue | undefined>;
-    /**
-     * The placeholder date used to start the field.
-     */
-    placeholder?: DateValue;
-    /**
-     * A callback function called when the placeholder changes.
-     */
-    onPlaceholderChange?: OnChangeFn<DateValue>;
-    /**
-     * The id of the validation message element which is used to apply the
-     * appropriate `aria-describedby` attribute to the input.
-     */
-    validationId?: string;
-    /**
-     * The id of the description element which is used to describe the input.
-     * This is used to apply the appropriate `aria-describedby` attribute to the input.
-     */
-    descriptionId?: string;
-}>;
-type InputProps = DOMElement;
-type DescriptionProps = DOMElement;
-type LabelProps = DOMElement<HTMLSpanElement>;
-type CalendarProps = DOMElement;
-type SegmentProps = Expand<{
-    part: SegmentPart;
-} & DOMElement>;
-export type { Props, CalendarProps, LabelProps, DescriptionProps, InputProps, SegmentProps };

package/dist/bits/date-picker/_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/date-range-field/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as DateRangeFieldProps, LabelProps as DateRangeFieldLabelProps, InputProps as DateRangeFieldInputProps, SegmentProps as DateRangeFieldSegmentProps, SegmentEvents as DateRangeFieldSegmentEvents, } from "./types.js";

package/dist/bits/date-range-field/_export.types.js

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

package/dist/bits/date-range-field/_types.d.ts

@@ -1,52 +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, OmitDates, DOMElement } from "../../internal/index.js";
-import type { DateRange, SegmentPart } from "../../shared/index.js";
-import type { DateValue } from "@internationalized/date";
-import type { CreateDateRangeFieldProps as ICreateDateRangeFieldProps } from "@melt-ui/svelte";
-type CreateDateRangeFieldProps = Omit<OmitDates<ICreateDateRangeFieldProps>, "required" | "name" | "startIds" | "endIds" | "startName" | "endName">;
-type Props = Expand<Omit<OmitDates<CreateDateRangeFieldProps>, "required" | "name" | "startIds" | "endIds" | "startName" | "endName"> & {
-    /**
-     * The value of the date field.
-     * You can bind this to a `DateValue` object to programmatically control the value.
-     */
-    value?: DateRange;
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<DateRange | undefined>;
-    /**
-     * The placeholder date used to start the field.
-     */
-    placeholder?: DateValue;
-    /**
-     * A callback function called when the placeholder changes.
-     */
-    onPlaceholderChange?: OnChangeFn<DateValue>;
-    /**
-     * The id of the validation message element which is used to apply the
-     * appropriate `aria-describedby` attribute to the input.
-     */
-    validationId?: string;
-    /**
-     * The id of the description element which is used to describe the input.
-     * This is used to apply the appropriate `aria-describedby` attribute to the input.
-     */
-    descriptionId?: string;
-}>;
-type InputProps = DOMElement;
-type LabelProps = DOMElement<HTMLSpanElement>;
-type SegmentProps = Expand<{
-    /**
-     * The type of field to render (start or end).
-     */
-    type: "start" | "end";
-    /**
-     * The part of the date to render.
-     */
-    part: SegmentPart;
-} & DOMElement>;
-export type { Props, LabelProps, InputProps, SegmentProps };

package/dist/bits/date-range-field/_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/date-range-picker/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as DateRangePickerProps, CalendarProps as DateRangePickerCalendarProps, LabelProps as DateRangePickerLabelProps, DescriptionProps as DateRangePickerDescriptionProps, InputProps as DateRangePickerInputProps, SegmentProps as DateRangePickerSegmentProps, CellProps as DateRangePickerCellProps, DayProps as DateRangePickerDayProps, GridBodyProps as DateRangePickerGridBodyProps, GridHeadProps as DateRangePickerGridHeadProps, GridRowProps as DateRangePickerGridRowProps, GridProps as DateRangePickerGridProps, HeadCellProps as DateRangePickerHeadCellProps, HeaderProps as DateRangePickerHeaderProps, HeadingProps as DateRangePickerHeadingProps, NextButtonProps as DateRangePickerNextButtonProps, PrevButtonProps as DateRangePickerPrevButtonProps, TriggerProps as DateRangePickerTriggerProps, ContentProps as DateRangePickerContentProps, ArrowProps as DateRangePickerArrowProps, CloseProps as DateRangePickerCloseProps, CloseEvents as DateRangePickerCloseEvents, TriggerEvents as DateRangePickerTriggerEvents, CalendarEvents as DateRangePickerCalendarEvents, DayEvents as DateRangePickerDayEvents, PrevButtonEvents as DateRangePickerPrevButtonEvents, NextButtonEvents as DateRangePickerNextButtonEvents, SegmentEvents as DateRangePickerSegmentEvents, } from "./types.js";

package/dist/bits/date-range-picker/_export.types.js

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

package/dist/bits/date-range-picker/_types.d.ts

@@ -1,84 +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, OmitDates, OmitFloating, DOMElement } from "../../internal/index.js";
-import type { DateRange, SegmentPart } from "../../shared/index.js";
-import type { DateValue } from "@internationalized/date";
-import type { CreateDateRangePickerProps } from "@melt-ui/svelte";
-type OmitStartEnd<T> = Omit<T, "startName" | "endName" | "startIds" | "endIds" | "dateFieldIds" | "popoverIds" | "calendarIds">;
-type OmitForm<T> = Omit<T, "required" | "name">;
-type WithOmission<T> = OmitForm<OmitDates<OmitStartEnd<OmitFloating<T>>>>;
-type Props = Expand<WithOmission<CreateDateRangePickerProps> & {
-    /**
-     * The open state of the popover.
-     * You can bind this to a boolean value to programmatically control the open state.
-     *
-     * @default false
-     */
-    open?: boolean;
-    /**
-     * A callback function called when the open state changes.
-     */
-    onOpenChange?: OnChangeFn<boolean>;
-    /**
-     * The value of the date field.
-     * You can bind this to a `DateValue` object to programmatically control the value.
-     */
-    value?: DateRange;
-    /**
-     * A callback function called when the value changes.
-     */
-    onValueChange?: OnChangeFn<DateRange | undefined>;
-    /**
-     * The placeholder date used to start the field.
-     */
-    placeholder?: DateValue;
-    /**
-     * A callback function called when the placeholder changes.
-     */
-    onPlaceholderChange?: OnChangeFn<DateValue>;
-    /**
-     * The id of the validation message element which is used to apply the
-     * appropriate `aria-describedby` attribute to the input.
-     */
-    validationId?: string;
-    /**
-     * The id of the description element which is used to describe the input.
-     * This is used to apply the appropriate `aria-describedby` attribute to the input.
-     */
-    descriptionId?: string;
-    /**
-     * 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;
-}>;
-type InputProps = DOMElement;
-type DescriptionProps = DOMElement;
-type LabelProps = DOMElement<HTMLSpanElement>;
-type CalendarProps = DOMElement;
-type SegmentProps = Expand<{
-    /**
-     * The type of field to render (start or end).
-     */
-    type: "start" | "end";
-    /**
-     * The part of the date to render.
-     */
-    part: SegmentPart;
-} & DOMElement>;
-export type { Props, CalendarProps, LabelProps, DescriptionProps, InputProps, SegmentProps };

package/dist/bits/date-range-picker/_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/dialog/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as DialogProps, CloseProps as DialogCloseProps, TitleProps as DialogTitleProps, PortalProps as DialogPortalProps, ContentProps as DialogContentProps, TriggerProps as DialogTriggerProps, OverlayProps as DialogOverlayProps, DescriptionProps as DialogDescriptionProps, TriggerEvents as DialogTriggerEvents, CloseEvents as DialogCloseEvents, ContentEvents as DialogContentEvents, } from "./types.js";

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

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

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

@@ -1,39 +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 { FocusProp } from "../../shared/index.js";
-import type { DOMElement, Expand, OmitOpen, OnChangeFn, Transition, TransitionProps } from "../../internal/index.js";
-import type { CreateDialogProps } from "@melt-ui/svelte";
-type Props = Expand<OmitOpen<Omit<CreateDialogProps, "role" | "ids" | "forceVisible" | "openFocus" | "closeFocus">> & {
-    /**
-     * The open state of the dialog.
-     * You can bind this to a boolean value to programmatically control the open state.
-     *
-     * @defaultValue false
-     */
-    open?: CreateDialogProps["defaultOpen"] & {};
-    /**
-     * A callback function called when the open state changes.
-     */
-    onOpenChange?: OnChangeFn<boolean>;
-    /**
-     * Override the default autofocus behavior of the dialog when it opens
-     */
-    openFocus?: FocusProp;
-    /**
-     * Override the default autofocus behavior of the dialog after close
-     */
-    closeFocus?: FocusProp;
-}>;
-type TriggerProps = DOMElement<HTMLButtonElement>;
-type CloseProps = TriggerProps;
-type ContentProps<T extends Transition = Transition, In extends Transition = Transition, Out extends Transition = Transition> = Expand<TransitionProps<T, In, Out> & DOMElement>;
-type DescriptionProps = DOMElement;
-type OverlayProps<T extends Transition = Transition, In extends Transition = Transition, Out extends Transition = Transition> = Expand<TransitionProps<T, In, Out> & DOMElement>;
-type PortalProps = DOMElement;
-type TitleProps = Expand<{
-    level?: "h1" | "h2" | "h3" | "h4" | "h5" | "h6";
-} & DOMElement<HTMLHeadingElement>>;
-export type { Props, CloseProps, TitleProps, PortalProps, ContentProps, TriggerProps, OverlayProps, DescriptionProps, };

package/dist/bits/dialog/_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/dropdown-menu/_export.types.d.ts

@@ -1 +0,0 @@
-export type { Props as DropdownMenuProps, SubProps as DropdownMenuSubProps, ItemProps as DropdownMenuItemProps, ArrowProps as DropdownMenuArrowProps, GroupProps as DropdownMenuGroupProps, LabelProps as DropdownMenuLabelProps, ContentProps as DropdownMenuContentProps, TriggerProps as DropdownMenuTriggerProps, RadioItemProps as DropdownMenuRadioItemProps, SeparatorProps as DropdownMenuSeparatorProps, RadioGroupProps as DropdownMenuRadioGroupProps, SubContentProps as DropdownMenuSubContentProps, SubTriggerProps as DropdownMenuSubTriggerProps, CheckboxItemProps as DropdownMenuCheckboxItemProps, RadioIndicatorProps as DropdownMenuRadioIndicatorProps, CheckboxIndicatorProps as DropdownMenuCheckboxIndicatorProps, ItemEvents as DropdownMenuItemEvents, TriggerEvents as DropdownMenuTriggerEvents, ContentEvents as DropdownMenuContentEvents, RadioItemEvents as DropdownMenuRadioItemEvents, SubContentEvents as DropdownMenuSubContentEvents, SubTriggerEvents as DropdownMenuSubTriggerEvents, CheckboxItemEvents as DropdownMenuCheckboxItemEvents, } from "./types.js";

package/dist/bits/dropdown-menu/_export.types.js

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

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

@@ -1,2 +0,0 @@
-import type { Props, Events } from "./types.js";
-export type { Props as LabelProps, Events as LabelEvents, };

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

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

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

@@ -1,3 +0,0 @@
-import type { DOMElement } from "../../internal/types.js";
-type Props = DOMElement<HTMLLabelElement>;
-export type { Props };

package/dist/bits/label/_types.js

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

package/dist/bits/link-preview/_export.types.d.ts

@@ -1,2 +0,0 @@
-import type { Props, ArrowProps, TriggerProps, ContentProps, TriggerEvents, ContentEvents } from "./types.js";
-export type { Props as LinkPreviewProps, ArrowProps as LinkPreviewArrowProps, TriggerProps as LinkPreviewTriggerProps, ContentProps as LinkPreviewContentProps, TriggerEvents as LinkPreviewTriggerEvents, ContentEvents as LinkPreviewContentEvents, };

package/dist/bits/link-preview/_export.types.js

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

package/dist/bits/link-preview/_types.d.ts

@@ -1,23 +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 { CreateLinkPreviewProps } from "@melt-ui/svelte";
-type Props = Expand<OmitFloating<CreateLinkPreviewProps> & {
-    /**
-     * The open state of the link preview.
-     * 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<HTMLAnchorElement>;
-export type { Props, ArrowProps, ContentProps, TriggerProps };

package/dist/bits/link-preview/_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 {};