@ecoma-io/loom 0.2.0 → 0.4.0

package/dist/packages/primitives/date-picker/src/DatePicker.js

@@ -0,0 +1,7 @@
+import DatePicker_vue_vue_type_script_setup_true_lang_default from "./DatePicker.vue_vue_type_script_setup_true_lang.js";
+//#region packages/primitives/date-picker/src/DatePicker.vue
+var DatePicker_default = DatePicker_vue_vue_type_script_setup_true_lang_default;
+//#endregion
+export { DatePicker_default as default };
+
+//# sourceMappingURL=DatePicker.js.map

package/dist/packages/primitives/date-picker/src/DatePicker.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"DatePicker.js","names":[],"sources":["../../../../../packages/primitives/date-picker/src/DatePicker.vue"],"sourcesContent":["<script lang=\"ts\">\nimport type { CalendarPanelLabels, DateSegmentLabels } from \"@ecoma-io/loom-labels\";\n\n/**\n * Everything this control publishes to assistive technology, which is two\n * shared slices and nothing of its own: the names of the field's segments and\n * the calendar popover's chrome. Both are declared in `src/lib/date-labels.ts`,\n * because `DateTimePicker`, `DateRangePicker` and `DateTimeRangePicker` say the\n * same words for the same reason — they are all one Reka implementation\n * underneath — and four copies of `Previous month` is a translator writing the\n * same word four times.\n *\n * An intersection rather than a third interface, so this name is the type a\n * consumer annotates their own bag with and the two halves stay one definition\n * each. Annotate with `LabelOverrides<DatePickerLabels>` and never with this\n * directly: this one is total, and a key added in a later release would stop a\n * consumer's build.\n */\nexport type DatePickerLabels = DateSegmentLabels & CalendarPanelLabels;\n</script>\n\n<script setup lang=\"ts\">\nimport { computed, ref, useId, useTemplateRef } from \"vue\";\nimport {\n  DatePickerRoot,\n  DatePickerAnchor,\n  DatePickerField,\n  DatePickerInput,\n  DatePickerTrigger,\n  DatePickerContent,\n  DatePickerCalendar,\n  DatePickerHeader,\n  DatePickerPrev,\n  DatePickerHeading,\n  DatePickerNext,\n  DatePickerGrid,\n  DatePickerGridHead,\n  DatePickerGridRow,\n  DatePickerHeadCell,\n  DatePickerGridBody,\n  DatePickerCell,\n  DatePickerCellTrigger,\n} from \"reka-ui\";\nimport { CalendarDays, ChevronLeft, ChevronRight } from \"@lucide/vue\";\nimport {\n  getLocalTimeZone,\n  isToday,\n  parseDate,\n  toCalendarDate,\n  type DateValue,\n} from \"@internationalized/date\";\nimport { cn } from \"@ecoma-io/loom-core\";\nimport { useSplitAttrs } from \"@ecoma-io/loom-core\";\nimport { useAncestorDisabled } from \"@ecoma-io/loom-labels\";\nimport { useFieldControl } from \"@ecoma-io/loom-labels\";\nimport { optional } from \"@ecoma-io/loom-core\";\nimport { useLabels, type LabelOverrides } from \"@ecoma-io/loom-labels\";\nimport {\n  CALENDAR_PANEL_LABELS,\n  DATE_SEGMENT_LABELS,\n  emptySegmentValueText,\n  isDateSegmentPart,\n} from \"@ecoma-io/loom-labels\";\n\n/**\n * DatePicker — one calendar date, entered either by typing it into a segmented\n * field or by picking it out of a calendar popover. Reach for it wherever a\n * date is a value rather than a search: a due date, a start date, a date of\n * birth.\n *\n * The segmented field is the reason this is not an `<input type=\"date\">`.\n * Arrow keys change the segment under the cursor, typing digits fills it and\n * advances, and the segment order and the month names follow `locale` rather\n * than the browser's own — which is what lets a Vietnamese reader and an\n * American reader see the same date written the way each of them writes it.\n * The calendar is the second path to the same value, not the only one.\n *\n * **The model value is a plain ISO date string, `\"YYYY-MM-DD\"`, never a\n * `DateValue`.** Reka and `@internationalized/date` model a date as a calendar\n * object, and that object is the right shape *inside* a date control — it\n * knows about calendars other than the Gregorian one, about month lengths, and\n * about what \"next month\" means on the 31st. It is the wrong shape at the\n * boundary: a host binding a due date has a string from its API and wants a\n * string back for it, and nobody should have to learn a date library to bind a\n * date. So the string is parsed on the way in and re-serialised on the way\n * out, the same instinct as Slider exposing a scalar where Reka models an\n * array. `min`, `max` and the emitted value all speak that one format.\n *\n * A value that does not parse — a half-typed string, an empty one, a\n * datetime — is read as *no date chosen* rather than thrown on. A component\n * library cannot decide that a host's bad data is fatal, and a date field that\n * crashes the page while someone types into the host's own text input beside\n * it is the worst possible reading of \"strict\".\n *\n * For a span rather than a single day, compose two of these — a range control\n * shares almost none of this one's model. For a month or a year alone, neither\n * this nor a Select is right; that is a control this library does not have yet.\n *\n * Inside a [Field](../Field/Field.vue) it wires itself: the row's id, the id of\n * its hint or error line, and `required` / `invalid` / `disabled` / `readonly` /\n * `name` all arrive through `useFieldControl()`, so `<Field label=\"Due date\"\n * error=\"…\"><DatePicker /></Field>` needs no attributes at the call site. Every\n * prop below still wins over the row when it is set, in both directions — which\n * is why the four booleans default to `undefined` rather than `false`.\n *\n * `readonly` and `disabled` are different states, not two dials on one, so the\n * field has three resting appearances rather than two. A read-only date is a\n * value on show: the field stays a Tab stop, its segments stay readable and\n * copyable at full strength, and it takes a lifted fill. A disabled one is\n * unavailable: no Tab stop, nothing submitted, and drained a step further in\n * fill, text colour and border weight together.\n */\nconst props = withDefaults(\n  defineProps<{\n    /**\n     * The chosen date as ISO `YYYY-MM-DD`. Unset, empty or unparseable means no\n     * date is chosen. The explicit `| undefined` is what lets `v-model` bind a\n     * ref that clears — the emitted value drops to `undefined` when the field\n     * is emptied, and a plain optional prop refuses to take it back.\n     */\n    modelValue?: string | undefined;\n    /** The earliest choosable date, same ISO format. Days before it are announced disabled and skipped by the keyboard. */\n    min?: string;\n    /** The latest choosable date, same ISO format. Days after it are announced disabled and skipped by the keyboard. */\n    max?: string;\n    /** BCP 47 tag driving the order of the field's segments, the month and weekday names, and which day a week starts on. */\n    locale?: string;\n    /** Unavailable: dims the control, refuses the calendar, and takes the field out of the tab order. Unset defers to a wrapping Field. */\n    disabled?: boolean | undefined;\n    /** Shows the date without allowing an edit: the field stays a Tab stop and stays submitted, and the calendar button is dropped because nothing in the calendar could be chosen. Unset defers to a wrapping Field. */\n    readonly?: boolean | undefined;\n    /** Error state: paints the destructive border and ring, and sets `aria-invalid`. Unset defers to a wrapping Field's `error`. */\n    invalid?: boolean | undefined;\n    /** Marks the field mandatory to assistive tech (`aria-required` on the segment group). Unset defers to a wrapping Field. */\n    required?: boolean | undefined;\n    /** The field name for a native form post or `FormData`, carried on the hidden input Reka submits the date through. Unset defers to a wrapping Field. */\n    name?: string;\n    /**\n     * Names for everything this control says out loud, as any subset of\n     * `DatePickerLabels` — the rest stay as the host's `provideLoomLabels`\n     * vocabulary left them, and then as Loom's English.\n     *\n     * This is the per-instance correction, not the place to localise an\n     * application: six of the nine names replace English literals Reka UI\n     * writes of its own accord, and a language is set once with\n     * `provideLoomLabels`.\n     */\n    labels?: LabelOverrides<DatePickerLabels>;\n  }>(),\n  {\n    locale: \"en\",\n    // Not `false`, for any of the four — TextField.vue carries the full\n    // reasoning. `false` is a caller deciding this one control is fine,\n    // enabled or editable even though its row is not; absent is a caller\n    // saying nothing, and only `undefined` survives to mean that past Vue's\n    // absent-Boolean-casts-to-false rule.\n    disabled: undefined,\n    readonly: undefined,\n    invalid: undefined,\n    required: undefined,\n  },\n);\n\nconst emit = defineEmits<{\n  /** The chosen date as ISO `YYYY-MM-DD`, or `undefined` once the field has been cleared. */\n  \"update:modelValue\": [value: string | undefined];\n}>();\n\n// Two slots, one prop. `text` is the name everywhere else in the library, and\n// there is no single `text` here because there is no single slot: the segment\n// names and the popover's chrome are separate vocabularies with separate\n// registry entries, and naming them apart is what keeps a reader of the\n// template able to see which one a binding came from. The one `labels` prop\n// feeds both — a getter returning the intersection satisfies either half, and\n// the keys the other half does not know are ignored by `useLabels`' own return\n// type.\nconst segmentText = useLabels(\"dateSegments\", DATE_SEGMENT_LABELS, () => props.labels);\nconst panelText = useLabels(\"calendarPanel\", CALENDAR_PANEL_LABELS, () => props.labels);\n\n// Read through the ref on every call rather than resolved into a lookup table\n// once: a table built in `setup` freezes the first language and every later\n// switch silently does nothing. `undefined` for the parts this slice does not\n// name — the `literal` separators, which Reka renders `aria-hidden` and which\n// must stay unnamed.\nfunction segmentLabel(part: string): string | undefined {\n  return isDateSegmentPart(part) ? segmentText.value[part] : undefined;\n}\n\n// The companion to `segmentLabel`, and the reason it returns an object rather\n// than a string is in `emptySegmentValueText`: Reka's `aria-valuetext` is a\n// hard-coded \"Empty\" only while the segment holds nothing, so this replaces\n// that case and leaves the filled one — a number, and the locale's own month\n// name — exactly as Reka wrote it.\n//\n// The month is the exception. Reka writes `\"5 - May\"`, with the month name from\n// `Intl.DateTimeFormat` but the separator and order hard-coded. `filledMonth`\n// lets a host compose the string their language needs (Japanese `\"5月\"`,\n// Vietnamese `\"tháng 5\"`). The numeric month arrives from the parsed model value\n// rather than from the segment's displayed text, because `item.value` is the\n// locale-formatted display and may not contain a parseable number.\nfunction segmentValueText(\n  part: string,\n  value: string,\n  monthValue?: number,\n): { \"aria-valuetext\"?: string } {\n  const empty = emptySegmentValueText(part, value, segmentText.value.empty);\n  if (empty[\"aria-valuetext\"]) return empty;\n  if (part === \"month\" && monthValue !== undefined) {\n    return {\n      \"aria-valuetext\": segmentText.value.filledMonth({ value: monthValue, locale: props.locale }),\n    };\n  }\n  return {};\n}\n\n// `class` sizes the whole control, so it lands on the anchor — the element the\n// caller's `max-w-xs` has to reach, and the one the popover measures itself\n// against. Every other fallthrough attribute goes one level in, onto the\n// `role=\"group\"` field: `aria-label`, `aria-labelledby` and `aria-describedby`\n// name and describe the thing being entered, and a group is what a screen\n// reader announces that name on entering. Putting them on the anchor instead\n// would name a layout div nothing ever lands in.\ndefineOptions({ inheritAttrs: false });\nconst { attrs, rest: fieldAttrs } = useSplitAttrs();\n\n/**\n * The date segments are `<div role=\"spinbutton\" tabindex=\"0\">`, and\n * `<fieldset disabled>` reaches only `<input>`, `<button>`, `<select>` and\n * `<textarea>` — so the calendar trigger inside a disabled group went inert\n * while the segments beside it still typed a date on an arrow key. Measured in\n * jsdom: an empty `mm` segment became `8`.\n *\n * Read off the DOM rather than taken from the Field context, which publishes no\n * `disabled` on purpose — see `../../lib/ancestor-disabled.ts`.\n */\nconst anchor = useTemplateRef<{ $el?: Element }>(\"anchor\");\nconst groupDisabled = useAncestorDisabled(() => anchor.value?.$el);\n\n// `id` and `aria-describedby` reach this control as fallthrough attrs rather\n// than props, so they are read off `attrs` and handed in as this caller's own\n// values — a caller who sets either still beats the row, and the row's\n// description is merged into theirs rather than replacing it.\n//\n// `field.attrs` spreads onto `DatePickerField` **after** `fieldAttrs`, which is\n// the node those two were already landing on, and the position is the contract:\n// the bag has resolved the caller's own values already and drops every key that\n// resolved to nothing, so it can only add. Where each key ends up is Reka's\n// decision and worth knowing: `DateFieldRoot` declares `id` and `name` as props\n// and puts both on the visually-hidden `<input>` it submits the date through —\n// which is the element a `<label for>` can actually name, a `role=\"group\"` div\n// being unlabelable — while `aria-describedby`, `aria-required` and\n// `aria-invalid` are undeclared, fall through to `$attrs`, and land on the group\n// itself, where a screen reader announces them once on entering the field.\n//\n// The `:aria-invalid` binding that used to sit on the field is gone with it: an\n// individual attribute written after a `v-bind` wins, so keeping one would\n// overwrite the resolved value with the raw prop.\nconst field = useFieldControl(() => ({\n  id: attrs.id as string | undefined,\n  describedBy: attrs[\"aria-describedby\"] as string | undefined,\n  ariaLabelledby: attrs[\"aria-labelledby\"] as string | undefined,\n  name: props.name,\n  // The fieldset beats the prop in both directions, exactly as it does for the\n  // trigger button inside this very control.\n  disabled: groupDisabled.value ? true : props.disabled,\n  readonly: props.readonly,\n  invalid: props.invalid,\n  required: props.required,\n}));\n\n// `aria-labelledby` for the group, resolved against the row. A caller who passes\n// `aria-labelledby` as a fallthrough attr wins (it reaches this control's own\n// `ariaLabelledby` through `useFieldControl`). A caller who passes `aria-label`\n// wins too — `aria-labelledby` overrides `aria-label` in ARIA, so the row's\n// label must not appear when the caller named the control themselves. Otherwise,\n// the row's label (published by Field as `labelledBy`) is the accessible name.\nconst groupLabelledBy = computed(() =>\n  attrs[\"aria-label\"] || attrs[\"aria-labelledby\"] ? undefined : field.labelledBy,\n);\n\nfunction fromIso(value: string | undefined): DateValue | undefined {\n  if (!value) return undefined;\n  try {\n    return parseDate(value);\n  } catch {\n    return undefined;\n  }\n}\n\n// `toString()` already normalises to the Gregorian ISO form whatever calendar\n// the value carries — a locale such as `th-TH` makes Reka's own placeholder a\n// Buddhist date whose year reads 2569, and it still prints `2026-08-11`. What\n// `toCalendarDate` adds is dropping a time component before it can turn the\n// string into `2026-08-11T00:00:00`. `granularity=\"day\"` below is what makes\n// that unreachable today; this is what keeps it unreachable if it ever moves.\nfunction toIso(date: DateValue): string {\n  return toCalendarDate(date).toString();\n}\n\n// `optional()` rather than three separate bindings: an absent bound forwarded\n// as an explicit `undefined` is still a key Reka sees, and an absent\n// `modelValue` forwarded that way is what turns an uncontrolled field into a\n// permanently empty one. Dropping the key says what is true.\nconst rootValue = computed(() =>\n  optional({\n    modelValue: fromIso(props.modelValue),\n    minValue: fromIso(props.min),\n    maxValue: fromIso(props.max),\n  }),\n);\n\n// The panel's open state is owned here rather than left to Reka's\n// `closeOnSelect`, which closes by watching its *own* model value — and that\n// value only moves for a host that echoes the emitted date straight back down.\n// A host that validates before accepting one, or that binds nothing at all,\n// would pick a day and watch the calendar stay open over the field it just\n// filled. Closing on the choice itself does not depend on anyone answering.\nconst open = ref(false);\n\nfunction onDateChange(date: DateValue | undefined) {\n  open.value = false;\n  emit(\"update:modelValue\", date ? toIso(date) : undefined);\n}\n\n// Today is a state, and it may not be carried by the marker dot alone — a\n// reader who cannot see the dot gets `aria-current=\"date\"`, which is the one\n// attribute screen readers already announce for \"this is the current one\".\n// Reka publishes today only as a `data-` attribute and a slot prop, neither of\n// which can reach an attribute binding on the cell itself.\nfunction isDateToday(date: DateValue): boolean {\n  return isToday(date, getLocalTimeZone());\n}\n\n// The field is one Tab stop, not three. Reka leaves every segment tabbable,\n// which turns a single date into three stops a keyboard user has to walk\n// through — and the control everyone already knows, the browser's own date\n// input, is one stop with the arrow keys moving inside it. So a roving\n// tabindex names exactly one segment as the stop, and Reka's own\n// ArrowLeft/ArrowRight handling (and its auto-advance after a filled segment)\n// moves between them by calling `focus()` directly, which ignores tabindex\n// entirely and so keeps working untouched.\nconst focusedPart = ref<string>();\n\nfunction segmentTabIndex(part: string, segments: readonly { part: string }[]): number | undefined {\n  // A disabled field has no stop at all; returning `undefined` removes the\n  // attribute, which is exactly what Reka does for the same case. A read-only\n  // one keeps every stop it had — the value is on show and a reader still\n  // arrows across it to read it, which is the whole difference between the two\n  // states.\n  if (field.disabled || part === \"literal\") return undefined;\n  const editable = segments.filter((segment) => segment.part !== \"literal\");\n  // The remembered segment is dropped when a locale change takes it away —\n  // a field with no tab stop is unreachable, and `en` has no era segment that\n  // `ja-JP-u-ca-japanese` does.\n  const active =\n    focusedPart.value !== undefined &&\n    editable.some((segment) => segment.part === focusedPart.value)\n      ? focusedPart.value\n      : editable[0]?.part;\n  return part === active ? 0 : -1;\n}\n\n// The month/year heading names the grid, so the two are wired together rather\n// than the grid being an unnamed table of numbers.\nconst headingId = useId();\n\nconst panel = ref<HTMLElement | null>(null);\n\n// Reka's focus scope would land on the first tabbable thing in the panel,\n// which is the previous-month button — so a keyboard user opening the calendar\n// arrives one Tab away from the grid and two from the day they came for.\n// Focus goes to the day the calendar is already sitting on instead: the\n// selected date, or today when nothing is selected, which is the cell Reka has\n// given the grid's own roving tabindex to.\nfunction onOpenAutoFocus(event: Event) {\n  const day = panel.value?.querySelector<HTMLElement>(\n    '[data-reka-calendar-cell-trigger][tabindex=\"0\"]',\n  );\n  if (!day) return;\n  event.preventDefault();\n  day.focus();\n}\n</script>\n\n<template>\n  <DatePickerRoot\n    v-model:open=\"open\"\n    v-bind=\"rootValue\"\n    :locale=\"locale\"\n    :disabled=\"field.disabled\"\n    :readonly=\"field.readonly\"\n    granularity=\"day\"\n    prevent-deselect\n    @update:model-value=\"onDateChange\"\n  >\n    <!-- The invalid marker lives out here, on the control as a whole, because\n         the field group below already carries a `data-invalid` of Reka's own\n         with a different meaning: that the *typed* date falls outside `min` and\n         `max`. Two markers spelled the same on one element is how a style rule\n         starts answering a question nobody asked it. -->\n    <DatePickerAnchor\n      ref=\"anchor\"\n      :data-invalid=\"field.invalid || undefined\"\n      :data-readonly=\"field.readonly || undefined\"\n      :class=\"cn('block w-full', attrs.class as string)\"\n    >\n      <DatePickerField\n        v-slot=\"{ segments }\"\n        v-bind=\"{ ...fieldAttrs, ...field.attrs }\"\n        :aria-labelledby=\"groupLabelledBy\"\n        :class=\"\n          cn(\n            // The text input's own height scale, so a date sitting in a form\n            // row beside a text field lines up rather than nearly lining up.\n            // No gap: the separator between two segments is itself a segment,\n            // so spacing them apart writes the date as `3 / 14 / 2026`.\n            'flex h-9 w-full items-center rounded-md border border-input bg-background px-3 text-sm text-foreground',\n            'transition-[color,background-color,border-color,box-shadow] duration-fast ease-out',\n            // The box carries the ring, exactly as TextField's wrapper does,\n            // and the focused segment below carries a fill instead of a second\n            // outline — a ring drawn inside a ring reads as a rendering fault.\n            'focus-within:outline-2 focus-within:outline-offset-2 focus-within:outline-ring',\n            !field.invalid && 'focus-within:shadow-halo',\n            // Three resting appearances, and every one of them belongs to this\n            // group rather than to the segments inside it. A fill painted per\n            // segment leaves the literal separators between them on\n            // `background`, and the control comes out striped.\n            //\n            // Read-only keeps its focus ring and its full-strength text: a\n            // read-only date is a value on show, not an unavailable control,\n            // and the two must not look alike. The fill lifts off `background`\n            // to `subtle`, which holds the segments at 13.46:1, and the rim\n            // stays `input` because nothing about the field's reach has moved —\n            // it is still a Tab stop and still submitted. Reka's own\n            // `data-readonly` on this group carries the same state to assistive\n            // tech, so nothing here rests on colour.\n            field.readonly && 'bg-subtle',\n            // Unavailable is a *colour* and a *weight*, never an opacity.\n            // `opacity-50` here faded the segments along with the box, and the\n            // segments are the whole content of the control: `--color-foreground`\n            // measures 14.09:1 on the resting fill and 2.99:1 once composited at\n            // half alpha, with the literal separators and any placeholder\n            // segment down at 2.02:1. The fill drains one step past read-only,\n            // the text follows it to a measured 4.68:1, and the rim slackens\n            // from `input` to `border` — so the two unavailable-looking states\n            // part on three channels rather than on hue alone, which is what a\n            // reader who cannot separate two greys has to have.\n            //\n            // The colour is set here rather than on each segment because no\n            // segment declares one of its own in the resting state, so each\n            // inherits this; `focus:text-primary-text` below is unreachable on a\n            // control that cannot take focus.\n            field.disabled && 'cursor-not-allowed border-border bg-muted text-muted-foreground',\n            // Last of the rules that name a border colour, and the order is\n            // load-bearing: `cn()` resolves a border colour by whichever class\n            // it saw last, so a field that is both in error and unavailable\n            // would otherwise lose its destructive rim to the disabled one.\n            field.invalid && 'border-destructive focus-within:outline-destructive',\n          )\n        \"\n      >\n        <!-- Every `:aria-label` from here down replaces one Reka writes in\n             English inside its own render function. Each reaches the DOM node\n             as a fallthrough attribute, which Vue merges last, so it is a\n             replacement rather than a second name. Removing one does not fall\n             back to nothing; it falls back to Reka's English, which is the\n             failure the label seam exists to close and which no test of Loom's\n             own strings would catch. -->\n        <DatePickerInput\n          v-for=\"(item, index) in segments\"\n          :key=\"index\"\n          :part=\"item.part\"\n          :tabindex=\"segmentTabIndex(item.part, segments)\"\n          :aria-label=\"segmentLabel(item.part)\"\n          v-bind=\"segmentValueText(item.part, item.value, fromIso(props.modelValue)?.month)\"\n          :class=\"\n            cn(\n              'tabular rounded-sm px-0.5 outline-none',\n              'transition-colors duration-instant ease-out',\n              'focus:bg-primary-muted focus:text-primary-text',\n              'data-[placeholder]:text-muted-foreground',\n              item.part === 'literal' && 'text-muted-foreground',\n            )\n          \"\n          @focusin=\"focusedPart = item.part\"\n        >\n          {{ item.value }}\n        </DatePickerInput>\n\n        <!-- Dropped entirely while read-only rather than disabled beside a\n             field that is plainly still alive. Reka's `readonly` reaches the\n             calendar too and makes every cell's click a no-op, so the button\n             would open a panel in which nothing can be chosen — a dead end that\n             looks like a working control, which is worse than not offering it.\n             The segments are still there to read the date off. -->\n        <DatePickerTrigger\n          v-if=\"!field.readonly\"\n          :aria-label=\"panelText.openCalendar\"\n          class=\"ml-auto inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring disabled:cursor-not-allowed\"\n        >\n          <CalendarDays class=\"h-4 w-4\" />\n        </DatePickerTrigger>\n      </DatePickerField>\n    </DatePickerAnchor>\n\n    <DatePickerContent\n      align=\"start\"\n      :side-offset=\"6\"\n      :class=\"\n        cn(\n          'z-overlay rounded-md border border-border bg-popover p-3 text-popover-foreground shadow-md outline-none',\n          // Both halves of the motion are scoped to their own state, never\n          // unconditional. Reka's Presence decides unmounting from the\n          // computed animation-name: an unconditional entrance left the closed\n          // panel computing a finished animation it would wait on forever — an\n          // invisible layer over the page, eating clicks. Scoped, closing\n          // swaps the computed animation to fade-fall's, and Presence holds\n          // the panel exactly one exit long, releasing it at animationend.\n          'data-[state=open]:animate-fade-rise data-[state=closed]:animate-fade-fall',\n        )\n      \"\n      @open-auto-focus=\"onOpenAutoFocus\"\n    >\n      <!-- The whole panel rises as one piece. The 42 cells deliberately carry\n           no stagger of their own: `listStaggerDelay` is the vocabulary for a\n           list of rows arriving in reading order, and a grid rippling in cell\n           by cell reads as a rendering glitch rather than as an entrance. -->\n      <div ref=\"panel\" class=\"flex flex-col gap-3\">\n        <!-- `calendarLabel` is a real Reka prop rather than a literal to\n             override, and it defaults to `\"Event Date\"` — a name for somebody\n             else's application. It is published twice: as the calendar\n             container's `aria-label`, and inside a visually-hidden live region\n             Reka renders itself, which a fallthrough attribute could not have\n             reached. -->\n        <DatePickerCalendar v-slot=\"{ grid, weekDays }\" :calendar-label=\"panelText.calendar\">\n          <DatePickerHeader class=\"flex items-center justify-between gap-2\">\n            <!-- The two pagers keep `data-[disabled]:opacity-50` where the\n                 field and the cells gave it up, and the difference is what is\n                 inside them: a chevron and nothing else. Fading a glyph costs a\n                 reader nothing, and the buttons carry their name in\n                 `aria-label` rather than in dimmed text. -->\n            <DatePickerPrev\n              :aria-label=\"panelText.previousMonth\"\n              class=\"inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring data-[disabled]:pointer-events-none data-[disabled]:opacity-50\"\n            >\n              <ChevronLeft class=\"h-4 w-4\" />\n            </DatePickerPrev>\n\n            <!-- Paging the calendar changes nothing a reader is looking at\n                 except this line, and nothing moves focus — so without the\n                 live region the month silently becomes a different month. -->\n            <DatePickerHeading\n              :id=\"headingId\"\n              aria-live=\"polite\"\n              class=\"text-sm font-medium text-foreground\"\n            />\n\n            <DatePickerNext\n              :aria-label=\"panelText.nextMonth\"\n              class=\"inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring data-[disabled]:pointer-events-none data-[disabled]:opacity-50\"\n            >\n              <ChevronRight class=\"h-4 w-4\" />\n            </DatePickerNext>\n          </DatePickerHeader>\n\n          <DatePickerGrid\n            v-for=\"month in grid\"\n            :key=\"month.value.toString()\"\n            role=\"grid\"\n            :aria-labelledby=\"headingId\"\n            class=\"border-collapse select-none\"\n          >\n            <!-- Reka renders `role=\"application\"` here, which hands every key\n                 straight to the page and takes the table's own semantics away\n                 with it. A calendar is a grid: `role=\"grid\"` is what makes the\n                 cells rows and columns to a screen reader rather than 42\n                 unrelated buttons, and the arrow-key handling Reka installs on\n                 the cells is what a grid promises anyway.\n\n                 The rows and cells below are laid out by the table itself\n                 rather than by flex, and that is load-bearing: `display: flex`\n                 on a `tr` drops its implicit `row` mapping in Chromium and\n                 WebKit, which leaves `role=\"gridcell\"` inside a grid with no\n                 row between them — a broken grid that looks identical. -->\n            <DatePickerGridHead>\n              <DatePickerGridRow>\n                <DatePickerHeadCell\n                  v-for=\"(day, index) in weekDays\"\n                  :key=\"index\"\n                  class=\"w-9 text-xs font-normal text-muted-foreground\"\n                >\n                  {{ day }}\n                </DatePickerHeadCell>\n              </DatePickerGridRow>\n            </DatePickerGridHead>\n\n            <DatePickerGridBody>\n              <DatePickerGridRow v-for=\"(week, weekIndex) in month.rows\" :key=\"weekIndex\">\n                <DatePickerCell\n                  v-for=\"day in week\"\n                  :key=\"day.toString()\"\n                  :date=\"day\"\n                  class=\"p-0 text-center\"\n                >\n                  <!-- A day out of `min`/`max` range is drawn in colour rather\n                       than faded: the number is the cell's whole content, and\n                       `opacity-50` took `--color-foreground` from 14.09:1 on\n                       the popover to 3.13:1. Muted is 5.76:1 and the rule is\n                       written as `:not([data-selected])` so it can never order\n                       against the selected fill's own text colour — the same\n                       trick the range pickers use on their four competing\n                       fills. The strike is the second, hueless cue, and it is\n                       what keeps an unavailable day apart from an adjacent\n                       month's, which is muted too and still selectable. -->\n                  <DatePickerCellTrigger\n                    v-slot=\"{ dayValue, today }\"\n                    :day=\"day\"\n                    :month=\"month.value\"\n                    :aria-current=\"isDateToday(day) ? 'date' : undefined\"\n                    class=\"group relative inline-flex h-9 w-9 items-center justify-center rounded-sm text-sm text-foreground transition-colors duration-fast ease-out hover:bg-subtle focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring focus-visible:shadow-halo data-[outside-view]:text-muted-foreground data-[selected]:bg-primary data-[selected]:text-primary-foreground data-[disabled]:pointer-events-none data-[disabled]:line-through [&[data-disabled]:not([data-selected])]:text-muted-foreground\"\n                  >\n                    {{ dayValue }}\n                    <!-- Today's second cue. The dot is decoration to a screen\n                         reader — `aria-current` on the cell is what it reads —\n                         but it is the whole cue for a reader who is looking at\n                         the grid, and it is a shape rather than a hue so it\n                         survives a colour deficiency and forced-colors both. -->\n                    <span\n                      v-if=\"today\"\n                      aria-hidden=\"true\"\n                      class=\"absolute bottom-1 h-1 w-1 rounded-full bg-primary group-data-[selected]:bg-primary-foreground\"\n                    />\n                  </DatePickerCellTrigger>\n                </DatePickerCell>\n              </DatePickerGridRow>\n            </DatePickerGridBody>\n          </DatePickerGrid>\n        </DatePickerCalendar>\n      </div>\n    </DatePickerContent>\n  </DatePickerRoot>\n</template>\n"],"mappings":""}

