@scalewing/react 1.19.0 → 1.21.0

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @scalewing/react
 
+## 1.21.0
+
+### Minor Changes
+
+- 2d54950: `DateField` and `CalendarButton` take an optional `today` (`YYYY-MM-DD`): the day the calendar marks as today (`aria-current="date"`), opens on when the field is empty, and picks with **Today**. It defaults to the device's local date, as before. Pass the business's own day when it keeps a time zone the device may not share, so a phone in UTC at 10 PM in New York no longer rings tomorrow while `max` disables it. An empty or malformed `today` throws a `RangeError`.
+
+## 1.20.0
+
+### Minor Changes
+
+- cfcac1a: `Tooltip` `relationship` (`docs/requests/teisoro-tooltip-labels.md`, Teisoro's workspace navigation). `relationship?: 'description' | 'label'`, default `'description'`, and the exported type `TooltipRelationship`. `'label'` makes the tooltip its trigger's accessible name: the trigger gets `aria-labelledby` with the tooltip's id (after its own, if any) instead of `aria-describedby`, so an icon-only control's name is read once rather than as both name and description. The tooltip stays in the page, hidden, so it names the trigger while not shown. With `disabled` there is no tooltip and no reference to it; the trigger then needs its own name (visible text or `aria-label`). Without `relationship` the markup and behavior are unchanged. No new classes, tokens or dependencies.
+
 ## 1.19.0
 
 ### Minor Changes

package/README.md

@@ -247,7 +247,7 @@ An option's optional `description` (a `ReactNode`) is secondary text for that op
 
 `Progress` shows a known value between zero and a positive maximum. It uses native progressbar semantics and displays the value and maximum beside the localized label. Invalid bounds throw instead of silently clamping. Optional `tone` is `accent`, `success`, or `danger`. `showCount={false}` hides the visible `value / max` count when the page shows its own count caption, so the count appears once; the progress bar still exposes its value and maximum.
 
-`Tooltip` adds supplementary plain-text help to one labelled, focusable trigger. Supply localized `content` and an existing trigger element with its own accessible name. It opens on hover or focus, closes on pointer leave, blur, Escape, or outside touch, and toggles on touch. Keep required instructions visible outside the tooltip. `disabled` turns the tooltip off, not its trigger: the trigger stays mounted, enabled and focusable, and there is no tooltip, no `aria-describedby` from it, and Escape is left to the page. Use it when what the tooltip says is visible at some widths, such as text shown only from `md` up, instead of rendering the trigger with and without a `Tooltip`, which mounts a new trigger and drops its focus. Focus, hover and touch are still followed, so a trigger that still has focus, the pointer or an open touch toggle shows the tooltip as soon as it is enabled again (Escape pressed while disabled reaches the page and does not stop that). `disabled` must be the same in the server render and the first client render, or hydration mismatches; read a breakpoint through a hydration-safe store, such as `useSyncExternalStore` with a server snapshot.
+`Tooltip` adds supplementary plain-text help to one labelled, focusable trigger, or names an icon-only one (`relationship="label"`, below). Supply localized `content` and an existing trigger element; by default it has its own accessible name. It opens on hover or focus, closes on pointer leave, blur, Escape, or outside touch, and toggles on touch. Keep required instructions visible outside the tooltip. `disabled` turns the tooltip off, not its trigger: the trigger stays mounted, enabled and focusable, and there is no tooltip, no `aria-describedby` from it, and Escape is left to the page. Use it when what the tooltip says is visible at some widths, such as text shown only from `md` up, instead of rendering the trigger with and without a `Tooltip`, which mounts a new trigger and drops its focus. Focus, hover and touch are still followed, so a trigger that still has focus, the pointer or an open touch toggle shows the tooltip as soon as it is enabled again (Escape pressed while disabled reaches the page and does not stop that). `disabled` must be the same in the server render and the first client render, or hydration mismatches; read a breakpoint through a hydration-safe store, such as `useSyncExternalStore` with a server snapshot. `relationship="label"` makes the tooltip its trigger's name instead of its description, for an icon-only control whose tooltip says what it is: the trigger gets `aria-labelledby` (after its own, if any) and no `aria-describedby` from the tooltip, so the text is read once. The tooltip stays in the page, hidden, so it names the trigger while it is not shown, and it wins over an `aria-label`. While `disabled` there is no tooltip to name the trigger, so give the trigger its own name for that state: visible text, such as a label shown only from `md` up, or an `aria-label`. Do not use `relationship="label"` while the trigger shows visible text that differs from `content`: the tooltip would replace that visible label as the name (WCAG 2.5.3, label in name). The default, `relationship="description"`, is the supplementary help above. `relationship` must also be the same in the server render and the first client render.
 
 `Separator` divides sections with a token-colored line. It is horizontal by default; use `orientation="vertical"` in a flex row. Set `decorative` when the line only supports layout so assistive technology ignores it.
 
@@ -291,7 +291,7 @@ Values outside the catalog throw a `RangeError`. There is no per-breakpoint span
 
 `DateField` is a controlled date-only field that draws its own calendar. Supply `value`, `min`, and `max` as valid `YYYY-MM-DD` dates; use an empty `value` for a blank field. Its callback returns a date-only string or an empty string, without timezone conversion. Invalid serialized dates and inverted bounds throw; a value outside the bounds remains visible with invalid styling. `required` marks the label with the same `aria-hidden` asterisk as `Field` and sets the entry's native `required`. Its label is drawn as `Field`'s (the same label words and mark inside a `<label>` that keeps the canvas type), so its label row and its gap to the entry match a `Field` beside it. For a blank required field, supply `error` when form validation runs to show the message and invalid styling.
 
-People type the date into a text entry in the locale's numeric order (`MM/DD/YYYY` for en-US, `DD/MM/YYYY` for es), with any non-digit separator, eight bare digits, or ISO `YYYY-MM-DD`. A keystroke calls `onChange` once the entry is complete, meaning its last field is at full width (four year digits, or two digits for a trailing day or month, as in ISO); otherwise the date commits when the person leaves the field or presses Enter, so typing `2024-03-10` never sends `2024-03-01` on the way. If the parent keeps the old value, the typed text stays on screen; any other outside change replaces it. Text that is not a date keeps the last value and, once the person leaves the field, sets `aria-invalid` and shows `labels.invalidEntry`. Like the native date input, the entry blocks form submission through `setCustomValidity`: `labels.invalidEntry` while its text is not a date, and `labels.outOfRange` while its date, typed or given, is outside `min`/`max`. The calendar button beside it opens a WAI-ARIA date picker dialog anchored under the field on the popover layer: the month grid shows today, the selected day, and days outside `min`/`max` as `aria-disabled` (padding before `0001-01-01` or after `9999-12-31` is blank and inert); arrows move by day and week, Home and End to the week's edges, PageUp and PageDown by month, Shift with them by year, Enter or Space selects and closes, and Escape closes and returns focus to the button. Month and year selectors in the header jump decades (the year list spans 120 years back and 20 ahead of today and the shown month, cut to `min` and `max`; the month list offers only months with a day inside them). A new `value`, `min`, or `max` while the calendar is open moves it to the new value or back inside the bounds. **Today** selects today; **Clear** appears only when the field is not `required`.
+People type the date into a text entry in the locale's numeric order (`MM/DD/YYYY` for en-US, `DD/MM/YYYY` for es), with any non-digit separator, eight bare digits, or ISO `YYYY-MM-DD`. A keystroke calls `onChange` once the entry is complete, meaning its last field is at full width (four year digits, or two digits for a trailing day or month, as in ISO); otherwise the date commits when the person leaves the field or presses Enter, so typing `2024-03-10` never sends `2024-03-01` on the way. If the parent keeps the old value, the typed text stays on screen; any other outside change replaces it. Text that is not a date keeps the last value and, once the person leaves the field, sets `aria-invalid` and shows `labels.invalidEntry`. Like the native date input, the entry blocks form submission through `setCustomValidity`: `labels.invalidEntry` while its text is not a date, and `labels.outOfRange` while its date, typed or given, is outside `min`/`max`. The calendar button beside it opens a WAI-ARIA date picker dialog anchored under the field on the popover layer: the month grid shows today, the selected day, and days outside `min`/`max` as `aria-disabled` (padding before `0001-01-01` or after `9999-12-31` is blank and inert); arrows move by day and week, Home and End to the week's edges, PageUp and PageDown by month, Shift with them by year, Enter or Space selects and closes, and Escape closes and returns focus to the button. Month and year selectors in the header jump decades (the year list spans 120 years back and 20 ahead of today and the shown month, cut to `min` and `max`; the month list offers only months with a day inside them). A new `value`, `min`, or `max` while the calendar is open moves it to the new value or back inside the bounds. **Today** selects today; **Clear** appears only when the field is not `required`. Today is the device's local date unless `today` (a `YYYY-MM-DD` date) is given: pass the business's own day when it keeps a time zone the device may not share, so a phone in another zone after the business's midnight does not mark tomorrow as today, open on it, or pick it while `max` is the business's day. `today` moves the today mark, the empty field's starting day, **Today**, and the year list's span; it may lie outside `min`/`max`, where **Today** is disabled as before. An empty or malformed `today` throws a `RangeError`.
 
 `locale` (BCP 47) sets month and weekday names, spoken dates, and the typed order; it defaults to the nearest `lang` attribute when the field mounts, then `en-US`, and a malformed tag throws. `weekStartsOn` is `0` (Sunday, the default) or `1` (Monday). `labels` overrides the control's own words, English by default: `chooseDate`, `previousMonth`, `nextMonth`, `month`, `year`, `today`, `clear`, `invalidEntry`, `outOfRange`, and the placeholder letters `dayPlaceholder`, `monthPlaceholder`, `yearPlaceholder`. The field label names only the text entry; the calendar button is named `labels.chooseDate` and described by the field label, so tests find the entry with `getByLabel` or `getByRole('textbox', { name })`.
 
@@ -314,7 +314,7 @@ People type the date into a text entry in the locale's numeric order (`MM/DD/YYY
 />
 ```
 
-`CalendarButton` is an icon-only `Button` that opens the same calendar dialog for a date the page already shows, such as a day heading with its own previous and next steps: `‹ Tuesday, September 22, 2026 [calendar] ›`. It has no text entry and no empty value. Supply `label` (what pressing it does, such as "Choose survey day"), a `YYYY-MM-DD` `value`, and `onChange`; optional `min`, `max`, `disabled`, `locale`, and `weekStartsOn` behave as on `DateField`, and `id` and a `ref` reach the `<button>`. `labels` takes the calendar's words (`previousMonth`, `nextMonth`, `month`, `year`, `today`) and `nameSeparator`. The button's accessible name is `label`, `labels.nameSeparator` (default `", "`), then the spoken date (`"Choose survey day, Tuesday, September 22, 2026"`); pass the locale's own pause where a comma does not fit, such as `"、"` in Japanese. It comes with `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls` while open; the calendar dialog is named by `label`. Enter, Space, or a press opens it on `value`. As on `DateField`, a `value` outside `min`/`max` is kept rather than refused, and the calendar then opens on the nearest allowed day with `value` shown selected and disabled; a button has no invalid state, so the page that shows the date flags it if it must. Choosing a day or **Today** calls `onChange` with the new date only when it changed, closes, and returns focus to the button; Escape closes without a change and returns focus; a press outside closes without a change and leaves focus where it landed. An empty or malformed `value`, `min`, or `max`, inverted bounds, a bad `locale` or `weekStartsOn`, an empty `label`, or an empty label word throws a `RangeError`. `size` (`xs`, `sm`, `md`; default `md`) and `variant` (default `ghost`) follow `Button`; the button is square at every size, and on a coarse pointer it is at least 44 px at every size. Place it beside the heading, not inside it, so the heading's text stays only the date.
+`CalendarButton` is an icon-only `Button` that opens the same calendar dialog for a date the page already shows, such as a day heading with its own previous and next steps: `‹ Tuesday, September 22, 2026 [calendar] ›`. It has no text entry and no empty value. Supply `label` (what pressing it does, such as "Choose survey day"), a `YYYY-MM-DD` `value`, and `onChange`; optional `min`, `max`, `today`, `disabled`, `locale`, and `weekStartsOn` behave as on `DateField`, and `id` and a `ref` reach the `<button>`. `labels` takes the calendar's words (`previousMonth`, `nextMonth`, `month`, `year`, `today`) and `nameSeparator`. The button's accessible name is `label`, `labels.nameSeparator` (default `", "`), then the spoken date (`"Choose survey day, Tuesday, September 22, 2026"`); pass the locale's own pause where a comma does not fit, such as `"、"` in Japanese. It comes with `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls` while open; the calendar dialog is named by `label`. Enter, Space, or a press opens it on `value`. As on `DateField`, a `value` outside `min`/`max` is kept rather than refused, and the calendar then opens on the nearest allowed day with `value` shown selected and disabled; a button has no invalid state, so the page that shows the date flags it if it must. Choosing a day or **Today** calls `onChange` with the new date only when it changed, closes, and returns focus to the button; Escape closes without a change and returns focus; a press outside closes without a change and leaves focus where it landed. An empty or malformed `value`, `min`, `max`, or `today`, inverted bounds, a bad `locale` or `weekStartsOn`, an empty `label`, or an empty label word throws a `RangeError`. `size` (`xs`, `sm`, `md`; default `md`) and `variant` (default `ghost`) follow `Button`; the button is square at every size, and on a coarse pointer it is at least 44 px at every size. Place it beside the heading, not inside it, so the heading's text stays only the date.
 
 ```tsx
 <Inline gap={1}>

package/dist/components/CalendarButton.d.ts

@@ -19,6 +19,12 @@ export type CalendarButtonProps = {
     onChange: (value: string) => void;
     min?: string;
     max?: string;
+    /**
+     * The calendar's today `YYYY-MM-DD`: the day it marks as today and picks
+     * with **Today**. Defaults to the device's local date; pass the business's
+     * day when it keeps its own time zone.
+     */
+    today?: string;
     disabled?: boolean;
     /** The `<button>` element's id. */
     id?: string;

package/dist/components/CalendarButton.js

@@ -26,7 +26,7 @@ function setForwardedRef(ref, node) {
  * date for something the page already shows, such as a day heading. It has
  * no text entry and no empty value. The ref reaches the `<button>`.
  */
-export const CalendarButton = forwardRef(function CalendarButton({ label, value, onChange, min, max, disabled = false, id, locale, weekStartsOn = 0, labels, size = 'md', variant = 'ghost', }, ref) {
+export const CalendarButton = forwardRef(function CalendarButton({ label, value, onChange, min, max, today, disabled = false, id, locale, weekStartsOn = 0, labels, size = 'md', variant = 'ghost', }, ref) {
     assertLabel(label);
     assertDateOnly('value', value);
     assertDateBounds(value, min, max);
@@ -36,6 +36,7 @@ export const CalendarButton = forwardRef(function CalendarButton({ label, value,
         value,
         disabled,
         onChange,
+        today,
     });
     const resolvedLocale = useLangLocale(locale, buttonRef);
     const labelId = useId();

package/dist/components/DateField.d.ts

@@ -9,6 +9,13 @@ export type DateFieldProps = {
     onChange: (value: string) => void;
     min?: string;
     max?: string;
+    /**
+     * The calendar's today `YYYY-MM-DD`: the day it marks as today, opens on
+     * when the field is empty, and picks with **Today**. Defaults to the
+     * device's local date; pass the business's day when it keeps its own
+     * time zone.
+     */
+    today?: string;
     disabled?: boolean;
     required?: boolean;
     description?: string;
@@ -23,4 +30,4 @@ export type DateFieldProps = {
     /** The control's own words; English by default. */
     labels?: Partial<DateFieldLabels>;
 };
-export declare function DateField({ label, value, onChange, min, max, disabled, required, description, error, locale, weekStartsOn, labels, }: DateFieldProps): import("react").JSX.Element;
+export declare function DateField({ label, value, onChange, min, max, today, disabled, required, description, error, locale, weekStartsOn, labels, }: DateFieldProps): import("react").JSX.Element;

package/dist/components/DateField.js

@@ -13,7 +13,7 @@ import { DateFieldGlyph } from './date-field/DateFieldGlyph.js';
 import { useCalendarPopup } from './date-field/use-calendar-popup.js';
 import { useDateEntry } from './date-field/use-date-entry.js';
 import { useLangLocale } from './date-field/use-lang-locale.js';
-export function DateField({ label, value, onChange, min, max, disabled = false, required = false, description, error, locale, weekStartsOn = 0, labels, }) {
+export function DateField({ label, value, onChange, min, max, today, disabled = false, required = false, description, error, locale, weekStartsOn = 0, labels, }) {
     assertDateBounds(value, min, max);
     assertWeekStart(weekStartsOn);
     const words = resolveDateFieldLabels(labels);
@@ -35,6 +35,7 @@ export function DateField({ label, value, onChange, min, max, disabled = false,
         value,
         disabled,
         onChange,
+        today,
         beforeSelect: entry.reset,
     });
     const inputId = useId();

package/dist/components/Tooltip.d.ts

@@ -1,4 +1,6 @@
 import { type ReactElement } from 'react';
+import { type TooltipRelationship, type TooltipTriggerAria } from './tooltip-trigger-aria.js';
+export type { TooltipRelationship };
 export type TooltipProps = {
     content: string;
     /**
@@ -11,8 +13,19 @@ export type TooltipProps = {
      * render and the first client render.
      */
     disabled?: boolean;
-    trigger: ReactElement<{
-        'aria-describedby'?: string;
-    }>;
+    /**
+     * `'description'` (default) adds supplementary help to a trigger that has
+     * its own name, through `aria-describedby`. `'label'` makes `content` the
+     * trigger's accessible name, through `aria-labelledby`, for an icon-only
+     * control: the text is read once, as its name. The tooltip stays in the
+     * DOM, hidden, so it names the trigger while it is not shown. While
+     * `disabled` there is no tooltip to name it, so the trigger then needs its
+     * own name: visible text, or an `aria-label` (which the tooltip overrides
+     * while enabled). The trigger's own `aria-labelledby` and `aria-describedby`
+     * are kept. It must match between the server render and the first client
+     * render.
+     */
+    relationship?: TooltipRelationship;
+    trigger: ReactElement<TooltipTriggerAria>;
 };
-export declare function Tooltip({ content, disabled, trigger }: TooltipProps): import("react").JSX.Element;
+export declare function Tooltip({ content, disabled, relationship, trigger, }: TooltipProps): import("react").JSX.Element;

package/dist/components/Tooltip.js

@@ -1,7 +1,8 @@
 'use client';
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 import { cloneElement, useEffect, useId, useRef, useState, } from 'react';
-export function Tooltip({ content, disabled = false, trigger }) {
+import { tooltipTriggerAria, } from './tooltip-trigger-aria.js';
+export function Tooltip({ content, disabled = false, relationship = 'description', trigger, }) {
     if (!content.trim())
         throw new RangeError('content must not be empty');
     // `open` follows focus, hover and touch even while disabled; `shown` is
@@ -10,9 +11,7 @@ export function Tooltip({ content, disabled = false, trigger }) {
     const shown = open && !disabled;
     const id = useId();
     const wrapperRef = useRef(null);
-    const describedBy = [trigger.props['aria-describedby'], disabled ? undefined : id]
-        .filter(Boolean)
-        .join(' ') || undefined;
+    const triggerAria = tooltipTriggerAria(trigger.props, disabled ? undefined : id, relationship);
     useEffect(() => {
         if (!open)
             return;
@@ -43,5 +42,5 @@ export function Tooltip({ content, disabled = false, trigger }) {
         }, onPointerDownCapture: (event) => {
             if (event.pointerType === 'touch')
                 setOpen((current) => !current);
-        }, ref: wrapperRef, children: [cloneElement(trigger, { 'aria-describedby': describedBy }), disabled ? null : (_jsx("span", { className: "sw-tooltip", hidden: !shown, id: id, role: "tooltip", children: content }))] }));
+        }, ref: wrapperRef, children: [cloneElement(trigger, triggerAria), disabled ? null : (_jsx("span", { className: "sw-tooltip", hidden: !shown, id: id, role: "tooltip", children: content }))] }));
 }

package/dist/components/date-field/use-calendar-popup.d.ts

@@ -3,6 +3,11 @@ export type CalendarPopupOptions = {
     value: string;
     disabled: boolean;
     onChange: (value: string) => void;
+    /**
+     * The calendar's today (`YYYY-MM-DD`); the device's local date when left
+     * out. An empty or malformed date throws a RangeError.
+     */
+    today?: string;
     /** Runs before a chosen date closes the calendar, such as a text reset. */
     beforeSelect?: () => void;
 };
@@ -33,4 +38,4 @@ export type CalendarPopup = {
  * DateField and CalendarButton. Disabling closes it for good; choosing a
  * date closes it, returns focus to the button, and reports a changed date.
  */
-export declare function useCalendarPopup({ value, disabled, onChange, beforeSelect, }: CalendarPopupOptions): CalendarPopup;
+export declare function useCalendarPopup({ value, disabled, onChange, today, beforeSelect, }: CalendarPopupOptions): CalendarPopup;

package/dist/components/date-field/use-calendar-popup.js

@@ -1,11 +1,13 @@
 import { useId, useRef, useState } from 'react';
-import { todayDateOnly } from '../../date-only.js';
+import { assertDateOnly, todayDateOnly } from '../../date-only.js';
 /**
  * The open state of a calendar dialog toggled by one button, shared by
  * DateField and CalendarButton. Disabling closes it for good; choosing a
  * date closes it, returns focus to the button, and reports a changed date.
  */
-export function useCalendarPopup({ value, disabled, onChange, beforeSelect, }) {
+export function useCalendarPopup({ value, disabled, onChange, today, beforeSelect, }) {
+    if (today !== undefined)
+        assertDateOnly('today', today);
     const buttonRef = useRef(null);
     const [open, setOpen] = useState(false);
     // Disabling closes the calendar for good, not just while disabled.
@@ -37,7 +39,7 @@ export function useCalendarPopup({ value, disabled, onChange, beforeSelect, }) {
             id,
             onClose: close,
             onSelect: select,
-            today: todayDateOnly(),
+            today: today ?? todayDateOnly(),
         },
     };
 }

package/dist/components/tooltip-trigger-aria.d.ts

@@ -0,0 +1,12 @@
+/**
+ * What a tooltip is to its trigger. A `description` supplements a trigger
+ * that already has a name; a `label` is the trigger's name, for an icon-only
+ * control whose tooltip says what it is.
+ */
+export type TooltipRelationship = 'description' | 'label';
+/** The trigger's own references, kept and joined with the tooltip's id. */
+export type TooltipTriggerAria = {
+    'aria-describedby'?: string;
+    'aria-labelledby'?: string;
+};
+export declare function tooltipTriggerAria(own: TooltipTriggerAria, tooltipId: string | undefined, relationship: TooltipRelationship): TooltipTriggerAria;

package/dist/components/tooltip-trigger-aria.js

@@ -0,0 +1,23 @@
+/*
+ * A description tooltip adds its id to the trigger's own `aria-describedby`
+ * and leaves its `aria-labelledby` exactly as it was. A label tooltip adds
+ * its id to the trigger's own `aria-labelledby` instead and leaves its
+ * `aria-describedby` as it was, so its text is the trigger's name (it wins
+ * over an `aria-label`) and is read once, not as both name and description.
+ * A disabled tooltip is not rendered (`tooltipId` undefined), so the trigger
+ * never points at a missing element.
+ */
+export function tooltipTriggerAria(own, tooltipId, relationship) {
+    if (relationship === 'label')
+        return {
+            'aria-describedby': own['aria-describedby'],
+            'aria-labelledby': joinIdRefs(own['aria-labelledby'], tooltipId),
+        };
+    return {
+        'aria-describedby': joinIdRefs(own['aria-describedby'], tooltipId),
+        'aria-labelledby': own['aria-labelledby'],
+    };
+}
+function joinIdRefs(...ids) {
+    return ids.filter(Boolean).join(' ') || undefined;
+}

package/dist/index.d.ts

@@ -8,7 +8,7 @@ export { CalendarButton, type CalendarButtonLabels, type CalendarButtonProps, }
 export { Checkbox, type CheckboxProps } from './components/Checkbox.js';
 export { Spinner, type SpinnerProps, type SpinnerSize, } from './components/Spinner.js';
 export { Progress, type ProgressProps, type ProgressTone, } from './components/Progress.js';
-export { Tooltip, type TooltipProps } from './components/Tooltip.js';
+export { Tooltip, type TooltipProps, type TooltipRelationship, } from './components/Tooltip.js';
 export { RadioGroup, type RadioGroupOption, type RadioGroupProps, } from './components/RadioGroup.js';
 export { AppHeader, type AppHeaderProps } from './components/AppHeader.js';
 export { Badge, type BadgeProps, type BadgeSize, type BadgeTone, badgeSizes, badgeTones, } from './components/Badge.js';

package/dist/index.js

@@ -7,7 +7,7 @@ export { CalendarButton, } from './components/CalendarButton.js';
 export { Checkbox } from './components/Checkbox.js';
 export { Spinner, } from './components/Spinner.js';
 export { Progress, } from './components/Progress.js';
-export { Tooltip } from './components/Tooltip.js';
+export { Tooltip, } from './components/Tooltip.js';
 export { RadioGroup, } from './components/RadioGroup.js';
 export { AppHeader } from './components/AppHeader.js';
 export { Badge, badgeSizes, badgeTones, } from './components/Badge.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@scalewing/react",
-  "version": "1.19.0",
+  "version": "1.21.0",
   "description": "Scalewing DOM components and package-owned CSS utilities.",
   "type": "module",
   "license": "MIT",