package/dist/packages/primitives/date-picker/src/DatePicker.vue.d.ts

@@ -0,0 +1,102 @@
+import { type LabelOverrides } from "../../../labels/src/index";
+import type { CalendarPanelLabels, DateSegmentLabels } from "../../../labels/src/index";
+/**
+ * Everything this control publishes to assistive technology, which is two
+ * shared slices and nothing of its own: the names of the field's segments and
+ * the calendar popover's chrome. Both are declared in `src/lib/date-labels.ts`,
+ * because `DateTimePicker`, `DateRangePicker` and `DateTimeRangePicker` say the
+ * same words for the same reason — they are all one Reka implementation
+ * underneath — and four copies of `Previous month` is a translator writing the
+ * same word four times.
+ *
+ * An intersection rather than a third interface, so this name is the type a
+ * consumer annotates their own bag with and the two halves stay one definition
+ * each. Annotate with `LabelOverrides<DatePickerLabels>` and never with this
+ * directly: this one is total, and a key added in a later release would stop a
+ * consumer's build.
+ */
+export type DatePickerLabels = DateSegmentLabels & CalendarPanelLabels;
+declare const _default: typeof __VLS_export;
+export default _default;
+declare const __VLS_export: import("vue").DefineComponent<{
+    /**
+     * The chosen date as ISO `YYYY-MM-DD`. Unset, empty or unparseable means no
+     * date is chosen. The explicit `| undefined` is what lets `v-model` bind a
+     * ref that clears — the emitted value drops to `undefined` when the field
+     * is emptied, and a plain optional prop refuses to take it back.
+     */
+    modelValue?: string | undefined;
+    /** The earliest choosable date, same ISO format. Days before it are announced disabled and skipped by the keyboard. */
+    min?: string;
+    /** The latest choosable date, same ISO format. Days after it are announced disabled and skipped by the keyboard. */
+    max?: string;
+    /** BCP 47 tag driving the order of the field's segments, the month and weekday names, and which day a week starts on. */
+    locale?: string;
+    /** Unavailable: dims the control, refuses the calendar, and takes the field out of the tab order. Unset defers to a wrapping Field. */
+    disabled?: boolean | undefined;
+    /** Shows the date without allowing an edit: the field stays a Tab stop and stays submitted, and the calendar button is dropped because nothing in the calendar could be chosen. Unset defers to a wrapping Field. */
+    readonly?: boolean | undefined;
+    /** Error state: paints the destructive border and ring, and sets `aria-invalid`. Unset defers to a wrapping Field's `error`. */
+    invalid?: boolean | undefined;
+    /** Marks the field mandatory to assistive tech (`aria-required` on the segment group). Unset defers to a wrapping Field. */
+    required?: boolean | undefined;
+    /** The field name for a native form post or `FormData`, carried on the hidden input Reka submits the date through. Unset defers to a wrapping Field. */
+    name?: string;
+    /**
+     * Names for everything this control says out loud, as any subset of
+     * `DatePickerLabels` — the rest stay as the host's `provideLoomLabels`
+     * vocabulary left them, and then as Loom's English.
+     *
+     * This is the per-instance correction, not the place to localise an
+     * application: six of the nine names replace English literals Reka UI
+     * writes of its own accord, and a language is set once with
+     * `provideLoomLabels`.
+     */
+    labels?: LabelOverrides<DatePickerLabels>;
+}, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {
+    "update:modelValue": (value: string | undefined) => any;
+}, string, import("vue").PublicProps, Readonly<{
+    /**
+     * The chosen date as ISO `YYYY-MM-DD`. Unset, empty or unparseable means no
+     * date is chosen. The explicit `| undefined` is what lets `v-model` bind a
+     * ref that clears — the emitted value drops to `undefined` when the field
+     * is emptied, and a plain optional prop refuses to take it back.
+     */
+    modelValue?: string | undefined;
+    /** The earliest choosable date, same ISO format. Days before it are announced disabled and skipped by the keyboard. */
+    min?: string;
+    /** The latest choosable date, same ISO format. Days after it are announced disabled and skipped by the keyboard. */
+    max?: string;
+    /** BCP 47 tag driving the order of the field's segments, the month and weekday names, and which day a week starts on. */
+    locale?: string;
+    /** Unavailable: dims the control, refuses the calendar, and takes the field out of the tab order. Unset defers to a wrapping Field. */
+    disabled?: boolean | undefined;
+    /** Shows the date without allowing an edit: the field stays a Tab stop and stays submitted, and the calendar button is dropped because nothing in the calendar could be chosen. Unset defers to a wrapping Field. */
+    readonly?: boolean | undefined;
+    /** Error state: paints the destructive border and ring, and sets `aria-invalid`. Unset defers to a wrapping Field's `error`. */
+    invalid?: boolean | undefined;
+    /** Marks the field mandatory to assistive tech (`aria-required` on the segment group). Unset defers to a wrapping Field. */
+    required?: boolean | undefined;
+    /** The field name for a native form post or `FormData`, carried on the hidden input Reka submits the date through. Unset defers to a wrapping Field. */
+    name?: string;
+    /**
+     * Names for everything this control says out loud, as any subset of
+     * `DatePickerLabels` — the rest stay as the host's `provideLoomLabels`
+     * vocabulary left them, and then as Loom's English.
+     *
+     * This is the per-instance correction, not the place to localise an
+     * application: six of the nine names replace English literals Reka UI
+     * writes of its own accord, and a language is set once with
+     * `provideLoomLabels`.
+     */
+    labels?: LabelOverrides<DatePickerLabels>;
+}> & Readonly<{
+    "onUpdate:modelValue"?: (value: string | undefined) => any;
+}>, {
+    locale: string;
+    disabled: boolean | undefined;
+    invalid: boolean | undefined;
+    readonly: boolean | undefined;
+    required: boolean | undefined;
+}, {}, {}, {}, string, import("vue").ComponentProvideOptions, false, {}, any>;
+//# sourceMappingURL=DatePicker.vue.d.ts.map

package/dist/packages/primitives/date-picker/src/DatePicker.vue_vue_type_script_setup_true_lang.js

@@ -0,0 +1,294 @@
+import { cn } from "../../../core/src/cn.js";
+import { optional } from "../../../core/src/props.js";
+import { useSplitAttrs } from "../../../core/src/attrs.js";
+import "../../../core/src/index.js";
+import { useLabels } from "../../../labels/src/labels.js";
+import { getLocalTimeZone as $ad063034c8620db8$export$aa8b41735afcabd2, isToday as $ad063034c8620db8$export$629b0a497aa65267 } from "../../../../node_modules/.pnpm/@internationalized_date@3.12.3/node_modules/@internationalized/date/dist/private/queries.js";
+import { toCalendarDate as $d07e34cce18680fd$export$93522d1a439f3617 } from "../../../../node_modules/.pnpm/@internationalized_date@3.12.3/node_modules/@internationalized/date/dist/private/conversion.js";
+import { parseDate as $58246871e4652552$export$6b862160d295c8e } from "../../../../node_modules/.pnpm/@internationalized_date@3.12.3/node_modules/@internationalized/date/dist/private/string.js";
+import { CALENDAR_PANEL_LABELS, DATE_SEGMENT_LABELS, emptySegmentValueText, isDateSegmentPart } from "../../../labels/src/date-labels.js";
+import { useFieldControl } from "../../../labels/src/field-context.js";
+import { useAncestorDisabled } from "../../../labels/src/ancestor-disabled.js";
+import "../../../labels/src/index.js";
+import { Fragment, computed, createBlock, createCommentVNode, createElementBlock, createElementVNode, createTextVNode, createVNode, defineComponent, mergeProps, normalizeClass, openBlock, ref, renderList, toDisplayString, unref, useId, useTemplateRef, withCtx } from "vue";
+import { CalendarDays, ChevronLeft, ChevronRight } from "@lucide/vue";
+import { DatePickerAnchor, DatePickerCalendar, DatePickerCell, DatePickerCellTrigger, DatePickerContent, DatePickerField, DatePickerGrid, DatePickerGridBody, DatePickerGridHead, DatePickerGridRow, DatePickerHeadCell, DatePickerHeader, DatePickerHeading, DatePickerInput, DatePickerNext, DatePickerPrev, DatePickerRoot, DatePickerTrigger } from "reka-ui";
+//#region packages/primitives/date-picker/src/DatePicker.vue?vue&type=script&setup=true&lang.ts
+var _hoisted_1 = {
+	key: 0,
+	"aria-hidden": "true",
+	class: "absolute bottom-1 h-1 w-1 rounded-full bg-primary group-data-[selected]:bg-primary-foreground"
+};
+var DatePicker_vue_vue_type_script_setup_true_lang_default = /*@__PURE__*/ defineComponent({
+	inheritAttrs: false,
+	__name: "DatePicker",
+	props: {
+		modelValue: {},
+		min: {},
+		max: {},
+		locale: { default: "en" },
+		disabled: {
+			type: Boolean,
+			default: void 0
+		},
+		readonly: {
+			type: Boolean,
+			default: void 0
+		},
+		invalid: {
+			type: Boolean,
+			default: void 0
+		},
+		required: {
+			type: Boolean,
+			default: void 0
+		},
+		name: {},
+		labels: {}
+	},
+	emits: ["update:modelValue"],
+	setup(__props, { emit: __emit }) {
+		const props = __props;
+		const emit = __emit;
+		const segmentText = useLabels("dateSegments", DATE_SEGMENT_LABELS, () => props.labels);
+		const panelText = useLabels("calendarPanel", CALENDAR_PANEL_LABELS, () => props.labels);
+		function segmentLabel(part) {
+			return isDateSegmentPart(part) ? segmentText.value[part] : void 0;
+		}
+		function segmentValueText(part, value, monthValue) {
+			const empty = emptySegmentValueText(part, value, segmentText.value.empty);
+			if (empty["aria-valuetext"]) return empty;
+			if (part === "month" && monthValue !== void 0) return { "aria-valuetext": segmentText.value.filledMonth({
+				value: monthValue,
+				locale: props.locale
+			}) };
+			return {};
+		}
+		const { attrs, rest: fieldAttrs } = useSplitAttrs();
+		/**
+		* The date segments are `<div role="spinbutton" tabindex="0">`, and
+		* `<fieldset disabled>` reaches only `<input>`, `<button>`, `<select>` and
+		* `<textarea>` — so the calendar trigger inside a disabled group went inert
+		* while the segments beside it still typed a date on an arrow key. Measured in
+		* jsdom: an empty `mm` segment became `8`.
+		*
+		* Read off the DOM rather than taken from the Field context, which publishes no
+		* `disabled` on purpose — see `../../lib/ancestor-disabled.ts`.
+		*/
+		const anchor = useTemplateRef("anchor");
+		const groupDisabled = useAncestorDisabled(() => anchor.value?.$el);
+		const field = useFieldControl(() => ({
+			id: attrs.id,
+			describedBy: attrs["aria-describedby"],
+			ariaLabelledby: attrs["aria-labelledby"],
+			name: props.name,
+			disabled: groupDisabled.value ? true : props.disabled,
+			readonly: props.readonly,
+			invalid: props.invalid,
+			required: props.required
+		}));
+		const groupLabelledBy = computed(() => attrs["aria-label"] || attrs["aria-labelledby"] ? void 0 : field.labelledBy);
+		function fromIso(value) {
+			if (!value) return void 0;
+			try {
+				return $58246871e4652552$export$6b862160d295c8e(value);
+			} catch {
+				return;
+			}
+		}
+		function toIso(date) {
+			return $d07e34cce18680fd$export$93522d1a439f3617(date).toString();
+		}
+		const rootValue = computed(() => optional({
+			modelValue: fromIso(props.modelValue),
+			minValue: fromIso(props.min),
+			maxValue: fromIso(props.max)
+		}));
+		const open = ref(false);
+		function onDateChange(date) {
+			open.value = false;
+			emit("update:modelValue", date ? toIso(date) : void 0);
+		}
+		function isDateToday(date) {
+			return $ad063034c8620db8$export$629b0a497aa65267(date, $ad063034c8620db8$export$aa8b41735afcabd2());
+		}
+		const focusedPart = ref();
+		function segmentTabIndex(part, segments) {
+			if (field.disabled || part === "literal") return void 0;
+			const editable = segments.filter((segment) => segment.part !== "literal");
+			return part === (focusedPart.value !== void 0 && editable.some((segment) => segment.part === focusedPart.value) ? focusedPart.value : editable[0]?.part) ? 0 : -1;
+		}
+		const headingId = useId();
+		const panel = ref(null);
+		function onOpenAutoFocus(event) {
+			const day = panel.value?.querySelector("[data-reka-calendar-cell-trigger][tabindex=\"0\"]");
+			if (!day) return;
+			event.preventDefault();
+			day.focus();
+		}
+		return (_ctx, _cache) => {
+			return openBlock(), createBlock(unref(DatePickerRoot), mergeProps({
+				open: open.value,
+				"onUpdate:open": _cache[0] || (_cache[0] = ($event) => open.value = $event)
+			}, rootValue.value, {
+				locale: __props.locale,
+				disabled: unref(field).disabled,
+				readonly: unref(field).readonly,
+				granularity: "day",
+				"prevent-deselect": "",
+				"onUpdate:modelValue": onDateChange
+			}), {
+				default: withCtx(() => [createVNode(unref(DatePickerAnchor), {
+					ref_key: "anchor",
+					ref: anchor,
+					"data-invalid": unref(field).invalid || void 0,
+					"data-readonly": unref(field).readonly || void 0,
+					class: normalizeClass(unref(cn)("block w-full", unref(attrs).class))
+				}, {
+					default: withCtx(() => [createVNode(unref(DatePickerField), mergeProps({
+						...unref(fieldAttrs),
+						...unref(field).attrs
+					}, {
+						"aria-labelledby": groupLabelledBy.value,
+						class: unref(cn)("flex h-9 w-full items-center rounded-md border border-input bg-background px-3 text-sm text-foreground", "transition-[color,background-color,border-color,box-shadow] duration-fast ease-out", "focus-within:outline-2 focus-within:outline-offset-2 focus-within:outline-ring", !unref(field).invalid && "focus-within:shadow-halo", unref(field).readonly && "bg-subtle", unref(field).disabled && "cursor-not-allowed border-border bg-muted text-muted-foreground", unref(field).invalid && "border-destructive focus-within:outline-destructive")
+					}), {
+						default: withCtx(({ segments }) => [(openBlock(true), createElementBlock(Fragment, null, renderList(segments, (item, index) => {
+							return openBlock(), createBlock(unref(DatePickerInput), mergeProps({
+								key: index,
+								part: item.part,
+								tabindex: segmentTabIndex(item.part, segments),
+								"aria-label": segmentLabel(item.part)
+							}, { ref_for: true }, segmentValueText(item.part, item.value, fromIso(props.modelValue)?.month), {
+								class: unref(cn)("tabular rounded-sm px-0.5 outline-none", "transition-colors duration-instant ease-out", "focus:bg-primary-muted focus:text-primary-text", "data-[placeholder]:text-muted-foreground", item.part === "literal" && "text-muted-foreground"),
+								onFocusin: ($event) => focusedPart.value = item.part
+							}), {
+								default: withCtx(() => [createTextVNode(toDisplayString(item.value), 1)]),
+								_: 2
+							}, 1040, [
+								"part",
+								"tabindex",
+								"aria-label",
+								"class",
+								"onFocusin"
+							]);
+						}), 128)), !unref(field).readonly ? (openBlock(), createBlock(unref(DatePickerTrigger), {
+							key: 0,
+							"aria-label": unref(panelText).openCalendar,
+							class: "ml-auto inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring disabled:cursor-not-allowed"
+						}, {
+							default: withCtx(() => [createVNode(unref(CalendarDays), { class: "h-4 w-4" })]),
+							_: 1
+						}, 8, ["aria-label"])) : createCommentVNode("", true)]),
+						_: 1
+					}, 16, ["aria-labelledby", "class"])]),
+					_: 1
+				}, 8, [
+					"data-invalid",
+					"data-readonly",
+					"class"
+				]), createVNode(unref(DatePickerContent), {
+					align: "start",
+					"side-offset": 6,
+					class: normalizeClass(unref(cn)("z-overlay rounded-md border border-border bg-popover p-3 text-popover-foreground shadow-md outline-none", "data-[state=open]:animate-fade-rise data-[state=closed]:animate-fade-fall")),
+					onOpenAutoFocus
+				}, {
+					default: withCtx(() => [createElementVNode("div", {
+						ref_key: "panel",
+						ref: panel,
+						class: "flex flex-col gap-3"
+					}, [createVNode(unref(DatePickerCalendar), { "calendar-label": unref(panelText).calendar }, {
+						default: withCtx(({ grid, weekDays }) => [createVNode(unref(DatePickerHeader), { class: "flex items-center justify-between gap-2" }, {
+							default: withCtx(() => [
+								createVNode(unref(DatePickerPrev), {
+									"aria-label": unref(panelText).previousMonth,
+									class: "inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring data-[disabled]:pointer-events-none data-[disabled]:opacity-50"
+								}, {
+									default: withCtx(() => [createVNode(unref(ChevronLeft), { class: "h-4 w-4" })]),
+									_: 1
+								}, 8, ["aria-label"]),
+								createVNode(unref(DatePickerHeading), {
+									id: unref(headingId),
+									"aria-live": "polite",
+									class: "text-sm font-medium text-foreground"
+								}, null, 8, ["id"]),
+								createVNode(unref(DatePickerNext), {
+									"aria-label": unref(panelText).nextMonth,
+									class: "inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring data-[disabled]:pointer-events-none data-[disabled]:opacity-50"
+								}, {
+									default: withCtx(() => [createVNode(unref(ChevronRight), { class: "h-4 w-4" })]),
+									_: 1
+								}, 8, ["aria-label"])
+							]),
+							_: 1
+						}), (openBlock(true), createElementBlock(Fragment, null, renderList(grid, (month) => {
+							return openBlock(), createBlock(unref(DatePickerGrid), {
+								key: month.value.toString(),
+								role: "grid",
+								"aria-labelledby": unref(headingId),
+								class: "border-collapse select-none"
+							}, {
+								default: withCtx(() => [createVNode(unref(DatePickerGridHead), null, {
+									default: withCtx(() => [createVNode(unref(DatePickerGridRow), null, {
+										default: withCtx(() => [(openBlock(true), createElementBlock(Fragment, null, renderList(weekDays, (day, index) => {
+											return openBlock(), createBlock(unref(DatePickerHeadCell), {
+												key: index,
+												class: "w-9 text-xs font-normal text-muted-foreground"
+											}, {
+												default: withCtx(() => [createTextVNode(toDisplayString(day), 1)]),
+												_: 2
+											}, 1024);
+										}), 128))]),
+										_: 2
+									}, 1024)]),
+									_: 2
+								}, 1024), createVNode(unref(DatePickerGridBody), null, {
+									default: withCtx(() => [(openBlock(true), createElementBlock(Fragment, null, renderList(month.rows, (week, weekIndex) => {
+										return openBlock(), createBlock(unref(DatePickerGridRow), { key: weekIndex }, {
+											default: withCtx(() => [(openBlock(true), createElementBlock(Fragment, null, renderList(week, (day) => {
+												return openBlock(), createBlock(unref(DatePickerCell), {
+													key: day.toString(),
+													date: day,
+													class: "p-0 text-center"
+												}, {
+													default: withCtx(() => [createVNode(unref(DatePickerCellTrigger), {
+														day,
+														month: month.value,
+														"aria-current": isDateToday(day) ? "date" : void 0,
+														class: "group relative inline-flex h-9 w-9 items-center justify-center rounded-sm text-sm text-foreground transition-colors duration-fast ease-out hover:bg-subtle focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring focus-visible:shadow-halo data-[outside-view]:text-muted-foreground data-[selected]:bg-primary data-[selected]:text-primary-foreground data-[disabled]:pointer-events-none data-[disabled]:line-through [&[data-disabled]:not([data-selected])]:text-muted-foreground"
+													}, {
+														default: withCtx(({ dayValue, today }) => [createTextVNode(toDisplayString(dayValue) + " ", 1), today ? (openBlock(), createElementBlock("span", _hoisted_1)) : createCommentVNode("", true)]),
+														_: 1
+													}, 8, [
+														"day",
+														"month",
+														"aria-current"
+													])]),
+													_: 2
+												}, 1032, ["date"]);
+											}), 128))]),
+											_: 2
+										}, 1024);
+									}), 128))]),
+									_: 2
+								}, 1024)]),
+								_: 2
+							}, 1032, ["aria-labelledby"]);
+						}), 128))]),
+						_: 1
+					}, 8, ["calendar-label"])], 512)]),
+					_: 1
+				}, 8, ["class"])]),
+				_: 1
+			}, 16, [
+				"open",
+				"locale",
+				"disabled",
+				"readonly"
+			]);
+		};
+	}
+});
+//#endregion
+export { DatePicker_vue_vue_type_script_setup_true_lang_default as default };
+
+//# sourceMappingURL=DatePicker.vue_vue_type_script_setup_true_lang.js.map

package/dist/packages/primitives/date-picker/src/DatePicker.vue_vue_type_script_setup_true_lang.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"DatePicker.vue_vue_type_script_setup_true_lang.js","names":[],"sources":["../../../../../packages/primitives/date-picker/src/DatePicker.vue"],"sourcesContent":["<script lang=\"ts\">\nimport type { CalendarPanelLabels, DateSegmentLabels } from \"@ecoma-io/loom-labels\";\n\n/**\n * Everything this control publishes to assistive technology, which is two\n * shared slices and nothing of its own: the names of the field's segments and\n * the calendar popover's chrome. Both are declared in `src/lib/date-labels.ts`,\n * because `DateTimePicker`, `DateRangePicker` and `DateTimeRangePicker` say the\n * same words for the same reason — they are all one Reka implementation\n * underneath — and four copies of `Previous month` is a translator writing the\n * same word four times.\n *\n * An intersection rather than a third interface, so this name is the type a\n * consumer annotates their own bag with and the two halves stay one definition\n * each. Annotate with `LabelOverrides<DatePickerLabels>` and never with this\n * directly: this one is total, and a key added in a later release would stop a\n * consumer's build.\n */\nexport type DatePickerLabels = DateSegmentLabels & CalendarPanelLabels;\n</script>\n\n<script setup lang=\"ts\">\nimport { computed, ref, useId, useTemplateRef } from \"vue\";\nimport {\n  DatePickerRoot,\n  DatePickerAnchor,\n  DatePickerField,\n  DatePickerInput,\n  DatePickerTrigger,\n  DatePickerContent,\n  DatePickerCalendar,\n  DatePickerHeader,\n  DatePickerPrev,\n  DatePickerHeading,\n  DatePickerNext,\n  DatePickerGrid,\n  DatePickerGridHead,\n  DatePickerGridRow,\n  DatePickerHeadCell,\n  DatePickerGridBody,\n  DatePickerCell,\n  DatePickerCellTrigger,\n} from \"reka-ui\";\nimport { CalendarDays, ChevronLeft, ChevronRight } from \"@lucide/vue\";\nimport {\n  getLocalTimeZone,\n  isToday,\n  parseDate,\n  toCalendarDate,\n  type DateValue,\n} from \"@internationalized/date\";\nimport { cn } from \"@ecoma-io/loom-core\";\nimport { useSplitAttrs } from \"@ecoma-io/loom-core\";\nimport { useAncestorDisabled } from \"@ecoma-io/loom-labels\";\nimport { useFieldControl } from \"@ecoma-io/loom-labels\";\nimport { optional } from \"@ecoma-io/loom-core\";\nimport { useLabels, type LabelOverrides } from \"@ecoma-io/loom-labels\";\nimport {\n  CALENDAR_PANEL_LABELS,\n  DATE_SEGMENT_LABELS,\n  emptySegmentValueText,\n  isDateSegmentPart,\n} from \"@ecoma-io/loom-labels\";\n\n/**\n * DatePicker — one calendar date, entered either by typing it into a segmented\n * field or by picking it out of a calendar popover. Reach for it wherever a\n * date is a value rather than a search: a due date, a start date, a date of\n * birth.\n *\n * The segmented field is the reason this is not an `<input type=\"date\">`.\n * Arrow keys change the segment under the cursor, typing digits fills it and\n * advances, and the segment order and the month names follow `locale` rather\n * than the browser's own — which is what lets a Vietnamese reader and an\n * American reader see the same date written the way each of them writes it.\n * The calendar is the second path to the same value, not the only one.\n *\n * **The model value is a plain ISO date string, `\"YYYY-MM-DD\"`, never a\n * `DateValue`.** Reka and `@internationalized/date` model a date as a calendar\n * object, and that object is the right shape *inside* a date control — it\n * knows about calendars other than the Gregorian one, about month lengths, and\n * about what \"next month\" means on the 31st. It is the wrong shape at the\n * boundary: a host binding a due date has a string from its API and wants a\n * string back for it, and nobody should have to learn a date library to bind a\n * date. So the string is parsed on the way in and re-serialised on the way\n * out, the same instinct as Slider exposing a scalar where Reka models an\n * array. `min`, `max` and the emitted value all speak that one format.\n *\n * A value that does not parse — a half-typed string, an empty one, a\n * datetime — is read as *no date chosen* rather than thrown on. A component\n * library cannot decide that a host's bad data is fatal, and a date field that\n * crashes the page while someone types into the host's own text input beside\n * it is the worst possible reading of \"strict\".\n *\n * For a span rather than a single day, compose two of these — a range control\n * shares almost none of this one's model. For a month or a year alone, neither\n * this nor a Select is right; that is a control this library does not have yet.\n *\n * Inside a [Field](../Field/Field.vue) it wires itself: the row's id, the id of\n * its hint or error line, and `required` / `invalid` / `disabled` / `readonly` /\n * `name` all arrive through `useFieldControl()`, so `<Field label=\"Due date\"\n * error=\"…\"><DatePicker /></Field>` needs no attributes at the call site. Every\n * prop below still wins over the row when it is set, in both directions — which\n * is why the four booleans default to `undefined` rather than `false`.\n *\n * `readonly` and `disabled` are different states, not two dials on one, so the\n * field has three resting appearances rather than two. A read-only date is a\n * value on show: the field stays a Tab stop, its segments stay readable and\n * copyable at full strength, and it takes a lifted fill. A disabled one is\n * unavailable: no Tab stop, nothing submitted, and drained a step further in\n * fill, text colour and border weight together.\n */\nconst props = withDefaults(\n  defineProps<{\n    /**\n     * The chosen date as ISO `YYYY-MM-DD`. Unset, empty or unparseable means no\n     * date is chosen. The explicit `| undefined` is what lets `v-model` bind a\n     * ref that clears — the emitted value drops to `undefined` when the field\n     * is emptied, and a plain optional prop refuses to take it back.\n     */\n    modelValue?: string | undefined;\n    /** The earliest choosable date, same ISO format. Days before it are announced disabled and skipped by the keyboard. */\n    min?: string;\n    /** The latest choosable date, same ISO format. Days after it are announced disabled and skipped by the keyboard. */\n    max?: string;\n    /** BCP 47 tag driving the order of the field's segments, the month and weekday names, and which day a week starts on. */\n    locale?: string;\n    /** Unavailable: dims the control, refuses the calendar, and takes the field out of the tab order. Unset defers to a wrapping Field. */\n    disabled?: boolean | undefined;\n    /** Shows the date without allowing an edit: the field stays a Tab stop and stays submitted, and the calendar button is dropped because nothing in the calendar could be chosen. Unset defers to a wrapping Field. */\n    readonly?: boolean | undefined;\n    /** Error state: paints the destructive border and ring, and sets `aria-invalid`. Unset defers to a wrapping Field's `error`. */\n    invalid?: boolean | undefined;\n    /** Marks the field mandatory to assistive tech (`aria-required` on the segment group). Unset defers to a wrapping Field. */\n    required?: boolean | undefined;\n    /** The field name for a native form post or `FormData`, carried on the hidden input Reka submits the date through. Unset defers to a wrapping Field. */\n    name?: string;\n    /**\n     * Names for everything this control says out loud, as any subset of\n     * `DatePickerLabels` — the rest stay as the host's `provideLoomLabels`\n     * vocabulary left them, and then as Loom's English.\n     *\n     * This is the per-instance correction, not the place to localise an\n     * application: six of the nine names replace English literals Reka UI\n     * writes of its own accord, and a language is set once with\n     * `provideLoomLabels`.\n     */\n    labels?: LabelOverrides<DatePickerLabels>;\n  }>(),\n  {\n    locale: \"en\",\n    // Not `false`, for any of the four — TextField.vue carries the full\n    // reasoning. `false` is a caller deciding this one control is fine,\n    // enabled or editable even though its row is not; absent is a caller\n    // saying nothing, and only `undefined` survives to mean that past Vue's\n    // absent-Boolean-casts-to-false rule.\n    disabled: undefined,\n    readonly: undefined,\n    invalid: undefined,\n    required: undefined,\n  },\n);\n\nconst emit = defineEmits<{\n  /** The chosen date as ISO `YYYY-MM-DD`, or `undefined` once the field has been cleared. */\n  \"update:modelValue\": [value: string | undefined];\n}>();\n\n// Two slots, one prop. `text` is the name everywhere else in the library, and\n// there is no single `text` here because there is no single slot: the segment\n// names and the popover's chrome are separate vocabularies with separate\n// registry entries, and naming them apart is what keeps a reader of the\n// template able to see which one a binding came from. The one `labels` prop\n// feeds both — a getter returning the intersection satisfies either half, and\n// the keys the other half does not know are ignored by `useLabels`' own return\n// type.\nconst segmentText = useLabels(\"dateSegments\", DATE_SEGMENT_LABELS, () => props.labels);\nconst panelText = useLabels(\"calendarPanel\", CALENDAR_PANEL_LABELS, () => props.labels);\n\n// Read through the ref on every call rather than resolved into a lookup table\n// once: a table built in `setup` freezes the first language and every later\n// switch silently does nothing. `undefined` for the parts this slice does not\n// name — the `literal` separators, which Reka renders `aria-hidden` and which\n// must stay unnamed.\nfunction segmentLabel(part: string): string | undefined {\n  return isDateSegmentPart(part) ? segmentText.value[part] : undefined;\n}\n\n// The companion to `segmentLabel`, and the reason it returns an object rather\n// than a string is in `emptySegmentValueText`: Reka's `aria-valuetext` is a\n// hard-coded \"Empty\" only while the segment holds nothing, so this replaces\n// that case and leaves the filled one — a number, and the locale's own month\n// name — exactly as Reka wrote it.\n//\n// The month is the exception. Reka writes `\"5 - May\"`, with the month name from\n// `Intl.DateTimeFormat` but the separator and order hard-coded. `filledMonth`\n// lets a host compose the string their language needs (Japanese `\"5月\"`,\n// Vietnamese `\"tháng 5\"`). The numeric month arrives from the parsed model value\n// rather than from the segment's displayed text, because `item.value` is the\n// locale-formatted display and may not contain a parseable number.\nfunction segmentValueText(\n  part: string,\n  value: string,\n  monthValue?: number,\n): { \"aria-valuetext\"?: string } {\n  const empty = emptySegmentValueText(part, value, segmentText.value.empty);\n  if (empty[\"aria-valuetext\"]) return empty;\n  if (part === \"month\" && monthValue !== undefined) {\n    return {\n      \"aria-valuetext\": segmentText.value.filledMonth({ value: monthValue, locale: props.locale }),\n    };\n  }\n  return {};\n}\n\n// `class` sizes the whole control, so it lands on the anchor — the element the\n// caller's `max-w-xs` has to reach, and the one the popover measures itself\n// against. Every other fallthrough attribute goes one level in, onto the\n// `role=\"group\"` field: `aria-label`, `aria-labelledby` and `aria-describedby`\n// name and describe the thing being entered, and a group is what a screen\n// reader announces that name on entering. Putting them on the anchor instead\n// would name a layout div nothing ever lands in.\ndefineOptions({ inheritAttrs: false });\nconst { attrs, rest: fieldAttrs } = useSplitAttrs();\n\n/**\n * The date segments are `<div role=\"spinbutton\" tabindex=\"0\">`, and\n * `<fieldset disabled>` reaches only `<input>`, `<button>`, `<select>` and\n * `<textarea>` — so the calendar trigger inside a disabled group went inert\n * while the segments beside it still typed a date on an arrow key. Measured in\n * jsdom: an empty `mm` segment became `8`.\n *\n * Read off the DOM rather than taken from the Field context, which publishes no\n * `disabled` on purpose — see `../../lib/ancestor-disabled.ts`.\n */\nconst anchor = useTemplateRef<{ $el?: Element }>(\"anchor\");\nconst groupDisabled = useAncestorDisabled(() => anchor.value?.$el);\n\n// `id` and `aria-describedby` reach this control as fallthrough attrs rather\n// than props, so they are read off `attrs` and handed in as this caller's own\n// values — a caller who sets either still beats the row, and the row's\n// description is merged into theirs rather than replacing it.\n//\n// `field.attrs` spreads onto `DatePickerField` **after** `fieldAttrs`, which is\n// the node those two were already landing on, and the position is the contract:\n// the bag has resolved the caller's own values already and drops every key that\n// resolved to nothing, so it can only add. Where each key ends up is Reka's\n// decision and worth knowing: `DateFieldRoot` declares `id` and `name` as props\n// and puts both on the visually-hidden `<input>` it submits the date through —\n// which is the element a `<label for>` can actually name, a `role=\"group\"` div\n// being unlabelable — while `aria-describedby`, `aria-required` and\n// `aria-invalid` are undeclared, fall through to `$attrs`, and land on the group\n// itself, where a screen reader announces them once on entering the field.\n//\n// The `:aria-invalid` binding that used to sit on the field is gone with it: an\n// individual attribute written after a `v-bind` wins, so keeping one would\n// overwrite the resolved value with the raw prop.\nconst field = useFieldControl(() => ({\n  id: attrs.id as string | undefined,\n  describedBy: attrs[\"aria-describedby\"] as string | undefined,\n  ariaLabelledby: attrs[\"aria-labelledby\"] as string | undefined,\n  name: props.name,\n  // The fieldset beats the prop in both directions, exactly as it does for the\n  // trigger button inside this very control.\n  disabled: groupDisabled.value ? true : props.disabled,\n  readonly: props.readonly,\n  invalid: props.invalid,\n  required: props.required,\n}));\n\n// `aria-labelledby` for the group, resolved against the row. A caller who passes\n// `aria-labelledby` as a fallthrough attr wins (it reaches this control's own\n// `ariaLabelledby` through `useFieldControl`). A caller who passes `aria-label`\n// wins too — `aria-labelledby` overrides `aria-label` in ARIA, so the row's\n// label must not appear when the caller named the control themselves. Otherwise,\n// the row's label (published by Field as `labelledBy`) is the accessible name.\nconst groupLabelledBy = computed(() =>\n  attrs[\"aria-label\"] || attrs[\"aria-labelledby\"] ? undefined : field.labelledBy,\n);\n\nfunction fromIso(value: string | undefined): DateValue | undefined {\n  if (!value) return undefined;\n  try {\n    return parseDate(value);\n  } catch {\n    return undefined;\n  }\n}\n\n// `toString()` already normalises to the Gregorian ISO form whatever calendar\n// the value carries — a locale such as `th-TH` makes Reka's own placeholder a\n// Buddhist date whose year reads 2569, and it still prints `2026-08-11`. What\n// `toCalendarDate` adds is dropping a time component before it can turn the\n// string into `2026-08-11T00:00:00`. `granularity=\"day\"` below is what makes\n// that unreachable today; this is what keeps it unreachable if it ever moves.\nfunction toIso(date: DateValue): string {\n  return toCalendarDate(date).toString();\n}\n\n// `optional()` rather than three separate bindings: an absent bound forwarded\n// as an explicit `undefined` is still a key Reka sees, and an absent\n// `modelValue` forwarded that way is what turns an uncontrolled field into a\n// permanently empty one. Dropping the key says what is true.\nconst rootValue = computed(() =>\n  optional({\n    modelValue: fromIso(props.modelValue),\n    minValue: fromIso(props.min),\n    maxValue: fromIso(props.max),\n  }),\n);\n\n// The panel's open state is owned here rather than left to Reka's\n// `closeOnSelect`, which closes by watching its *own* model value — and that\n// value only moves for a host that echoes the emitted date straight back down.\n// A host that validates before accepting one, or that binds nothing at all,\n// would pick a day and watch the calendar stay open over the field it just\n// filled. Closing on the choice itself does not depend on anyone answering.\nconst open = ref(false);\n\nfunction onDateChange(date: DateValue | undefined) {\n  open.value = false;\n  emit(\"update:modelValue\", date ? toIso(date) : undefined);\n}\n\n// Today is a state, and it may not be carried by the marker dot alone — a\n// reader who cannot see the dot gets `aria-current=\"date\"`, which is the one\n// attribute screen readers already announce for \"this is the current one\".\n// Reka publishes today only as a `data-` attribute and a slot prop, neither of\n// which can reach an attribute binding on the cell itself.\nfunction isDateToday(date: DateValue): boolean {\n  return isToday(date, getLocalTimeZone());\n}\n\n// The field is one Tab stop, not three. Reka leaves every segment tabbable,\n// which turns a single date into three stops a keyboard user has to walk\n// through — and the control everyone already knows, the browser's own date\n// input, is one stop with the arrow keys moving inside it. So a roving\n// tabindex names exactly one segment as the stop, and Reka's own\n// ArrowLeft/ArrowRight handling (and its auto-advance after a filled segment)\n// moves between them by calling `focus()` directly, which ignores tabindex\n// entirely and so keeps working untouched.\nconst focusedPart = ref<string>();\n\nfunction segmentTabIndex(part: string, segments: readonly { part: string }[]): number | undefined {\n  // A disabled field has no stop at all; returning `undefined` removes the\n  // attribute, which is exactly what Reka does for the same case. A read-only\n  // one keeps every stop it had — the value is on show and a reader still\n  // arrows across it to read it, which is the whole difference between the two\n  // states.\n  if (field.disabled || part === \"literal\") return undefined;\n  const editable = segments.filter((segment) => segment.part !== \"literal\");\n  // The remembered segment is dropped when a locale change takes it away —\n  // a field with no tab stop is unreachable, and `en` has no era segment that\n  // `ja-JP-u-ca-japanese` does.\n  const active =\n    focusedPart.value !== undefined &&\n    editable.some((segment) => segment.part === focusedPart.value)\n      ? focusedPart.value\n      : editable[0]?.part;\n  return part === active ? 0 : -1;\n}\n\n// The month/year heading names the grid, so the two are wired together rather\n// than the grid being an unnamed table of numbers.\nconst headingId = useId();\n\nconst panel = ref<HTMLElement | null>(null);\n\n// Reka's focus scope would land on the first tabbable thing in the panel,\n// which is the previous-month button — so a keyboard user opening the calendar\n// arrives one Tab away from the grid and two from the day they came for.\n// Focus goes to the day the calendar is already sitting on instead: the\n// selected date, or today when nothing is selected, which is the cell Reka has\n// given the grid's own roving tabindex to.\nfunction onOpenAutoFocus(event: Event) {\n  const day = panel.value?.querySelector<HTMLElement>(\n    '[data-reka-calendar-cell-trigger][tabindex=\"0\"]',\n  );\n  if (!day) return;\n  event.preventDefault();\n  day.focus();\n}\n</script>\n\n<template>\n  <DatePickerRoot\n    v-model:open=\"open\"\n    v-bind=\"rootValue\"\n    :locale=\"locale\"\n    :disabled=\"field.disabled\"\n    :readonly=\"field.readonly\"\n    granularity=\"day\"\n    prevent-deselect\n    @update:model-value=\"onDateChange\"\n  >\n    <!-- The invalid marker lives out here, on the control as a whole, because\n         the field group below already carries a `data-invalid` of Reka's own\n         with a different meaning: that the *typed* date falls outside `min` and\n         `max`. Two markers spelled the same on one element is how a style rule\n         starts answering a question nobody asked it. -->\n    <DatePickerAnchor\n      ref=\"anchor\"\n      :data-invalid=\"field.invalid || undefined\"\n      :data-readonly=\"field.readonly || undefined\"\n      :class=\"cn('block w-full', attrs.class as string)\"\n    >\n      <DatePickerField\n        v-slot=\"{ segments }\"\n        v-bind=\"{ ...fieldAttrs, ...field.attrs }\"\n        :aria-labelledby=\"groupLabelledBy\"\n        :class=\"\n          cn(\n            // The text input's own height scale, so a date sitting in a form\n            // row beside a text field lines up rather than nearly lining up.\n            // No gap: the separator between two segments is itself a segment,\n            // so spacing them apart writes the date as `3 / 14 / 2026`.\n            'flex h-9 w-full items-center rounded-md border border-input bg-background px-3 text-sm text-foreground',\n            'transition-[color,background-color,border-color,box-shadow] duration-fast ease-out',\n            // The box carries the ring, exactly as TextField's wrapper does,\n            // and the focused segment below carries a fill instead of a second\n            // outline — a ring drawn inside a ring reads as a rendering fault.\n            'focus-within:outline-2 focus-within:outline-offset-2 focus-within:outline-ring',\n            !field.invalid && 'focus-within:shadow-halo',\n            // Three resting appearances, and every one of them belongs to this\n            // group rather than to the segments inside it. A fill painted per\n            // segment leaves the literal separators between them on\n            // `background`, and the control comes out striped.\n            //\n            // Read-only keeps its focus ring and its full-strength text: a\n            // read-only date is a value on show, not an unavailable control,\n            // and the two must not look alike. The fill lifts off `background`\n            // to `subtle`, which holds the segments at 13.46:1, and the rim\n            // stays `input` because nothing about the field's reach has moved —\n            // it is still a Tab stop and still submitted. Reka's own\n            // `data-readonly` on this group carries the same state to assistive\n            // tech, so nothing here rests on colour.\n            field.readonly && 'bg-subtle',\n            // Unavailable is a *colour* and a *weight*, never an opacity.\n            // `opacity-50` here faded the segments along with the box, and the\n            // segments are the whole content of the control: `--color-foreground`\n            // measures 14.09:1 on the resting fill and 2.99:1 once composited at\n            // half alpha, with the literal separators and any placeholder\n            // segment down at 2.02:1. The fill drains one step past read-only,\n            // the text follows it to a measured 4.68:1, and the rim slackens\n            // from `input` to `border` — so the two unavailable-looking states\n            // part on three channels rather than on hue alone, which is what a\n            // reader who cannot separate two greys has to have.\n            //\n            // The colour is set here rather than on each segment because no\n            // segment declares one of its own in the resting state, so each\n            // inherits this; `focus:text-primary-text` below is unreachable on a\n            // control that cannot take focus.\n            field.disabled && 'cursor-not-allowed border-border bg-muted text-muted-foreground',\n            // Last of the rules that name a border colour, and the order is\n            // load-bearing: `cn()` resolves a border colour by whichever class\n            // it saw last, so a field that is both in error and unavailable\n            // would otherwise lose its destructive rim to the disabled one.\n            field.invalid && 'border-destructive focus-within:outline-destructive',\n          )\n        \"\n      >\n        <!-- Every `:aria-label` from here down replaces one Reka writes in\n             English inside its own render function. Each reaches the DOM node\n             as a fallthrough attribute, which Vue merges last, so it is a\n             replacement rather than a second name. Removing one does not fall\n             back to nothing; it falls back to Reka's English, which is the\n             failure the label seam exists to close and which no test of Loom's\n             own strings would catch. -->\n        <DatePickerInput\n          v-for=\"(item, index) in segments\"\n          :key=\"index\"\n          :part=\"item.part\"\n          :tabindex=\"segmentTabIndex(item.part, segments)\"\n          :aria-label=\"segmentLabel(item.part)\"\n          v-bind=\"segmentValueText(item.part, item.value, fromIso(props.modelValue)?.month)\"\n          :class=\"\n            cn(\n              'tabular rounded-sm px-0.5 outline-none',\n              'transition-colors duration-instant ease-out',\n              'focus:bg-primary-muted focus:text-primary-text',\n              'data-[placeholder]:text-muted-foreground',\n              item.part === 'literal' && 'text-muted-foreground',\n            )\n          \"\n          @focusin=\"focusedPart = item.part\"\n        >\n          {{ item.value }}\n        </DatePickerInput>\n\n        <!-- Dropped entirely while read-only rather than disabled beside a\n             field that is plainly still alive. Reka's `readonly` reaches the\n             calendar too and makes every cell's click a no-op, so the button\n             would open a panel in which nothing can be chosen — a dead end that\n             looks like a working control, which is worse than not offering it.\n             The segments are still there to read the date off. -->\n        <DatePickerTrigger\n          v-if=\"!field.readonly\"\n          :aria-label=\"panelText.openCalendar\"\n          class=\"ml-auto inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring disabled:cursor-not-allowed\"\n        >\n          <CalendarDays class=\"h-4 w-4\" />\n        </DatePickerTrigger>\n      </DatePickerField>\n    </DatePickerAnchor>\n\n    <DatePickerContent\n      align=\"start\"\n      :side-offset=\"6\"\n      :class=\"\n        cn(\n          'z-overlay rounded-md border border-border bg-popover p-3 text-popover-foreground shadow-md outline-none',\n          // Both halves of the motion are scoped to their own state, never\n          // unconditional. Reka's Presence decides unmounting from the\n          // computed animation-name: an unconditional entrance left the closed\n          // panel computing a finished animation it would wait on forever — an\n          // invisible layer over the page, eating clicks. Scoped, closing\n          // swaps the computed animation to fade-fall's, and Presence holds\n          // the panel exactly one exit long, releasing it at animationend.\n          'data-[state=open]:animate-fade-rise data-[state=closed]:animate-fade-fall',\n        )\n      \"\n      @open-auto-focus=\"onOpenAutoFocus\"\n    >\n      <!-- The whole panel rises as one piece. The 42 cells deliberately carry\n           no stagger of their own: `listStaggerDelay` is the vocabulary for a\n           list of rows arriving in reading order, and a grid rippling in cell\n           by cell reads as a rendering glitch rather than as an entrance. -->\n      <div ref=\"panel\" class=\"flex flex-col gap-3\">\n        <!-- `calendarLabel` is a real Reka prop rather than a literal to\n             override, and it defaults to `\"Event Date\"` — a name for somebody\n             else's application. It is published twice: as the calendar\n             container's `aria-label`, and inside a visually-hidden live region\n             Reka renders itself, which a fallthrough attribute could not have\n             reached. -->\n        <DatePickerCalendar v-slot=\"{ grid, weekDays }\" :calendar-label=\"panelText.calendar\">\n          <DatePickerHeader class=\"flex items-center justify-between gap-2\">\n            <!-- The two pagers keep `data-[disabled]:opacity-50` where the\n                 field and the cells gave it up, and the difference is what is\n                 inside them: a chevron and nothing else. Fading a glyph costs a\n                 reader nothing, and the buttons carry their name in\n                 `aria-label` rather than in dimmed text. -->\n            <DatePickerPrev\n              :aria-label=\"panelText.previousMonth\"\n              class=\"inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring data-[disabled]:pointer-events-none data-[disabled]:opacity-50\"\n            >\n              <ChevronLeft class=\"h-4 w-4\" />\n            </DatePickerPrev>\n\n            <!-- Paging the calendar changes nothing a reader is looking at\n                 except this line, and nothing moves focus — so without the\n                 live region the month silently becomes a different month. -->\n            <DatePickerHeading\n              :id=\"headingId\"\n              aria-live=\"polite\"\n              class=\"text-sm font-medium text-foreground\"\n            />\n\n            <DatePickerNext\n              :aria-label=\"panelText.nextMonth\"\n              class=\"inline-flex h-7 w-7 shrink-0 items-center justify-center rounded-sm text-muted-foreground transition-colors duration-fast ease-out hover:bg-subtle hover:text-foreground focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring data-[disabled]:pointer-events-none data-[disabled]:opacity-50\"\n            >\n              <ChevronRight class=\"h-4 w-4\" />\n            </DatePickerNext>\n          </DatePickerHeader>\n\n          <DatePickerGrid\n            v-for=\"month in grid\"\n            :key=\"month.value.toString()\"\n            role=\"grid\"\n            :aria-labelledby=\"headingId\"\n            class=\"border-collapse select-none\"\n          >\n            <!-- Reka renders `role=\"application\"` here, which hands every key\n                 straight to the page and takes the table's own semantics away\n                 with it. A calendar is a grid: `role=\"grid\"` is what makes the\n                 cells rows and columns to a screen reader rather than 42\n                 unrelated buttons, and the arrow-key handling Reka installs on\n                 the cells is what a grid promises anyway.\n\n                 The rows and cells below are laid out by the table itself\n                 rather than by flex, and that is load-bearing: `display: flex`\n                 on a `tr` drops its implicit `row` mapping in Chromium and\n                 WebKit, which leaves `role=\"gridcell\"` inside a grid with no\n                 row between them — a broken grid that looks identical. -->\n            <DatePickerGridHead>\n              <DatePickerGridRow>\n                <DatePickerHeadCell\n                  v-for=\"(day, index) in weekDays\"\n                  :key=\"index\"\n                  class=\"w-9 text-xs font-normal text-muted-foreground\"\n                >\n                  {{ day }}\n                </DatePickerHeadCell>\n              </DatePickerGridRow>\n            </DatePickerGridHead>\n\n            <DatePickerGridBody>\n              <DatePickerGridRow v-for=\"(week, weekIndex) in month.rows\" :key=\"weekIndex\">\n                <DatePickerCell\n                  v-for=\"day in week\"\n                  :key=\"day.toString()\"\n                  :date=\"day\"\n                  class=\"p-0 text-center\"\n                >\n                  <!-- A day out of `min`/`max` range is drawn in colour rather\n                       than faded: the number is the cell's whole content, and\n                       `opacity-50` took `--color-foreground` from 14.09:1 on\n                       the popover to 3.13:1. Muted is 5.76:1 and the rule is\n                       written as `:not([data-selected])` so it can never order\n                       against the selected fill's own text colour — the same\n                       trick the range pickers use on their four competing\n                       fills. The strike is the second, hueless cue, and it is\n                       what keeps an unavailable day apart from an adjacent\n                       month's, which is muted too and still selectable. -->\n                  <DatePickerCellTrigger\n                    v-slot=\"{ dayValue, today }\"\n                    :day=\"day\"\n                    :month=\"month.value\"\n                    :aria-current=\"isDateToday(day) ? 'date' : undefined\"\n                    class=\"group relative inline-flex h-9 w-9 items-center justify-center rounded-sm text-sm text-foreground transition-colors duration-fast ease-out hover:bg-subtle focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-ring focus-visible:shadow-halo data-[outside-view]:text-muted-foreground data-[selected]:bg-primary data-[selected]:text-primary-foreground data-[disabled]:pointer-events-none data-[disabled]:line-through [&[data-disabled]:not([data-selected])]:text-muted-foreground\"\n                  >\n                    {{ dayValue }}\n                    <!-- Today's second cue. The dot is decoration to a screen\n                         reader — `aria-current` on the cell is what it reads —\n                         but it is the whole cue for a reader who is looking at\n                         the grid, and it is a shape rather than a hue so it\n                         survives a colour deficiency and forced-colors both. -->\n                    <span\n                      v-if=\"today\"\n                      aria-hidden=\"true\"\n                      class=\"absolute bottom-1 h-1 w-1 rounded-full bg-primary group-data-[selected]:bg-primary-foreground\"\n                    />\n                  </DatePickerCellTrigger>\n                </DatePickerCell>\n              </DatePickerGridRow>\n            </DatePickerGridBody>\n          </DatePickerGrid>\n        </DatePickerCalendar>\n      </div>\n    </DatePickerContent>\n  </DatePickerRoot>\n</template>\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAgHA,MAAM,QAAQ;EAmDd,MAAM,OAAO;EAab,MAAM,cAAc,UAAU,gBAAgB,2BAA2B,MAAM,MAAM;EACrF,MAAM,YAAY,UAAU,iBAAiB,6BAA6B,MAAM,MAAM;EAOtF,SAAS,aAAa,MAAkC;GACtD,OAAO,kBAAkB,IAAI,IAAI,YAAY,MAAM,QAAQ,KAAA;EAC7D;EAcA,SAAS,iBACP,MACA,OACA,YAC+B;GAC/B,MAAM,QAAQ,sBAAsB,MAAM,OAAO,YAAY,MAAM,KAAK;GACxE,IAAI,MAAM,mBAAmB,OAAO;GACpC,IAAI,SAAS,WAAW,eAAe,KAAA,GACrC,OAAO,EACL,kBAAkB,YAAY,MAAM,YAAY;IAAE,OAAO;IAAY,QAAQ,MAAM;GAAO,CAAC,EAC7F;GAEF,OAAO,CAAC;EACV;EAUA,MAAM,EAAE,OAAO,MAAM,eAAe,cAAc;;;;;;;;;;;EAYlD,MAAM,SAAS,eAAkC,QAAQ;EACzD,MAAM,gBAAgB,0BAA0B,OAAO,OAAO,GAAG;EAqBjE,MAAM,QAAQ,uBAAuB;GACnC,IAAI,MAAM;GACV,aAAa,MAAM;GACnB,gBAAgB,MAAM;GACtB,MAAM,MAAM;GAGZ,UAAU,cAAc,QAAQ,OAAO,MAAM;GAC7C,UAAU,MAAM;GAChB,SAAS,MAAM;GACf,UAAU,MAAM;EAClB,EAAE;EAQF,MAAM,kBAAkB,eACtB,MAAM,iBAAiB,MAAM,qBAAqB,KAAA,IAAY,MAAM,UACtE;EAEA,SAAS,QAAQ,OAAkD;GACjE,IAAI,CAAC,OAAO,OAAO,KAAA;GACnB,IAAI;IACF,OAAO,yCAAU,KAAK;GACxB,QAAQ;IACN;GACF;EACF;EAQA,SAAS,MAAM,MAAyB;GACtC,OAAO,0CAAe,IAAI,CAAC,CAAC,SAAS;EACvC;EAMA,MAAM,YAAY,eAChB,SAAS;GACP,YAAY,QAAQ,MAAM,UAAU;GACpC,UAAU,QAAQ,MAAM,GAAG;GAC3B,UAAU,QAAQ,MAAM,GAAG;EAC7B,CAAC,CACH;EAQA,MAAM,OAAO,IAAI,KAAK;EAEtB,SAAS,aAAa,MAA6B;GACjD,KAAK,QAAQ;GACb,KAAK,qBAAqB,OAAO,MAAM,IAAI,IAAI,KAAA,CAAS;EAC1D;EAOA,SAAS,YAAY,MAA0B;GAC7C,OAAO,0CAAQ,MAAM,0CAAiB,CAAC;EACzC;EAUA,MAAM,cAAc,IAAY;EAEhC,SAAS,gBAAgB,MAAc,UAA2D;GAMhG,IAAI,MAAM,YAAY,SAAS,WAAW,OAAO,KAAA;GACjD,MAAM,WAAW,SAAS,QAAQ,YAAY,QAAQ,SAAS,SAAS;GASxE,OAAO,UAJL,YAAY,UAAU,KAAA,KACtB,SAAS,MAAM,YAAY,QAAQ,SAAS,YAAY,KAAK,IACzD,YAAY,QACZ,SAAS,EAAE,EAAE,QACM,IAAI;EAC/B;EAIA,MAAM,YAAY,MAAM;EAExB,MAAM,QAAQ,IAAwB,IAAI;EAQ1C,SAAS,gBAAgB,OAAc;GACrC,MAAM,MAAM,MAAM,OAAO,cACvB,mDACF;GACA,IAAI,CAAC,KAAK;GACV,MAAM,eAAe;GACrB,IAAI,MAAM;EACZ;;GAIE,OAAA,UAAA,GAAA,YA+PiB,MAAA,cAAA,GA/PjB,WA+PiB;IA9PP,MAAM,KAAA;IAAA,iBAAA,OAAA,OAAA,OAAA,MAAA,WAAA,KAAI,QAAA;GACV,GAAA,UAAA,OAAS;IAChB,QAAQ,QAAA;IACR,UAAU,MAAA,KAAA,CAAK,CAAC;IAChB,UAAU,MAAA,KAAA,CAAK,CAAC;IACjB,aAAY;IACZ,oBAAA;IACC,uBAAoB;;IAOrB,SAAA,cAuGmB,CAvGnB,YAuGmB,MAAA,gBAAA,GAAA;KAtGb,SAAA;KAAJ,KAAI;KACH,gBAAc,MAAA,KAAA,CAAK,CAAC,WAAW,KAAA;KAC/B,iBAAe,MAAA,KAAA,CAAK,CAAC,YAAY,KAAA;KACjC,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,gBAAiB,MAAA,KAAA,CAAK,CAAC,KAAK,CAAA;;KAEtC,SAAA,cAgGkB,CAhGlB,YAgGkB,MAAA,eAAA,GAhGlB,WAgGkB;MAAA,GA9FH,MAAA,UAAA;MAAU,GAAK,MAAA,KAAA,CAAK,CAAC;KAAK,GAAA;MACtC,mBAAiB,gBAAA;MACjB,OAAkB,MAAA,EAAA,CAAE,CAAA,0GAAA,sFAAA,kFAAu2B,CAAA,MAAA,KAAA,CAAK,CAAC,WAAO,4BAAo7B,MAAA,KAAA,CAAK,CAAC,YAAQ,aAAilC,MAAA,KAAA,CAAK,CAAC,YAAQ,mEAA0Y,MAAA,KAAA,CAAK,CAAC,WAAO,qDAAA;;MA2D/zG,SAAA,SAAiC,EA9DzB,eAAQ,EA6DlB,UAAA,IAAA,GAAA,mBAmBkB,UAAA,MAAA,WAlBQ,WAAhB,MAAM,UAAK;OADrB,OAAA,UAAA,GAAA,YAmBkB,MAAA,eAAA,GAnBlB,WAmBkB;QAjBf,KAAK;QACL,MAAM,KAAK;QACX,UAAU,gBAAgB,KAAK,MAAM,QAAQ;QAC7C,cAAY,aAAa,KAAK,IAAI;OAC3B,GAAA,EAAA,SAAA,KAAA,GAAA,iBAAiB,KAAK,MAAM,KAAK,OAAO,QAAQ,MAAM,UAAU,CAAA,EAAG,KAAK,GAAA;QAC/E,OAAoB,MAAA,EAAA,CAAE,CAAA,0CAAA,+CAAA,kDAAA,4CAA+P,KAAK,SAAI,aAAA,uBAAA;QAS9R,YAAO,WAAE,YAAA,QAAc,KAAK;;QAE7B,SAAA,cAAgB,CAAb,gBAAA,gBAAA,KAAK,KAAK,GAAA,CAAA,CAAA,CAAA;;;;;;;;;MAUN,CAAA,GAAA,GAAA,IAAA,CAAA,MAAA,KAAA,CAAK,CAAC,YADf,UAAA,GAAA,YAMoB,MAAA,iBAAA,GAAA;;OAJjB,cAAY,MAAA,SAAA,CAAS,CAAC;OACvB,OAAM;;OAEN,SAAA,cAAgC,CAAhC,YAAgC,MAAA,YAAA,GAAA,EAAlB,OAAM,UAAS,CAAA,CAAA,CAAA;;;;;;;;;;IAKnC,CAAA,GAAA,YAsIoB,MAAA,iBAAA,GAAA;KArIlB,OAAM;KACL,eAAa;KACb,OAAK,eAAW,MAAA,EAAA,CAAE,CAAA,2GAAA,2EAAA,CAAA;KAaD;;KAMlB,SAAA,cA+GM,CA/GN,mBA+GM,OAAA;MA/GG,SAAA;MAAJ,KAAI;MAAQ,OAAM;KAOrB,GAAA,CAAA,YAuGqB,MAAA,kBAAA,GAAA,EAvG4B,kBAAgB,MAAA,SAAA,CAAS,CAAC,SAAA,GAAA;MACzE,SAAA,SA4BmB,EA7BS,MAAM,eAAQ,CAC1C,YA4BmB,MAAA,gBAAA,GAAA,EA5BD,OAAM,0CAAyC,GAAA;OAM/D,SAAA,cAKiB;QALjB,YAKiB,MAAA,cAAA,GAAA;SAJd,cAAY,MAAA,SAAA,CAAS,CAAC;SACvB,OAAM;;SAEN,SAAA,cAA+B,CAA/B,YAA+B,MAAA,WAAA,GAAA,EAAlB,OAAM,UAAS,CAAA,CAAA,CAAA;;;QAM9B,YAIE,MAAA,iBAAA,GAAA;SAHC,IAAI,MAAA,SAAA;SACL,aAAU;SACV,OAAM;;QAGR,YAKiB,MAAA,cAAA,GAAA;SAJd,cAAY,MAAA,SAAA,CAAS,CAAC;SACvB,OAAM;;SAEN,SAAA,cAAgC,CAAhC,YAAgC,MAAA,YAAA,GAAA,EAAlB,OAAM,UAAS,CAAA,CAAA,CAAA;;;;;MAIjC,CAAA,IAAA,UAAA,IAAA,GAAA,mBAuEiB,UAAA,MAAA,WAtEC,OAAT,UAAK;OADd,OAAA,UAAA,GAAA,YAuEiB,MAAA,cAAA,GAAA;QArEd,KAAK,MAAM,MAAM,SAAQ;QAC1B,MAAK;QACJ,mBAAiB,MAAA,SAAA;QAClB,OAAM;;QAcN,SAAA,cAUqB,CAVrB,YAUqB,MAAA,kBAAA,GAAA,MAAA;SATnB,SAAA,cAQoB,CARpB,YAQoB,MAAA,iBAAA,GAAA,MAAA;UANhB,SAAA,cAAgC,EADlC,UAAA,IAAA,GAAA,mBAMqB,UAAA,MAAA,WALI,WAAf,KAAK,UAAK;WADpB,OAAA,UAAA,GAAA,YAMqB,MAAA,kBAAA,GAAA;YAJlB,KAAK;YACN,OAAM;;YAEN,SAAA,cAAS,CAAN,gBAAA,gBAAA,GAAG,GAAA,CAAA,CAAA,CAAA;;;;;;;QAKZ,GAAA,IAAA,GAAA,YAuCqB,MAAA,kBAAA,GAAA,MAAA;SAtCA,SAAA,cAAuC,EAA1D,UAAA,IAAA,GAAA,mBAqCoB,UAAA,MAAA,WArC2B,MAAM,OAA1B,MAAM,cAAS;UAA1C,OAAA,UAAA,GAAA,YAqCoB,MAAA,iBAAA,GAAA,EArCwC,KAAK,UAAS,GAAA;WAEtE,SAAA,cAAmB,EADrB,UAAA,IAAA,GAAA,mBAmCiB,UAAA,MAAA,WAlCD,OAAP,QAAG;YADZ,OAAA,UAAA,GAAA,YAmCiB,MAAA,cAAA,GAAA;aAjCd,KAAK,IAAI,SAAQ;aACjB,MAAM;aACP,OAAM;;aAYN,SAAA,cAkBwB,CAlBxB,YAkBwB,MAAA,qBAAA,GAAA;cAhBhB;cACL,OAAO,MAAM;cACb,gBAAc,YAAY,GAAG,IAAA,SAAa,KAAA;cAC3C,OAAM;;cAEN,SAAA,SAAc,EANJ,UAAU,YAAK,CAMtB,gBAAA,gBAAA,QAAQ,IAAG,KAMd,CAAA,GACQ,SADR,UAAA,GAAA,mBAIE,QAJF,UAIE,KAAA,mBAAA,IAAA,IAAA,CAAA,CAAA"}

package/dist/packages/primitives/date-picker/src/index.d.ts

@@ -0,0 +1,3 @@
+export { default } from "./DatePicker.vue";
+export type { DatePickerLabels } from "./DatePicker.vue";
+//# sourceMappingURL=index.d.ts.map

package/dist/packages/primitives/date-picker/src/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../packages/primitives/date-picker/src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,kBAAkB,CAAC;AAC3C,YAAY,EAAE,gBAAgB,EAAE,MAAM,kBAAkB,CAAC"}

package/dist/packages/primitives/date-picker/src/index.js

@@ -0,0 +1,2 @@
+import DatePicker_default from "./DatePicker.js";
+export { DatePicker_default as default };

package/dist/packages/primitives/date-range-picker/src/DateRangePicker.js

@@ -0,0 +1,7 @@
+import DateRangePicker_vue_vue_type_script_setup_true_lang_default, { DATE_RANGE_LABELS } from "./DateRangePicker.vue_vue_type_script_setup_true_lang.js";
+//#region packages/primitives/date-range-picker/src/DateRangePicker.vue
+var DateRangePicker_default = DateRangePicker_vue_vue_type_script_setup_true_lang_default;
+//#endregion
+export { DATE_RANGE_LABELS, DateRangePicker_default as default };
+
+//# sourceMappingURL=DateRangePicker.js.map