Add ChoroplethMap, a GeoJSON region choropleth chart component that joins data rows to features by name/nameProperty and shades regions with a continuous visualMap scale. Includes Kumo light/dark map colours, tooltip formatting, optional legend, hover/click callbacks, roam controls, docs, and demos.

Both BubbleMap and ChoroplethMap now apply a d3-geo projection (latitude-clamped Mercator by default; pass another d3-geo projection or null for raw plotting) and size by aspectRatio so the map fills its container without letterboxing. The container height now derives from the projected window's aspect ratio by default; pass an explicit height to opt back into a fixed pixel height.

Update BubbleMap viewport behavior to avoid resetting user pan and zoom while refreshing bubble data.

BubbleMap now defaults roam to false to avoid accidental pan and zoom interactions. Consumers that want drag-to-pan or scroll-to-zoom can pass roam={true}.

Add orientation="vertical" support to Flow for laying out nodes top-to-bottom. The align prop now controls cross-axis alignment in both orientations.

feat(chart): add BubbleMap chart component

New BubbleMap component renders proportional bubbles over a registered geographic map using ECharts' scatter series. Includes value-based radius scaling, a mapColors palette addition to ChartPalette, and supporting types. Also extracts escapeHtml / defaultValueFormat tooltip helpers into a shared tooltip-utils module reused by SankeyChart.

Keep primary and destructive button active/focus rings matched to their variant color.

Use the Button component for Toast close controls and match the hover tint to the toast variant.

Limit Dropdown content height to available viewport space to prevent overflow.

Replace the internal class merging implementation with cnfast.

fix(button): resolve Firefox rendering artifact when Turnstile is present

Replace translate-y-px with box-shadow: inset 0 1px 0 0 var(--kumo-button-emphasis-bg) on the primary/destructive button emphasis overlay span. The transform triggered a rendering bug in Firefox on pages with Turnstile's contain: strict CSS. The box-shadow achieves the same visual depth effect without the rendering issue.

Fix Dialog size prop to set a fixed width instead of only a minimum width. Previously, dialog content could stretch the dialog beyond its intended size.

Update Base UI to 1.6.0.

Add Toolbar for composing explicit toolbar controls into a shared grouped card.

feat(chart): add enableLegendSelection prop to TimeseriesChart

Opt-in (default false) hidden ECharts legend that lets consumers drive series visibility imperatively via the legendSelect / legendUnSelect / legendToggleSelect actions — useful for building a custom interactive legend with ChartLegend. Series toggled off via the legend are also excluded from the tooltip. Requires registering ECharts' LegendComponent (echarts.use([LegendComponent])). When disabled, behaviour is unchanged.

Extend LegendItems to take pointer events & timeseries merges forwardref to support those events

Update the Button primary and destructive variants with token-derived gradient treatments.

Fix horizontal scroll in Sidebar.Content: always apply overflow-x: hidden on the scroll viewport, not just when collapsed. Base UI's ScrollArea.Viewport sets overflow: scroll as an inline style, which allowed ~14px of horizontal overflow when consumer content (e.g. search buttons with keyboard shortcuts) exceeded the sidebar width.

feat(radio): add generic value type support to Radio.Group and Radio.Item

Fix the green Badge variant missing its background color token.

Keep generated component registry descriptions to JSDoc summaries before markdown sections or code examples.

fix(button): use ring-kumo-line for default secondary button ring

Refine outline and secondary destructive button hover states.

fix(sidebar): correct GroupLabel top margin from mt-6 to mt-4

Allow unprefixed Dialog max-width classes to override the default viewport cap at desktop breakpoints.

Sidebar: mobile rewrite, smooth collapse transitions, and new props

New features:

• mobileBreakpoint prop on Provider — configurable viewport width for mobile detection
• contentClassName prop on Sidebar root — pass-through class for the inner content container
• Controlled mobile state — open prop now controls the mobile sidebar too, not just desktop

Fixes:

• Replaced Base UI Dialog mobile sidebar with a plain <nav> + backdrop for simpler, more predictable transitions
• Collapsible sections now animate closed smoothly when the sidebar collapses instead of snapping shut
• Removed hidden class from Sidebar.MenuSub so sub-menus participate in collapse animations
• Removed inertValue React-version helper — SidebarSlidingView now sets inert imperatively for React 18 compatibility
• Restored inert on closed SidebarCollapsibleContent while removing its data-open attribute

Styling:

• bg-kumo-tint → bg-(--sidebar-active-bg) CSS variable for active/hover/focus backgrounds
• Icon opacity 0.5 → 0.4; chevron gains hover opacity transition
• Header gains shrink-0 and animated padding on collapse
• Content scroll area gains animated gap transition and tabIndex={-1} on viewport
• Sliding views container gains max-w-(--sidebar-width) to prevent overflow
• Mobile sidebar uses --sidebar-animation-duration CSS variable for slide transition

Add React 18 and React 19 compatibility checks for Kumo tests.

Fix Chart (and SankeyChart) rendering in dark mode. The chart canvas now stays transparent so the surrounding bg-kumo-* surface shows through symmetrically in both modes, and ECharts' built-in "dark" theme is applied when isDarkMode is true so the tooltip card, axes, splitLines, and legend text are themed correctly.

fix(sidebar): add text truncation with ellipsis to Sidebar.MenuButton content

Previously, Sidebar.MenuButton used overflow-hidden which clipped long text without showing an ellipsis. Now uses truncate to match Sidebar.MenuSubButton's behavior.

Fix segmented Tabs scroll fade, scroll-into-view, and ring styling:

• Rewrite CSS scroll-fade masking to use @property-animated custom properties, fixing proportional fade rendering across browsers.
• Scroll the selected tab into view on click so it stays visible in overflowing tab lists.
• Move ring ring-kumo-hairline/70 from the inner list to the root container so the segmented variant ring wraps the entire component correctly.

Fix Flow connector rendering in Firefox by emitting valid SVG path data without array commas and setting visible overflow on the SVG element attribute.

Restore React 18-compatible Sidebar inert attribute handling while keeping the full React compatibility CI suite.

Fix Combobox and Autocomplete rendering in React 18 by using the explicit context provider API.

Update Banner to use borderless tinted styling by default and add a secondary variant.

Re-export useFilter from Combobox and Autocomplete namespaces. Use it to write custom filter props that preserve Base UI's default case- and accent-insensitive matching via Intl.Collator.

Sidebar: comprehensive modernization

Breaking changes:

• Removed Sidebar.Input — build custom search triggers inline
• Removed Sidebar.MenuAction — unused in practice
• Removed Sidebar.GroupContent and group-level collapsible props (collapsible, defaultOpen, open, onOpenChange) from Sidebar.Group — use Sidebar.Collapsible at the item level instead
• Replaced Base UI Collapsible dependency with custom CSS grid-rows implementation
• SidebarState type is now "expanded" | "collapsed" | "peeking" (was "expanded" | "collapsed")

New features:

• contained prop on Provider — absolute positioning for embedded/demo sidebars
• peekable prop on Provider — hover/focus collapsed sidebar to temporarily expand
• animationDuration prop on Provider — configurable animation timing
• Sidebar.SlidingViews + Sidebar.SlidingView — animated horizontal transitions between navigation surfaces
• Animated SidebarPanelIcon replacing Phosphor SidebarSimpleIcon
• Enhanced Sidebar.Trigger with aria-expanded and dynamic aria-label
• Keyboard-accessible resize handle (arrow keys, Home, End)
• Custom Sidebar.Collapsible with keyboard auto-expand on focus

Token/styling fixes:

• border-kumo-hairline → border-kumo-line throughout
• Hardcoded duration-250 → --sidebar-animation-duration CSS custom property
• bg-kumo-base → bg-(--sidebar-bg) for theme overridability
• Focus styles: ring-2/ring-kumo-brand → outline-none/text-kumo-strong/bg-kumo-tint
• Icon opacity-50, updated spacing (header h-58px, footer h-12, menu gap-y-px)
• isolate on sidebar root with low z-index (z-1, z-2) instead of z-20/z-50
• Mobile sidebar now has correct data-state/data-side/data-variant/data-collapsible attributes

TimeseriesChart: React tooltip with Base UI positioning

Replaces ECharts' HTML-string tooltip with a React component positioned by Base UI's Tooltip primitive:

• Tooltip rendered as a React component with correct theme tokens — no more inline styles or getComputedStyle hacks
• Positioning handled by Base UI Tooltip (Floating UI), with automatic collision avoidance and viewport flipping
• New tooltipFollowCursor prop: "both" (default, free-following) or "x" (axis-locked, Recharts-style)
• New tooltipMode prop: "all" (default) or "single" (nearest series to cursor)
• New tooltipMaxItems prop: caps rows in "all" mode with +N more footer (default 10)
• Date formatted with Intl.DateTimeFormat (locale-aware) instead of ISO string
• Values sorted descending; fallback formatter avoids scientific notation

Banner: replace dark: Tailwind variants with new kumo-banner-info and kumo-banner-warning semantic tokens so dark-mode opacity is baked into the design system. No visual change.

fix(styles): show pointer cursor on clickable Kumo elements by default

Adds a global cursor: pointer rule scoped to elements rendered by Kumo components, identified by the new data-kumo-component and data-kumo-part attributes. Interactive component roots and parts now opt into the rule by setting these attributes, which gives the library a stable scoping primitive that doesn't couple to Tailwind class names.

Components updated to set data-kumo-component / data-kumo-part: Button, LinkButton, Link, Checkbox, Radio, Switch, Select (trigger, option), DropdownMenu (item, link-item, checkbox-item, radio-item, submenu-trigger), Combobox (trigger, item, clear, chip-remove), Autocomplete (item), Dialog (trigger, close), Popover (trigger), Tabs (tab), Collapsible (trigger, default-trigger), Breadcrumbs (link), TableOfContents (item, group-link), Sidebar (menu-button, menu-sub-button, trigger, rail), MenuBar (option), Toast (close), SensitiveInput (toggle-visibility, copy, masked-container).

fix(sidebar): collapsed state styling, transitions, and sliding views

Add flex items-center to ComboboxBase.Icon in TriggerInput for consistency with TriggerValue and Select

Fix Select placeholder not showing when renderValue is provided and the value is empty.

Update semantic color tokens to better represent status icons and indicators:

• Adjust status token values in the theme generator and refresh generated theme output
• Update toast and badge status background treatments
• Update docs to reflect new tint token usage

Adjust toast visual styling for improved readability and emphasis: increase background tint intensity for success/warning/info variants, refine description text contrast, and update close-button icon contrast.

Fixed vertical alignment of checkbox and radio indicators with multi-line labels.

When label text wrapped to multiple lines, the indicators were vertically centered against the entire text block. They now align to the top, sitting next to the first line of text.

echarts is now an optional peer dependency. If you don't use Chart components (Chart, TimeseriesChart, SankeyChart), it will no longer be installed automatically. If you do use them, run npm install echarts (as documented).

Added Badge dot styling as a new variant for indicators that need a subtle visual cue. Updated badge docs and demo examples to reflect the new badge variant and dot-style behavior.

Update Base UI to 1.5.0.

Fix InputGroup focus ring thickness and color: container mode uses 1.5px ring (wraps entire group including buttons), hybrid container zone and individual mode use 1px ring (thin to avoid colliding with adjacent buttons), and all modes use ring-kumo-focus/50 (50% opacity) to match the standalone Input component.

Fix error state red border on Combobox, Select, Autocomplete, and SensitiveInput to match Input behavior

Add inline label layout and fix auto-assigned node colors in tooltips

Fix Tooltip popup overflowing viewport when content is wider than available space. The popup now constrains its width to var(--available-width), a CSS variable provided by Base UI's Positioner that reflects the space between the trigger and the viewport edge.

Fix language alias normalization in ShikiProvider

• Add normalizeLanguage() function that maps common language aliases (js, ts, sh, yml, py, md, gql) to their canonical SupportedLanguage names
• Normalize language aliases in ShikiProvider when preloading grammars, so passing ['js', 'ts'] works the same as ['javascript', 'typescript']
• Normalize language aliases in highlight() hook at runtime, so code fences using js or ts highlight correctly without warnings
• Export normalizeLanguage from @cloudflare/kumo/code for consumers who need to normalize aliases themselves
• Intentionally omit mdx alias since MDX has a distinct grammar that would lose JSX highlighting if mapped to markdown

fix(banner): remove variant selection background for legibility

Selected text inside Banner now uses the browser default selection color instead of a same-hue variant-tinted background. The previous selection:bg-kumo-{info,warning,danger} utilities produced low contrast between the selection background and the variant text color (most notably in light mode for the error and alert variants), making selected text hard to read.

Add left and right props to SankeyChart for controlling series layout padding

Fix tooltip popup exit transitions by animating the Tailwind scale property alongside opacity.

Add passwordManagerIgnore to Input for suppressing password manager overlays on non-credential fields.

Add scroll fade to segmented tabs. When tabs overflow, gradient masks appear on the edges based on scroll position via scroll-driven animations (Chrome 115+, degrades gracefully). Scrollbar is hidden; the fade is the scroll affordance.

Add size="sm" variant to Tabs component (h-6.5 / 26px, matching Input sm)

Forward toastManager prop on <Toasty> so code outside the React tree (timers, query-cache listeners, module-load callbacks) can dispatch toasts via a manager created by createKumoToastManager(). Also surface createKumoToastManager on the top-level package export (previously only available via the deep @cloudflare/kumo/components/toast path).

Add transparent background to SankeyChart component

Expose optionUpdateBehavior prop on TimeseriesChart to control how ECharts applies option updates

Add hideLabel prop to Field so components can skip the native <label> while keeping description/error wiring. Use it in Select with Base UI's Select.Label to fix hover/focus coupling between the label text and trigger.

fix(input): render error and description props without requiring a label

fix(radio): prevent radio button distortion with long labels by adding shrink-0 to the default appearance radio indicator

Fix overflowing segmented Tabs drag-to-scroll interactions so mouse and touch drags reliably scroll while normal tab clicks still activate tabs.

Create Sankey Chart component

Fix CommandPalette List bottom ring being clipped by Footer background. Add scroll padding to prevent items from clipping behind rounded corners.

Deprecate to prop on Link in favor of href. The to prop is a routing-framework concept that doesn't belong on a presentational component. Use href for all link destinations and configure a LinkProvider wrapper to bridge to your router. to continues to work but emits a dev-mode deprecation warning.

Allow LayerCard.Primary and LayerCard.Secondary to accept all standard HTML div attributes, including data-testid for testing.

Set cursor-default on Tooltip triggers so disclosure buttons don't appear clickable. Overridable via className.

Export Combobox.Trigger, Combobox.Value, and Combobox.Icon — the raw Base UI primitives for building custom combobox triggers. Use these when you need full control over the trigger's visual treatment (e.g. a sidebar account switcher that renders as a plain button instead of an input-like control).

fix(CloudflareLogo): remove registered trademark symbol from full logo variant

Fix Google Translate DOM mutation crash in Button

Remove z-50 from mobile Sidebar Dialog backdrop and panel. The z-50 caused portaled floating elements (Popover, DropdownMenu, Select, Combobox) opened from inside the Sidebar to render behind the Dialog backdrop. Matches the pattern used by Kumo's own Dialog component, which relies on DOM order for stacking with no explicit z-index. Also adds data-sidebar-backdrop and data-sidebar-popup attributes as stable CSS hooks.

fix(combobox): forward all props from TriggerValue to ComboboxBase.Value, enabling placeholder support and styled placeholder text via data-[placeholder]:text-kumo-placeholder

fix(registry): correct Select component metadata for AI-generated code

The component registry metadata was incorrectly typing Select's value, defaultValue, and onValueChange props as string, causing AI agents to produce broken code when implementing Select with object values (e.g., rendering object.value in the trigger instead of the label).

Changes:

• value type: string → T (generic, matches actual component interface)
• defaultValue type: string → T
• onValueChange type: (value: string) => void → (value: T) => void
• Added missing renderValue prop: (value: T) => ReactNode — required for object values
• Added missing items prop: supports both Record<string, string> and Array<{ label, value }> forms
• Added missing isItemEqualToValue prop: required for object equality comparison

Gracefully fall back to default variant instead of crashing when an invalid variant prop is passed at runtime. Previously 22 of 25 components would throw TypeError on unknown variant values; all 25 now use a shared resolveVariant() utility that returns the default config and logs a dev warning.

Forward all Base UI Panel props (including keepMounted and hiddenUntilFound) through Collapsible.DefaultPanel. Previously these were silently dropped because DefaultPanel used a standalone props interface instead of extending BasePanelProps.

Fix registry codegen to match demo examples when component export name differs from directory name (e.g. DropdownMenu vs dropdown). This restores missing examples for DropdownMenu and other affected components.

TooltipProvider props (delay, closeDelay, timeout) are now shown in the Tooltip component's API Reference on the docs site.

Rebalanced semantic text token usage to improve hierarchy and consistency across components, docs, and generated Figma output.

• Updated theme token definitions so text-kumo-strong represents high-emphasis text and text-kumo-inactive is lighter/inactive in both light and dark modes.
• Migrated affected UI surfaces from text-kumo-strong to text-kumo-subtle where content is supportive metadata, labels, or secondary text.
• Synced token usage in docs and Figma code generators with the updated semantic text mapping.

BREAKING: Checkbox onCheckedChange now receives event details as second argument

The onCheckedChange callback signature now matches Base UI, providing access to the underlying event:

// Before
onCheckedChange={(checked) => console.log(checked)}

// After (event details available as optional second arg)
onCheckedChange={(checked, eventDetails) => {
  console.log(checked);
  console.log(eventDetails.event); // native event
}}

Removed deprecated props:

• onChange - use onCheckedChange instead
• onValueChange on individual checkboxes - use onCheckedChange instead
• onClick - was redundant, use standard React event handling via spread props

Migration:

// Before (deprecated)
<Checkbox onChange={(e) => console.log(e.target.checked)} />
<Checkbox onValueChange={(checked) => setChecked(checked)} />

// After
<Checkbox onCheckedChange={(checked) => setChecked(checked)} />

Note: Checkbox.Group's onValueChange prop is unchanged - it still accepts (values: string[]) => void.

feat(Collapsible)!: refactor to compound component API

Breaking change: Collapsible now uses a compound component pattern matching other Kumo components like Popover and Dialog.

Before

<Collapsible label="Show details" open={open} onOpenChange={setOpen}>
  Content here
</Collapsible>

After

<Collapsible.Root open={open} onOpenChange={setOpen}>
  <Collapsible.Trigger>Show details</Collapsible.Trigger>
  <Collapsible.Panel>Content here</Collapsible.Panel>
</Collapsible.Root>

Migration

For the quickest migration, use the new DefaultTrigger and DefaultPanel components which preserve the previous styling:

<Collapsible.Root open={open} onOpenChange={setOpen}>
  <Collapsible.DefaultTrigger>Show details</Collapsible.DefaultTrigger>
  <Collapsible.DefaultPanel>Content here</Collapsible.DefaultPanel>
</Collapsible.Root>

New Sub-components

feat(Text): decouple visual heading variants from semantic HTML elements

Breaking change: heading1, heading2, heading3 variants no longer auto-render <h1>, <h2>, <h3> tags. They now render as <span> by default. Use the as prop to set the appropriate semantic heading level for your document outline.

Before:

<Text variant="heading1">Title</Text> // rendered <h1>

After:

<Text variant="heading1" as="h1">
  Title
</Text> // explicit semantic element

The as prop is now restricted to valid text elements: "h1" through "h6", "p", and "span".

BREAKING (v2): Text requires an explicit as prop when variant is a heading ("heading1", "heading2", "heading3").

The previous major bump (#393) decoupled heading variants from semantic HTML — heading variants render as <span> unless an as prop is provided. That made the library more flexible but introduced a silent accessibility footgun: forgetting as on a real section heading produced a <span>, excluding it from the document outline without any type-level feedback.

This change makes as required for heading variants via a discriminated union. Body and monospace variants are unchanged (as remains optional; defaults to <p> and <span> respectively).

Migration

Every <Text variant="heading1">, <Text variant="heading2">, <Text variant="heading3"> must now pass as. TypeScript will flag each call site:

// Before (compiled, silently produced a <span>)
<Text variant="heading1">Page Title</Text>

// After (required)
<Text variant="heading1" as="h1">Page Title</Text>

// Still allowed — decorative heading-styled text that is NOT a section heading:
<Text variant="heading1" as="span">Big bold card label</Text>

For each heading call site, decide whether it's a real section heading (use as="h1"/"h2"/etc.) or decorative (use as="span"). Codemod cannot make this choice mechanically — it is a semantic judgment per usage.

Body and monospace variants: no changes required.

feat(radio, checkbox, switch): add composable Legend sub-component for group components

• Add Radio.Legend, Checkbox.Legend, and Switch.Legend sub-components
• Accepts className for full styling control (e.g. className="sr-only" to visually hide)
• Make legend string prop optional when using the sub-component instead
• Useful when a parent Field already provides a visible label and the legend would be redundant
• Breaking: Switch.Group no longer renders a visible border/padding/rounded container — now consistent with Radio.Group and Checkbox.Group. Use className to add a border if needed.

Add InputGroup compound component for composing decorated inputs

Compound structure: InputGroup, InputGroup.Input, InputGroup.Addon, InputGroup.Suffix, InputGroup.Button.

• Field integration — pass label, description, error, required, and labelTooltip directly to InputGroup
• Size variants (xs, sm, base, lg) propagate to all sub-components via context, including icon sizing in addons
• InputGroup.Addon — positions icons, text, or buttons at align="start" (default) or align="end" of the input
• InputGroup.Suffix — inline text suffix (e.g. .workers.dev)
• InputGroup.Button — ghost button for secondary actions with tooltip support
• Deprecated InputGroup.Label — use InputGroup.Addon instead
• Deprecated InputGroup.Description — use InputGroup.Suffix instead

{
  /* Reveal / hide password */
}
<InputGroup>
  <InputGroup.Input
    type={show ? "text" : "password"}
    defaultValue="password"
    aria-label="Password"
  />
  <InputGroup.Addon align="end" className="pr-1">
    <InputGroup.Button
      size="sm"
      aria-label={show ? "Hide password" : "Show password"}
      onClick={() => setShow(!show)}
    >
      {show ? <EyeSlashIcon size={16} /> : <EyeIcon size={16} />}
    </InputGroup.Button>
  </InputGroup.Addon>
</InputGroup>;

{
  /* Search input */
}
<InputGroup>
  <InputGroup.Addon>
    <MagnifyingGlassIcon className="text-kumo-subtle" />
  </InputGroup.Addon>
  <InputGroup.Input placeholder="Search..." />
</InputGroup>;

Adds Autocomplete component. A free-form text input with an optional filtered suggestion list. Unlike Combobox, the value is not constrained to the items list.

feat(radio): accept ReactNode for Radio.Item label and honor controlPosition on card appearance

• Radio.Item's label prop now accepts ReactNode, allowing icons, badges, or other markup alongside text.
• Radio.Group's controlPosition prop now takes effect on appearance="card". Card appearance continues to default to "end" (radio on the right); pass controlPosition="start" to render the radio on the left of the label and description.

Polish TableOfContents indicator and semantic HTML

• Replace pill/background-tint hover with left-border indicator pattern
• Switch to semantic ul/li HTML structure
• Add href and active props to TableOfContents.Group for clickable labels

feat(table): add onCheckedChange prop to Table.CheckCell and Table.CheckHead, aligning with the Checkbox component's signature.

The new prop exposes an optional second argument with event details, matching Base UI's idiom:

<Table.CheckCell
  checked={selected.has(row.id)}
  onCheckedChange={(checked, eventDetails) => {
    toggle(row.id);
    eventDetails?.event.stopPropagation();
  }}
/>

The existing onValueChange prop still works but is now deprecated and flagged by the no-deprecated-props lint rule. It will be removed in a future major version. Migrate by renaming the prop — the single-argument callback shape is preserved.

This change is additive and does not require consumer code changes at this time.

Expand Text component's as prop to accept additional HTML text elements: label, dt, dd, li, figcaption, legend, pre, code, em, strong, small, abbr, and time. This unblocks downstream usage in Stratus where Text needs to render as definition list terms, labels, and code elements.

Remove invalid hover border utility from secondary button variants to keep hover styling consistent and avoid unintended class output.

Update chart color docs and demos, including sequential heatmap/CVD coverage and improved chart demo behavior.

Combobox.Item now renders a visible disabled state when the disabled prop is set. Previously the prop was forwarded to Base UI (so click/keyboard selection were correctly blocked) but the row looked identical to an enabled one. Adds data-[disabled]:* Tailwind classes for muted text, cursor-not-allowed, reduced opacity, and suppresses the highlight background on disabled rows during keyboard navigation. Also fixes className passthrough — user-supplied classes are now merged via cn() instead of being overridden.

Improve focus ring consistency and clipping behavior across inputs and related controls.

• Move the command palette focus ring to the input header container with focus-within and remove duplicate input-level ring styles.
• Update Select trigger and option focus styles to use inset focus rings to prevent clipping in rounded/overflow contexts.
• Fix clipboard copy button focus ring clipping by using inset focus-visible ring, matching border-radius inheritance, and isolated stacking.
• Align InputGroup and InputGroup.Button focus ring color to ring-kumo-focus, including hybrid container-zone focus ring classes.
• Update InputGroup tests to match inline focus ring class changes.
• Set DatePicker (react-day-picker) focus ring token to var(--color-kumo-brand).
• Update InputGroup container and hybrid keyboard outlines in kumo-binding.css to use var(--color-kumo-focus) at 1px weight.

Allow CommandPalette.Input to accept standard HTML input attributes (autoComplete, autoCorrect, autoCapitalize, spellCheck, data-*, etc.) by extending its props type with InputHTMLAttributes<HTMLInputElement>. Export new CommandPaletteInputProps type.

Fix InputGroup hover state incorrectly propagating to the first child button (e.g. in Pagination.Controls). Root now renders as <div> instead of <label> when it contains multiple labelable controls.

Fix Table body cells rendering at 16px. The Table root now sets text-base (14px) so <td> cells match Kumo's default body font-size instead of inheriting the browser default. Also replaces an arbitrary text-[14px] in Empty with text-base.

Improved focus and keyboard accessibility styles across Kumo components and docs navigation.

• Added the kumo-focus semantic token to the theme generator config and generated theme-kumo.css output.
• Updated focus ring behavior across interactive components (including Button, Input, InputGroup, Select, Checkbox, Radio, Switch, Sidebar, Tabs, Menubar, and related controls) for more consistent and visible keyboard focus visibility.
• Text-entry controls use a lighter opacity kumo-focus ring to keep pointer and keyboard focus visually consistent where browsers apply :focus-visible heuristics to typed-input controls.
• Refined Select and Input styling/state combinations to align focus visuals with current semantic token usage.
• Updated docs SidebarNav keyboard-focus affordances (links, section toggles, search trigger) and adjusted collapsible list overflow so focus rings remain visible.
• Replace raw colors in Select with kumo semantic tokens.

Fix InputGroup container className to enforce mb-0, ensuring all container variants (not just the standalone <label> mode) reset inherited bottom margin.

Fix InputGroup label wrappers to enforce mb-0, preventing inherited label margins from shifting layout and click-target overlays.

chore: update @base-ui/react to v1.4.0

Bugfix release with improvements to Popover hover state, Checkbox/Switch readOnly mode, Select touch handling, Tabs activation direction, Toast timers, and various other fixes. No breaking changes.

feat(chart): rename formatter to dangerousHtmlFormatter for XSS awareness

BREAKING CHANGE: The formatter property in KumoChartOption['tooltip'] has been renamed to dangerousHtmlFormatter. This change makes the security implications of using HTML formatters more explicit to developers. The API remains identical—only the name has changed.

Migration: Replace formatter with dangerousHtmlFormatter in your chart tooltip configurations.

feat(tooltip, popover): deprecate asChild in favor of render prop

Unifies composition patterns across the library by adopting Base UI's render prop pattern. The asChild prop is now deprecated on:

• Tooltip
• Popover.Trigger
• Popover.Close

Migration:

- <Tooltip content="Save" asChild>
-   <Button>Save</Button>
- </Tooltip>
+ <Tooltip content="Save" render={<Button>Save</Button>} />

- <Popover.Trigger asChild>
-   <Button>Open</Button>
- </Popover.Trigger>
+ <Popover.Trigger render={<Button>Open</Button>} />

- <Popover.Close asChild>
-   <Button>Close</Button>
- </Popover.Close>
+ <Popover.Close render={<Button>Close</Button>} />

The asChild prop remains functional for backward compatibility but will be removed in a future major version.

feat(popover): expose anchor prop on Popover.Content for virtual positioning

Forwards Base UI's anchor prop through Popover.Content to the underlying Positioner, enabling popover positioning against custom elements, refs, or virtual points (e.g., a DOMRect from getBoundingClientRect()). This is useful when the popover trigger and the desired anchor are in different component trees, or when anchoring to a coordinate rather than a DOM element.

Convert Table of Contents to exported Kumo component

feat(Select): add size prop (xs/sm/base/lg) matching Input and Combobox heights

feat(layer-card): support simple card usage and deprecate Surface

• allow LayerCard to be used directly without LayerCard.Primary for simple single-layer card layouts
• keep LayerCard.Secondary and LayerCard.Primary supported for the existing layered card pattern
• deprecate Surface in favor of LayerCard while keeping the old API working as a compatibility wrapper
• update docs and examples to prefer LayerCard, including table examples that no longer need a nested LayerCard.Primary

fix(pagination): add ARIA attributes for screen reader accessibility

• Wrap pagination controls in <nav> for proper landmark navigation
• Add aria-live="polite" and aria-atomic="true" to status text for page change announcements
• Add navigation to PaginationLabels for i18n customization of the nav aria-label

fix(chart): escape HTML in tooltip series name and values

Escapes HTML entities in TimeseriesChart tooltip series names and values before rendering.

fix(combobox): make TriggerInput caret button clickable for Playwright tests

fix(dropdown): pass children through when render prop is provided on DropdownMenu.Trigger

fix(Select): TypeScript inference with strictNullChecks and renderValue/placeholder interaction

TypeScript fix: Under strictNullChecks, using value={objectOrNull} would cause T to be inferred as never, making callbacks like onValueChange and renderValue unusable. This is now fixed.

Runtime fix: renderValue is now only called with non-null values. When value is null, the placeholder is shown instead. Previously, renderValue would receive null at runtime despite being typed as (value: T) => ReactNode.

// Recommended pattern
<Select
  placeholder="Select..."
  value={value}
  onValueChange={setValue} // value is T | null (works with strictNullChecks)
  renderValue={(v) => v.name} // v is T (non-null), no defensive coding needed
/>

Fix sidebar collapsible content snapping shut instead of animating smoothly when closing.

fix(table): align sticky column colors with compact header variant

fix(tokens): correct text-kumo-subtle dark mode value to provide visible contrast

Updated the token value for kumo-line and kumo-hairline in dark mode so they are more visible.

• replace kumo-line usages with kumo-hairline across Kumo components and docs UI/content styles
• use ring-kumo-line for shadowed surfaces (for example combobox, dialog, select, dropdown, toast, and related surface wrappers)
• adjust theme token configuration and generated styles to support updated neutral/hairline appearance

fix(a11y): add accessible labels to icon-only controls

Add Enter key navigation to Pagination page number input and new pageSelector prop for dropdown mode

• The page number input in Pagination.Controls now navigates on Enter key press (previously only on blur)
• New pageSelector prop on Pagination.Controls: set to "dropdown" to render a Select dropdown instead of a text input for page selection

Add disabled option support, groups, group labels, and separators to Select

• Select.Option now accepts disabled and className props
• New Select.Group and Select.GroupLabel sub-components for organizing options under labeled headers
• New Select.Separator sub-component for visual dividers between groups
• The items object-map prop now accepts SelectItemDescriptor values with disabled metadata

Expose delay and closeDelay props on Tooltip component to control open and close timing. These props are forwarded to the underlying Base UI Trigger component.

Input and InputArea now automatically apply error styling when the error prop is truthy. You no longer need to set variant="error" separately - just pass an error message and the styling is applied automatically. The variant="error" prop is now deprecated but still works for backwards compatibility.

Adjust semantic tint usage for status/error ring styles across core form and feedback components.

• Update background styles in Badge and Banner components to use *-tint tokens.
• Update kumo-danger to a darker token to improve a11y contrast.
• Update error ring styling in form components to use semantic tokens (now darker with token swap).
• Removed text-color-badge-red-subtle token in replacement of the danger token.
• Update theme generator color mappings used by these tints to improve visual consistency.

Fix CodeBlock crash when an unsupported lang value is passed at runtime. The codeVariants() function now uses optional chaining with a nullish coalescing fallback to the default language, matching the defensive pattern already used by switchVariants() and badgeVariants().

fix(select): use ring-kumo-hairline token in Select popup (missed in PR #355)

Fix Select popup scrolling and height behavior; align popup/list structure with Base UI. Split popup into frame (Popup) and scroll container (List) to match Combobox pattern and fix touch scroll on long lists.

fix(loader): add ARIA attributes for screen reader accessibility

Added role="status" and aria-label="Loading" to the Loader SVG component to make it accessible to screen readers. This resolves a WCAG 2.1 SC 4.1.3 (Status Messages) violation where assistive technology users received no indication that content was loading.

Refine badge semantics/fill styling and banner tone updates

• Rework Badge variant model to prioritize semantic variants (primary, secondary, error, warning, success, info) with updated descriptions and primary as default.
• Keep token color variants for product-specific use cases while updating class mappings so semantic and token variants are distinct.
• Slight updates to token color variants to meet a11y contrast requirements.
• Update token color variants by replacing yellow with purple since yellow doesn't meet a11y contrast requirements, and keeping docs/demo examples in sync.
• Update badge docs demos/content to focus on primary semantic badges and a consolidated "other variants" section.
• Adjust banner variant surfaces (default, alert, error) to stronger tinted backgrounds and borders.
• Update theme generator badge/semantic token mappings and regenerate theme-kumo.css to match the new badge color system.

Fix Switch label click not toggling when a custom id prop is provided

The id was not being forwarded to Base UI's Switch.Root, causing a mismatch between the label's htmlFor and the button's actual id.

Align semantic token documentation and docs presentation updates.

• Update colors.mdx token documentation structure.
• Replaced kumo-ring with kumo-hairline for border/ring colors and all its instances in kumo components and docs.
• Sync packages/kumo/ai/USAGE.md token reference categories and descriptions with the docs token guide.
• Adjust the typo in the recessed dark token value in theme generator config and regenerate theme-kumo.css.
• Updated kumo-fill-hover token value from neutral-700 to neutral-800

Badge: add color-based variants and deprecate semantic variants

• Add color variants: red, orange, yellow, green, teal, blue, neutral, inverted
• Add subtle variants for each color (red-subtle, orange-subtle, etc.) with lighter backgrounds and darker text
• Retain outline and beta variants unchanged
• Deprecate primary (use inverted), secondary (use neutral), destructive (use red), success (use green)
• Dark mode support: subtle variants flip to dark backgrounds with light text, regular color variants darken slightly, inverted flips to white bg with black text
• Default variant changed from primary to neutral

Add action prop to Banner for rendering CTA buttons alongside structured title/description content without resorting to the children prop.

Refresh semantic surface color tokens and component surface usage.

• Add and adopt kumo-canvas as the page-level surface token in theme output and docs usage.
• Rebalance neutral token values in kumo-binding.css and generated theme variables for improved light/dark surface hierarchy.
• Update surface-related component styling (LayerCard, MenuBar, Tabs) to align with the refreshed canvas/elevated/recessed layering model.
• Update token usage guidance in ai/USAGE.md to reflect page vs component background roles.

Make timeseries' highlighted on hovering a data point

Add Shadow DOM support via KumoPortalProvider and container prop on all portal-based components

All overlay components (Dialog, DropdownMenu, Combobox, Select, Tooltip, Popover, CommandPalette, Toast) now support rendering inside Shadow DOM or custom containers.

New exports:

• KumoPortalProvider - Context provider to set default portal container for all overlays
• PortalContainer - Type for portal container (HTMLElement, ShadowRoot, or ref)

Component updates: All portal-based components now accept an optional container prop:

• Dialog - container prop on Dialog component
• DropdownMenu.Content - container prop
• Combobox.Content - container prop
• Select - container prop
• Tooltip - container prop
• Popover.Content - container prop
• CommandPalette.Root and CommandPalette.Dialog - container prop
• Toasty (Toast provider) - container prop

Usage:

Set once at the app level:

<KumoPortalProvider container={shadowRoot}>
  <App />
</KumoPortalProvider>

Or override per component:

<Dialog container={customContainer}>
  <Dialog.Title>Modal inside shadow DOM</Dialog.Title>
</Dialog>

When no provider or prop is set, components default to document.body (existing behavior).

SkeletonLine: add blockHeight prop to set a container height and vertically center the skeleton line within it

Table: add sticky prop to Table.Head and Table.Cell for pinning columns to left/right edges, and sticky prop to Table.Header for sticky header rows. Uses isolate stacking context with z-0/z-1/z-2 layering.

Add toml as a supported language for syntax highlighting in the Code component

Add title prop to Button — wraps the button in a Tooltip when provided.

Checkbox.Group & Radio.Group: remove fieldset border box and simplify styling

• Remove rounded-lg border border-kumo-line p-4 wrapper from both group fieldsets
• Downsize legend from text-lg to text-base with inline-flex layout
• Drop font-medium from Checkbox.Item and Radio.Item labels

Fix missing disabled styling on Combobox triggers. TriggerValue and TriggerMultipleWithInput now apply opacity-50 and cursor-not-allowed when disabled, matching the behaviour of the Select component.

Update dialog backdrop overlay to use bg-kumo-recessed token

Remove ai/schemas.ts from version control (now fully generated at build time)

Fix LayerCard.Primary stacking order when sandwiched between LayerCard.Secondary elements

Fix SensitiveInput focus ring and global CSS pollution

• Fix focus ring not showing on container when inner input is focused (focus-within:outline)
• Add defensive styles to eye toggle and copy buttons to prevent global CSS pollution
• Fix inputVariants parentFocusIndicator using wrong selector ([&:has(:focus-within)] → focus-within:)

SkeletonLine: move .skeleton-line styles into @layer base so Tailwind utility classes (e.g. className="h-6") can override the default height

Tabs indicator now uses translate-x for its transition animation, replacing the CSS left transition with a GPU-accelerated transform.

fix flow component not reflecting padding prop

Surface: replace as prop with Base UI render prop for polymorphism

The as prop used a hand-rolled generic forwardRef pattern (with as any casts) that conflicted with how the rest of the library handles polymorphism via Base UI's useRender hook.

Surface now accepts a render prop, consistent with Link and other components. The old as prop is kept as a deprecated alias and continues to work unchanged — no migration required.

// Still works (deprecated)
<Surface as="section">...</Surface>

// Preferred going forward
<Surface render={<section />}>...</Surface>

Switch: polish squircle styling

• Use ring-inset on thumb to prevent border protruding beyond the track
• Make thumb ring transparent to remove visible border outline
• Switch focus indicator from ring to outline with outline-offset-2 to avoid clashing with the track's own ring border

fix(Tabs): update segmented tab spacing and track styling

• Adjust segmented Tabs list styling colour to bg-kumo-recessed and added ring to make the Tabs background more visible
• Remove extra edge spacing and keep the segmented track/indicator alignment consistent

update toast styling to use a subtle ring and background that reflect each state.

update status text token values for info and danger to improve a11y contrast ratio on banners.

Add truncate prop to Text component. When true, applies truncate min-w-0 classes to clip overflowing text with an ellipsis.

Make Chart components keyboard focusable with tabindex. Timeseries adds ariaDescription prop

Generate component-registry files at build time, remove from git

Eliminates contributor friction by generating component-registry.json, component-registry.md, and schemas.ts during the build process instead of tracking them in git. Contributors will no longer see stale diffs or need to manually regenerate these files.

• Add ai/component-registry.json and ai/component-registry.md to .gitignore
• Convert ai/schemas.ts to a stub file for TypeScript compilation
• Add codegen:registry to build script for deterministic generation

feat(code): add HCL (HashiCorp Configuration Language) as a supported syntax highlighting language

fix(flow): connector lines no longer misalign when the page scrolls or a sidebar shifts the layout

getBoundingClientRect values were stored in React state per node and later subtracted against a freshly-read container rect at connector-draw time. Any layout shift (sidebar open/close, page scroll, inner container scroll) between those two reads produced stale coordinates, causing connector lines to jump out of place or disappear entirely.

Fix: add scroll and resize listeners (capture phase) at the FlowNode, FlowParallelNode, and FlowNodeList levels so all rects are remeasured after any layout shift. Connector computation in FlowNodeList and FlowParallelNode is also moved from the render phase into useLayoutEffect so the container rect and node rects are always read in the same synchronous pass.

Add missing HCL language import to server-side Shiki bundle

The HCL language was added to SupportedLanguage type and the client-side provider in a previous commit, but the server.tsx BUNDLED_LANGS object was missed. This caused typecheck failures when building.

Sidebar: polish animations, fix separator reflow bug, improve header spacing

Fix connector alignment and spacing between adjacent parallel nodes in Flow diagrams

Add success and info toast variants with semantic token styling. Migrate error/warning variants from raw CSS to semantic tokens for consistent theming.

Fix Radio compound component to use Object.assign pattern, enabling sub-component detection (Radio.Group, Radio.Item) in the component registry.

Revert outline button variant ring width from ring-2 (2px) back to ring (1px) to restore visual consistency with existing dashboard usage.

fix: update styling for mostly-used components with new greyscale tokens (combobox, dialog, input, layerCard, select & tabs) as well as homegrid and component preview backgrounds.

Remove es2022 build target that caused Jest/babel-jest test failures in stratus

Add radio card appearance via appearance="card" prop on Radio.Group and Radio.Item. Cards display a bordered, selectable container with title and description. Also adds description prop to Radio.Item for helper text. Supports vertical and horizontal orientations, error state, and disabled state.

Expose Chart optionUpdateBehavior to control how ECharts applies option updates; notMerge now defaults to false.

Add neutral variant to Switch component and improve accessibility

• New variant="neutral" option: monochrome switch with squircle shape, matching the design from stratus
• Improved off-state visibility for default variant with darker background/ring colors
• Removed error variant (not useful for toggle switches)
• Added defensive fallback so invalid variant values don't cause runtime crashes

removed outline-none to bring back focus states on all buttons

Fix flaky vitest "Closing rpc while fetch was pending" error in deep-imports test

Fix InputArea label click not focusing textarea. Use FieldBase.Control with render callback to properly associate the label with the textarea element.

Fix TypeScript return types for ShikiProvider and CodeHighlighted components.

Changed return type from ReactNode to React.JSX.Element to resolve JSX compatibility errors. This fixes issues when consuming these components in projects with stricter TypeScript configurations (e.g., skipLibCheck: false), where ReactNode was incorrectly inferred as a valid JSX element return type.

Fix table header font size to ensure consistent rendering across dashboards with different default font sizes

Add dedicated kumo-placeholder text color token and use it for Input, InputArea, SensitiveInput, and CommandPalette placeholder text. The new token provides better visual distinction between placeholder and active text in both light and dark modes.

Replace the package-level ESLint pass with Oxlint JS plugin coverage for the remaining jsx-a11y rules, and pin the library build to es2022 with a post-build browser-compat test that blocks newer runtime APIs from shipping in dist.

fix(Select): prevent chevron overflow with long multi-select values

Added min-w-0 truncate to the value element and shrink-0 to the chevron icon so that long option names truncate gracefully instead of pushing the chevron outside the select bounds.

Fix combobox caret icon to use text-kumo-subtle with fill-current instead of invalid fill-kumo-subtle token

fix TimeseriesChart brush cursor not activating when loading prop transitions from true to false

add xAxisTickFormat, yAxisTickFormat, and tooltipValueFormat props to TimeseriesChart; deprecate yAxisTickLabelFormat

Deprecation: yAxisTickLabelFormat is deprecated

If you were using yAxisTickLabelFormat to customize tooltip output, switch to tooltipValueFormat.

Before:

<TimeseriesChart yAxisTickLabelFormat={(v) => `${v} req/s`} />

After:

<TimeseriesChart tooltipValueFormat={(v) => `${v} req/s`} />

Fix combobox caret icon visibility by using fill-kumo-subtle instead of fill-kumo-ring

reorganize greyscale tokens and update color preferences

updated button styles for outline and secondary

Fix Jest module resolution failures and reduce Shiki bundle size

Jest Fix:

• Add chunkFileNames config to prevent double-dash filenames (e.g., combobox--ec3iibR.js) that Jest cannot resolve
• Move chunks to dist/chunks/ subdirectory for cleaner structure

Bundle Size Reduction:

• Switch from full Shiki bundle to fine-grained imports via shiki/core
• Reduce from ~300 language/theme chunks to ~16 bundled languages
• Total JS files reduced from 358 to ~163 (54% reduction)

Supported Languages: javascript, typescript, jsx, tsx, json, jsonc, html, css, python, yaml, markdown, graphql, sql, bash, shell, diff

Breaking Change:

• BundledLanguage type is now deprecated, use SupportedLanguage instead
• Only the languages listed above are bundled; other Shiki languages are no longer available out of the box

Fix npm publish failure by removing cross-package dependency from prepublish hook

Select: Improved label API to match Input component pattern

• hideLabel is now deprecated. When label is provided, the label is visible by default (previously hidden by default).
  • For visible labels: <Select label="Country" /> (no changes needed if you were using hideLabel={false})
  • For hidden labels: Use <Select aria-label="Select a country" /> instead of <Select label="Country" hideLabel={true} />
• Bug fix: Placeholder text now displays correctly when using object map items format (e.g., items={{ a: "Option A" }}). Previously, placeholders only worked with array format items.

Backward compatibility: hideLabel={true} still works but shows a deprecation warning in development. Existing code using hideLabel={false} requires no changes.

Migration guide:

// Before (label hidden by default)
<Select label="Country" />                    // label was sr-only
<Select label="Country" hideLabel={false} />  // label was visible

// After (label visible by default, matching Input)
<Select label="Country" />                    // label is now visible
<Select aria-label="Country" />               // use aria-label for hidden labels

Add optional id prop to Flow.Node for stable node identification and connector test IDs

Avoid adding multiple toasts with the same ID. Use a subtle bump animation when a toast with an existing ID is added.

Fix theme token flicker by generating stable light/dark fallback variables with safer scope and layer precedence.

fix: add defensive styles to prevent global CSS pollution

Problem

When Kumo components are used in applications with aggressive global styles (e.g., Stratus's cfBaseStyles layer), certain elements get polluted:

• label { margin-bottom: 1rem } adds unwanted margins to all labels
• button { background: gray } affects unstyled button wrappers (e.g., tooltip triggers)
• a { color: var(--text-color-primary) } can override link colors if the consuming app defines --text-color-primary differently

Solution

Add defensive Tailwind utility classes directly to components. These:

1. Reset commonly-polluted properties to safe defaults
2. Use cn() (tailwind-merge) so consumer styles via className still override them
3. Are no-ops in clean CSS environments (no visual change in Kumo docs)

Changes

Label margins (m-0)

• Label: labelVariants() now includes m-0
• Field: FieldBase.Label gets m-0
• Checkbox: label wrapper gets m-0
• Radio: label wrapper gets m-0
• Switch: label wrapper gets m-0

Button trigger resets

• Tooltip trigger (when !asChild): bg-transparent border-none shadow-none p-0 m-0 h-auto min-h-0 leading-[0] inline-flex items-center
• Collapsible trigger: bg-transparent border-none shadow-none p-0 m-0

Link color namespace fix

• Link: Changed from text-primary to text-kumo-link to avoid collision with consuming apps that define --text-color-primary differently

Label tooltip composition

• Label: Tooltip trigger now uses <Button variant="ghost" size="xs" shape="square"> with asChild, leveraging composition instead of relying on defensive resets

Docs

Added "Custom Trigger" section to Tooltip docs demonstrating that className can fully override defensive styles when not using asChild.

fix(dropdown): use Base UI CheckboxItemIndicator for proper accessibility

Replace custom Checkbox component with Base UI's CheckboxItemIndicator in DropdownMenuCheckboxItem. The previous implementation nested an interactive Checkbox inside the menuitemcheckbox role, causing duplicate accessibility labels. CheckboxItemIndicator is automatically aria-hidden and only renders when checked, following the standard Base UI pattern.

Fix Field error message line height by adding leading-snug for consistent text spacing

Improve info banner dark mode contrast for WCAG AA compliance. Changes kumo-info from blue-700 (L=48.8%) to blue-400 (L=70.7%), achieving 7.97:1 contrast ratio against the banner background.

Fix Combobox.TriggerValue icon misalignment caused by inherited line-height

The caret icon span was inheriting line-height from the parent button's text-base class, causing the span's height to exceed the icon's height (e.g., 21.5px vs 16px). The icon sits at the top of the span by default, so when the span is centered via top-1/2 -translate-y-1/2, the icon appears offset.

Added flex items-center to the icon wrapper to ensure proper vertical centering regardless of inherited styles. This matches the pattern used in TriggerInput.

fix(Pagination): use aria-label instead of label for PageSize select

The Select component now shows visible labels by default. Since Pagination.PageSize already displays "Per page:" text next to the select, the internal Select should use aria-label for accessibility without showing a duplicate visible label.

chore(toast): replace inline XIcon with Phosphor icon

Prevent password managers autofilling Pagination input field

fix(tabs): improve focus ring and hover styling

• Fixed focus ring to use proper ring-kumo-ring token instead of browser default blue
• Segmented variant: inset focus ring to avoid overlap with adjacent tabs, hidden on active tab
• Underline variant: added padding for better focus ring spacing around text
• Added subtle hover states for both variants

fix(Tabs): pass TabItem render prop through to Base UI for custom tab rendering (e.g., link-based tabs)

Add Shiki-powered CodeHighlighted component for syntax highlighting

• New entry point: @cloudflare/kumo/code - keeps Shiki out of main bundle
• ShikiProvider: Lazy-loads Shiki on first render, shares instance across all children
• CodeHighlighted: Syntax highlighting with line numbers, line highlighting, copy button
• Server utilities: @cloudflare/kumo/code/server for SSR/static highlighting
• Themes: Ships with github-light and vesper defaults, supports any Shiki theme
• i18n: Customizable labels via provider or per-component
• CSS customization: --kumo-code-highlight-bg variable for highlight color
• Deprecates: Legacy Code and CodeBlock components (will be removed in v2)

feat(combobox): add size prop with xs, sm, base, lg variants matching Input component

feat(flow): make nested lists work inside parallel nodes

Add role prop to Dialog component supporting both "dialog" (default) and "alertdialog" ARIA roles

New Feature:

• Dialog.Root now accepts a role prop to specify the dialog's ARIA semantics
• When role="alertdialog" is used, the dialog uses Base UI's AlertDialog primitives for proper accessibility
• This provides correct screen reader announcements for confirmation and destructive action dialogs

When to use role="alertdialog":

• Destructive actions (delete, discard, remove)
• Confirmation flows requiring explicit user acknowledgment
• Actions that cannot be undone
• Critical warnings or errors

Example:

// Standard dialog (default)
<Dialog.Root>
  <Dialog.Trigger render={(p) => <Button {...p}>Edit</Button>} />
  <Dialog>...</Dialog>
</Dialog.Root>

// Alert dialog for destructive actions
<Dialog.Root role="alertdialog">
  <Dialog.Trigger render={(p) => <Button variant="destructive" {...p}>Delete</Button>} />
  <Dialog>...</Dialog>
</Dialog.Root>

Add TimeseriesChart component with ECharts integration, supporting legends, gradient fills, custom axis formatting, loading skeleton state, and configurable color palettes.

feat(select): auto-render options from items prop when children omitted

The Select component now automatically renders Select.Option elements from the items prop when children are not explicitly provided.

Add missing success background and tint semantic color tokens (bg-kumo-success, bg-kumo-success-tint) for parity with info, warning, and danger. Fix text-kumo-success dark mode contrast by using green-400 instead of green-500. Add new success Badge variant for positive state indicators.

fix(breadcrumbs): improve mobile breadcrumb readability

breadcrumbs now render a compact mobile trail for deeper hierarchies by collapsing early levels to ... and keeping the trailing path visible. labels in breadcrumb links and the current page now truncate correctly to prevent stacking or overlap on narrow viewports.

fix(badge): prevent crash when unknown variant is passed

Add defensive fallback to primary variant when an unrecognized variant string is provided to Badge component. This prevents "Cannot read properties of undefined (reading 'classes')" errors when consumers use a variant that doesn't exist in their installed version.

fix(code): Fix CodeHighlighted dark mode, layout, and SSR issues

• Fix dark mode: Make <pre> background transparent so container's bg-kumo-base handles theming and border-radius is respected
• Fix layout: Wrap Shiki output in overflow container to prevent line highlight negative margins from being clipped
• Fix width: Add w-full to container for proper full-width display
• Fix SSR: Remove "use client" directive from @cloudflare/kumo/code/server entry point so server utilities work in RSC/SSR contexts

fix(CommandPalette): add explicit text-base class to Item component for consistent 14px font size

Fix Select to render description and error when hideLabel is true

Previously, the description and error props were silently ignored when hideLabel was true (the default). Now, helper text and error messages display correctly even when the label is visually hidden.

Fix TypeScript errors when consumers type-check their projects with kumo installed.

Previously, TypeScript would attempt to type-check raw .tsx and .ts source files shipped in the package (block sources in dist/src/blocks/, ai/schemas.ts, and scripts/theme-generator/*.ts), causing build failures in downstream projects.

This change:

• Moves block source files to a separate dist/blocks-source/ directory
• Compiles ai/schemas.ts and scripts/theme-generator/*.ts to JavaScript
• Updates package exports to point to compiled .js files with proper .d.ts types

fix(inputs): expand small control hit areas

Fix pagination component to properly wrap numbers in tabular-nums class for consistent number alignment. Both the page range and total count now use tabular numerals.

Simplify Select placeholder implementation by using Base UI's native placeholder prop on SelectBase.Value instead of manually injecting placeholder items into the items array. This provides a cleaner, more intuitive API that aligns with standard HTML select behavior while maintaining backward compatibility with the null-value placeholder pattern.

fix(breadcrumbs): enhance mobile breadcrumb display for better readability

Add variant="compact" prop to Table.Header for a more condensed header style

Fix Combobox group label styling to use semantic token and correct padding

Standardize z-index usage with isolation containment

• Add isolation: isolate to components with internal stacking (Tabs, MenuBar, InputGroup, Flow/Parallel)
• Simplify internal z-index values to z-0/z-1/z-2 instead of arbitrary values like z-10/z-20
• Remove superfluous z-10 from CommandPalette List
• Update Toast viewport to z-1 (matching Base UI's documented pattern)
• Update ClipboardText viewport to use isolate instead of z-50

This prevents z-index values from leaking outside component boundaries.

feat(dropdown): add LinkItem for navigation links and fix icon rendering

New Features:

• Add DropdownMenu.LinkItem for navigation links (semantic <a> element with proper menu item behavior)
• Upgrade @base-ui/react from 1.0.0 to 1.2.0
• Add new primitives: csp-provider and drawer from Base UI 1.2.0

Bug Fixes:

• Fix icon prop not rendering on DropdownMenu.Item when no href is provided

Deprecations:

• href prop on DropdownMenu.Item is deprecated. Use DropdownMenu.LinkItem instead.

Migration:

// Before (deprecated)
<DropdownMenu.Item href="https://example.com">Link</DropdownMenu.Item>

// After (recommended)
<DropdownMenu.LinkItem href="https://example.com" target="_blank">
  Link
</DropdownMenu.LinkItem>

DropdownMenu.LinkItem gives you full control over link attributes (target, rel, etc.) without the component making assumptions about your intent.

Add positionMethod prop to Popover.Content to control CSS positioning strategy. Use "fixed" when the popover needs to escape stacking contexts (e.g., inside sticky headers). Defaults to "absolute".

Improve Flow diagram components with disabled node support and better connector rendering:

• Add disabled prop to FlowNode for greying out connectors
• Add align prop to FlowParallelNode for start/end alignment
• Improve connector path rendering with smarter junction detection
• Fix panning behavior to not interfere with node interactions

Refactor Banner component with softer styling and i18n-friendly props

• Added title and description props for structured content with i18n support
• Softened visual appearance: reduced background opacity (20% -> 10%), muted border colors
• Text now uses text-kumo-default for readability, with colored icons for variant indication
• Added iconClasses to variant config for per-variant icon coloring
• Component now uses forwardRef and sets displayName per conventions
• Deprecated children and text props in favor of title/description
• Legacy children prop still works for backwards compatibility

Fix Checkbox ring color to use ring-kumo-contrast when checked or indeterminate

Fix Combobox dropdown scrolling regression and improve scroll behavior.

Bug fix: The overflow-hidden class was accidentally re-introduced during a semantic color token migration, which overrode overflow-y-auto and caused dropdown content to be clipped instead of scrollable.

Improvement: Restructured Combobox.Content to use flexbox layout so that when using Combobox.Input inside the dropdown (searchable popup pattern), the input stays fixed at the top while only the list scrolls. Previously, the entire popup content would scroll together.

Scrollbar fix: Moved horizontal padding from the popup container to individual child components, so the scrollbar renders flush with the popup edge instead of being inset (which was clipping the checkmark indicators).

feat(flow): add FlowDiagram components for building directed flow diagrams

New components for visualizing workflows and data flows:

• FlowDiagram - Root container with pan/scroll support for large diagrams
• FlowNode - Individual node with automatic connector points
• FlowNode.Anchor - Custom attachment points for connectors within nodes
• FlowParallelNode - Container for parallel branches with junction connectors

Adds motion as a new dependency for smooth panning interactions.

Deprecate DateRangePicker in favor of DatePicker with mode="range"

• Added @deprecated JSDoc comments to DateRangePicker component and its exports
• IDEs will now show deprecation warnings guiding users to use DatePicker instead

Prevented ClipboardText from overflowing with long text values.

chore(kumo): add test scripts to root package.json

Add DatePicker component built on react-day-picker v9

New Component: DatePicker

• Three selection modes: single, multiple, and range
• Forwards all react-day-picker props for maximum flexibility
• Styled with Kumo tokens (no external CSS import needed)
• Supports localization via date-fns locales
• Supports timezone via timeZone prop
• Custom modifiers for highlighting specific dates
• Footer prop for messages/usage limits
• Accessible keyboard navigation with Kumo-styled focus rings

Usage:

// Single date
<DatePicker mode="single" selected={date} onSelect={setDate} />

// Multiple dates
<DatePicker mode="multiple" selected={dates} onSelect={setDates} max={5} />

// Date range
<DatePicker mode="range" selected={range} onSelect={setRange} numberOfMonths={2} />

Composing with Popover:

<Popover>
  <Popover.Trigger asChild>
    <Button variant="outline" icon={CalendarDotsIcon}>
      Pick a date
    </Button>
  </Popover.Trigger>
  <Popover.Content className="p-3">
    <DatePicker mode="single" selected={date} onSelect={setDate} />
  </Popover.Content>
</Popover>

Note: Consider using DatePicker with mode="range" instead of DateRangePicker for new projects - it offers more flexibility and a smaller bundle size.

Internal changes:

• Added react-day-picker v9 as a dependency
• Updated lint rule to allow components without KUMO_*_VARIANTS exports
• Updated component registry codegen to handle variant-less components
• Disabled jsx-a11y/no-autofocus rule (intentional prop forwarding)

feat(clipboard-text): add slide animation with tooltip on copy

Updated the MenuBar so its child buttons align with the container’s outer corners.

Fix kumo add to consolidate imports from @cloudflare/kumo into a single statement using inline type syntax.

Previously, running kumo add DeleteResource would produce non-conformant code with duplicate imports:

import { Dialog, DialogRoot } from "@cloudflare/kumo";
import { Input } from "@cloudflare/kumo";
import { Button } from "@cloudflare/kumo";

Now it produces a single consolidated import:

import {
  Dialog,
  DialogRoot,
  Input,
  Button,
  type DialogProps,
} from "@cloudflare/kumo";

This satisfies ESLint's import/no-duplicates rule with prefer-inline: true.

Fix z-index stacking issues with nested portaled components (e.g., Select inside Dialog)

• Remove unnecessary z-index values from Dialog, Select, Combobox, and Dropdown
• Delete .z-modal { z-index: 9999 } - DOM order now handles stacking naturally
• Components opened later correctly appear on top without z-index wars

fix(dropdown): improve external link detection to handle http:// and protocol-relative urls

updated the external link check to use a regex that matches https://, http://, and protocol-relative URLs (//). previously only https:// links opened in a new tab.

Changed ClipboardIcon to CopyIcon in ClipboardText component

Fix AI command USAGE.md path resolution to work correctly from bundled dist output

fix(cli): include block source files in build for kumo add command

The kumo add command was failing because block source files (.tsx) were not being copied to dist/ during the build process. This adds copying of block source files from src/blocks/ to dist/src/blocks/ so the CLI can install them into user projects.

fix(Table): Add indeterminate prop and fix checkbox click handling

• Added indeterminate prop to Table.CheckHead and Table.CheckCell components to support indeterminate checkbox state (shows minus icon when some but not all rows are selected)
• Fixed checkbox click handling - clicking directly on the checkbox now works correctly (previously only clicking the cell area next to the checkbox worked)
• Updated Table demos (TableSelectedRowDemo and TableFullDemo) with proper React state management for interactive row selection

fix: delete-resource shouldn't nest buttons within each other

support overwriting text in pagination component

fix(cli): resolve broken doc/docs/ls commands by fixing registry path from catalog/ to ai/ fix(dialog): wrap sub-components to isolate @base-ui/react type references from downstream consumers fix(label): render as <label> element with htmlFor support instead of <span> feat(input): add Textarea alias for InputArea feat(toast): add ToastProvider alias for Toasty feat(button): require aria-label on icon-only buttons (shape="square" | "circle") via discriminated union fix(docs): add Tailwind 4 @source directive to usage example, add confirmation dialog recipe, update Select basic example, document icon-only button aria-label pattern

fix: CLI commands now find component registry and run codegen:registry before publish

fix(cli): resolve registry path for docs and ls commands

Add CloudflareLogo component with glyph and full logo variants, color schemes (brand/black/white), and exported SVG path data for custom implementations

Replace .toSorted() with .sort() on spread copies to fix TypeError on Chrome <110

add 'Delete Resource' block

Add variant support, custom content, and action buttons to Toast component.

"fix: adjusted bullet size for sensitive input"

fixes to figma plugin init + zod v4 in kumo

Fix kumo CLI bin resolution in repo checkouts so pnpm install doesn't warn when dist/ hasn't been built yet.

Kumo 1.0.0 Release

The first stable release of Kumo, Cloudflare's component library.

Breaking Changes

Blocks Distribution via CLI

Blocks (PageHeader, ResourceListPage) are no longer exported from @cloudflare/kumo. They must now be installed via the CLI:

npx @cloudflare/kumo init        # Initialize kumo.json
npx @cloudflare/kumo add PageHeader

Blocks are copied to your project for full customization with imports automatically transformed to @cloudflare/kumo.

Checkbox API Changes

• Ref type changed: HTMLInputElement → HTMLButtonElement
• Props changed: No longer extends InputHTMLAttributes (explicit props only)
• Handler renamed: onChange/onValueChange → onCheckedChange (deprecated handlers still work)

Banner API Deprecation

The text prop is deprecated in favor of children:

// Before (deprecated)
<Banner text="Your message" />

// After (preferred)
<Banner>Your message</Banner>

New Features

• Link component: Inline text links with Base UI composition API and render prop for framework routing
• DropdownMenu enhancements: Nested submenus (Sub, SubTrigger, SubContent) and radio items (RadioGroup, RadioItem)
• Grid component: New layout primitive
• Theme generator: Config-driven token definitions with consolidated semantic color system
• Component catalog: Visibility controls for documentation
• Deprecated props lint rule: kumo/no-deprecated-props detects @deprecated JSDoc tags

Fixes

• Dropdown danger variant color contrast
• Tabs segmented indicator border radius
• Combobox dropdown scrolling
• Primary button hover/focus contrast

Migration Guide

Blocks

If you were using blocks (note: they were never officially exported):

# 1. Initialize configuration
npx @cloudflare/kumo init

# 2. Install blocks
npx @cloudflare/kumo add PageHeader
npx @cloudflare/kumo add ResourceListPage

# 3. Update imports to the local path shown after installation

Checkbox

// Before
<Checkbox onChange={(e) => setValue(e.target.checked)} />;
const ref = useRef<HTMLInputElement>(null);

// After
<Checkbox onCheckedChange={(checked) => setValue(checked)} />;
const ref = useRef<HTMLButtonElement>(null);

Banner

// Before (still works, but deprecated)
<Banner text="Your message" />

// After
<Banner>Your message</Banner>

feat(banner): add children prop, deprecate text prop

Banner now supports children for content, which is the preferred API. The text prop is deprecated but still works for backwards compatibility.

// Preferred (new)
<Banner>Your message</Banner>
<Banner icon={<Icon />}>Your message</Banner>

// Deprecated (still works)
<Banner text="Your message" />

The text prop will be removed in a future major version.

feat(cli): blocks are now distributed via CLI instead of npm exports

New CLI commands for block management:

• kumo init - Initialize kumo.json configuration file
• kumo blocks - List all available blocks for CLI installation
• kumo add <block-name> - Install a block to your project with transformed imports

Blocks are copied to your project for full customization, with relative imports automatically converted to @cloudflare/kumo.

Add lint rule to detect usage of deprecated props on Kumo components.

• New kumo/no-deprecated-props lint rule automatically detects deprecated props from @deprecated JSDoc tags
• Component registry now includes deprecated field for props with @deprecated annotations
• Docs site shows strikethrough and @deprecated badge for deprecated props in API reference tables

To deprecate a prop, add a JSDoc comment:

interface MyComponentProps {
  /** @deprecated Use `newProp` instead */
  oldProp?: string;
}

The lint rule will flag usage and show a helpful message:

The `oldProp` prop on <MyComponent> is deprecated. Use `newProp` instead.

Add nested menu (submenu) and RadioGroup/RadioItem support to DropdownMenu

• Add DropdownMenu.Sub, DropdownMenu.SubTrigger, and DropdownMenu.SubContent for nested submenus
• Add DropdownMenu.RadioGroup, DropdownMenu.RadioItem, and DropdownMenu.RadioItemIndicator for single-selection menus
• Fix SubTrigger styling to match Item component
• Fix focus ring on dropdown popup
• Add Storybook stories demonstrating nested menus and radio items
• Update Astro docs with examples and API reference

fix(checkbox): make label clickable, add new onCheckedChange API

• Clicking the label now toggles the checkbox
• New onCheckedChange callback (preferred over deprecated onChange/onValueChange)
• Ref type is now HTMLButtonElement (aligns with Base UI implementation)

Add Link component with Base UI composition API

• New Link component for consistent inline text links
• Supports render prop for composition with framework-specific links (e.g., React Router)
• Uses Base UI's useRender hook for proper ref/event merging
• Three variants: inline (default), current, and plain
• Link.ExternalIcon subcomponent for external link indicators
• Integrates with LinkProvider for framework-agnostic routing

feat: theme generator, color token consolidation, component catalog

• New theme generator system with config-driven token definitions
• Consolidated semantic color tokens with config.ts as single source of truth
• New component catalog system with visibility controls
• Added Grid component
• Updated Figma plugin generators for new semantic tokens
• Migrated documentation from Storybook to Astro

run component-registry when starting docs site

Fix color contrast issue in Dropdown danger variant by using subtle bg-kumo-danger/5 background instead of bg-kumo-danger-tint, improving readability while maintaining the visual "danger" cue

Add render prop for Tabs component

Fix Combobox dropdown not scrolling when it has many items. The overflow-hidden class was overriding overflow-y-auto, causing content to be clipped instead of scrollable.

fix: improve primary button hover/focus contrast by using bg-hover-selected instead of bg-primary/70

Adds disabled prop for table cell checkboxes

fix(tabs): adjust segmented indicator border radius for proper visual nesting

Ship component registry with @cloudflare/kumo module

feat(popover): Add new Popover component

Adds a new Popover component based on Base UI's popover primitive. The Popover provides an accessible popup anchored to a trigger element, with support for:

• Compound component API: Popover, Popover.Trigger, Popover.Content, Popover.Title, Popover.Description, Popover.Close
• Positioning options: side (top, bottom, left, right), align (start, center, end), sideOffset
• Click-to-open by default, with optional openOnHover behavior
• Controlled mode via open and onOpenChange props
• Visual styling matching the updated Tooltip component (surface-aware background, proper light/dark mode support)

Migrate documentation site from React Router (kumo-docs) to Astro (kumo-docs-astro) as the primary docs platform, consolidate CI/CD pipelines, and add version display features.

Bump node to v24.12.0

Add Figma plugin for UI kit generation

• New plugin at packages/figma/ (@cloudflare/figma-plugin)
• Generates 29 component types: Badge, Banner, Button, Checkbox, Code, CodeBlock, Collapsible, Combobox, DateRangePicker, Dialog, Dropdown, Icon Library, Input, InputArea, LayerCard, LinkButton, Loader, MenuBar, Meter, Pagination, RefreshButton, Select, SensitiveInput, Surface, Switch, Switch.Group, Tabs, Text, Toast
• Each component generated with light and dark mode sections
• Icon Library generator creates all Phosphor and Cloudflare brand icons
• Parses component-registry.json and source files for variant specs
• Extracts opacity modifiers from Tailwind classes (bg-kumo-brand/70 → opacity-primary-70)
• Binds fills/strokes to kumo-colors variables
• Includes progress UI and validation output

feat(kumo): add command-palette component

semantic color changes and more consolidation for non-text colors

feat(tooltip): Update tooltip to use bg-kumo-base with proper light/dark mode support

Changes the tooltip background from a fixed dark color to a surface-aware background that adapts to light and dark modes. Implements Base UI's 3-path arrow SVG approach for pixel-perfect border alignment across color modes.

fix(kumo): updated version in package.json (unintentionally downgraded)

feat(PageHeader): add optional title and description props

• Adds title?: string and description?: string props to PageHeader block
• Title renders as semantic h1 for Section 508 and WCAG 2.4.2 (Level A) compliance: "Web pages have titles that describe topic or purpose"
• Description uses max-w-prose (65ch) for optimal readability per industry standards
• Styling matches Stratus Workers & Pages implementation
• Includes comprehensive Storybook examples (WithTitle, WithTitleAndDescription, CompleteExample)

Why This Feature Matters

Without this feature, pages using only PageHeader would lack a semantic page title (h1), requiring developers to manually add titles elsewhere. This creates:

• ❌ Risk of Section 508 and WCAG 2.4.2 violations
• ❌ Compliance risk for FedRAMP High authorization (requires Section 508 conformance)
• ❌ Inconsistent title placement across pages
• ❌ Additional implementation burden on every page

With this feature, PageHeader provides a standardized way to include accessible page titles that:

• ✅ Render as semantic h1 elements (required by Section 508 and WCAG 2.4.2)
• ✅ Visually differentiate from breadcrumbs
• ✅ Work correctly with screen readers and assistive technology
• ✅ Maintain consistency across the dashboard
• ✅ Support FedRAMP High compliance requirements

Important: Breadcrumbs Are Not Page Titles

Breadcrumbs serve navigation purposes and cannot replace semantic page titles. Both should coexist:

• Page title (h1): Primary orientation, required for accessibility
• Breadcrumb trail: Secondary navigation showing site hierarchy
• Visual differentiation: Size, weight, and placement distinguish the two

References

• Section 508 Standards - Requires WCAG 2.0 Level A and AA conformance
• WCAG 2.4.2: Page Titled - Level A requirement

Add table component

• Introduce new Table component with row variants and styling options
• Add Table documentation and examples to kumo-docs

lighter red in light mode

Add Label component with standardized label features for form fields

• New Label component with support for ReactNode children, optional indicator, and tooltip
• Enhanced form components (Input, Select, Checkbox, Switch, SensitiveInput, Combobox) with:
  • label prop now accepts ReactNode (not just strings)
  • required={false} shows "(optional)" text
  • labelTooltip prop for info icon with hover tooltip
• Updated Field component to use Label internally
• Added Label documentation page to kumo-docs

Add Radio component for single-selection from a set of options

• New Radio.Group and Radio.Item compound components built on Base UI primitives
• Supports vertical and horizontal orientations
• Includes error, description, and disabled states
• controlPosition prop for label placement ("start" or "end")
• Full accessibility support with semantic HTML and keyboard navigation
• Documentation added to both kumo-docs and kumo-docs-astro sites

Add Storybook preview deployments and MR reporter system

• Storybook previews deploy to Cloudflare Workers on MR commits
• Staging deployment to storybook.staging.kumo-ui.com on merge to main
• Consolidated MR comments with beta npm version and preview URL

Add variant prop to Tabs component with 'segmented' (default) and 'underline' options

Fix label not appearing in Combobox unless a description or error given.

fix bug where delete user external links were being treated as internal navigation and appending urls to domain

Fix Base UI nativeButton warning in Switch component by adding nativeButton prop to BaseSwitch.Root

Update deployment configs to enable preview urls

added a next / previous form of pagination

Modernize Active Sessions page with updated Kumo design patterns

• Align border color with sidebar
  • Center arrow icon in select component

Add bg-kumo-base as default background for Surface component

Fix Combobox button styles

Migrate to @base-ui/react V1

Breaking Change: Updated from @base-ui-components/react to the new @base-ui/react V1 package.

What Changed

• Package name: @base-ui-components/react → @base-ui/react
• Version: ^1.0.0-rc.0 > ^1.0.0
• All component imports updated to use the new package
• All primitive re-exports updated to use the new package
• Build configuration updated to bundle the new package

Migration Required

This is a major version bump because the underlying Base UI package has changed. While the Kumo API remains the same, you'll need to:

1. Update dependencies:

   pnpm install
   

2. No code changes needed - All Kumo components and primitives work exactly the same way. The package name change is internal to Kumo.

For Kumo Maintainers

After merging this PR, run:

# Install the new @base-ui/react package
pnpm install

# Regenerate primitive files with new package references
pnpm --filter @cloudflare/kumo build:primitives

# Rebuild the package
pnpm --filter @cloudflare/kumo build

# Run tests to verify everything works
pnpm --filter @cloudflare/kumo test:run

Technical Details

• Updated all imports from @base-ui-components/react/* to @base-ui/react/*
• Updated generate-primitives.ts script to reference new package
• Updated test files to check for new package name
• Updated vite.config.ts manualChunks to match new package name
• All 37 primitives will be regenerated with new imports

Add built-in Field integration to form components with automatic layout

New Features:

• Input, InputArea, SensitiveInput, Select, Checkbox, Switch, and Combobox now accept label, description, and error props for built-in Field wrapper support
• Automatic CSS-driven layout: vertical for text inputs, horizontal for checkboxes/switches using :has() selectors
• Checkbox.Group and Switch.Group compound components for managing multiple related controls with shared legend/description/error
• Storybook Code Panel enabled for better component code examples

Accessibility:

• Runtime console warnings (dev-only) when Input/Checkbox lack accessible names (label, aria-label, or aria-labelledby)
• Comprehensive JSDoc documentation with accessibility guidance and examples

Breaking Changes:

• Field component removed from public API (now internal implementation detail - use component props instead)

Migration:

// Before: Explicit Field wrapper
<Field label="Email" description="...">
  <Input placeholder="you@example.com" />
</Field>

// After: Built-in Field API (recommended)
<Input
  label="Email"
  description="..."
  placeholder="you@example.com"
/>

change error color for text component to match field input error colors

secondary-destructive button variant

fix: update changeset validation logic

• Complete semantic color tokens migrated from Stratus app

  • Document color and text-color tokens in Storybook
  • Add accessibility tests via Storybook Vitest addon
  • Add component-metadata generator for AI tooling
  • Enable linting in CI/CD (passing)
  • Apply Prettier Tailwind plugin for consistent class ordering
  • Use pnpm catalog for shared package versions
  • Semantic colors now scoped to [data-theme] and [data-mode] attributes
  • Consumers must ensure root element has these attributes for proper theming

  Migration Guide

  Add data-theme and data-mode attributes to your root element:

  // React example
  <html data-theme="kumo" data-mode={isDark ? "dark" : "light"}>
  
  // Static HTML
  <html data-theme="kumo" data-mode="light">
  

  • data-theme: Set to "kumo" (default theme) or other theme variants like "fedramp"
  • data-mode: Set to "light" or "dark" to control color scheme

  If no data-mode is set, the system defaults to light mode.

tab and text style fixes; storybook theme select always visible

inputs with built-in fields

Bundle Base UI primitives with granular exports and fix critical compatibility issues

Primitives: Granular Exports

Added granular exports for all 37 Base UI primitives alongside the existing barrel export. This enables better tree-shaking and smaller bundle sizes when using individual primitives.

// Barrel export (imports all primitives)
import { Slider, Popover, Tooltip } from "@cloudflare/kumo/primitives";

// Granular exports (tree-shakeable, recommended)
import { Slider } from "@cloudflare/kumo/primitives/slider";
import { Popover } from "@cloudflare/kumo/primitives/popover";

Available primitives: accordion, alert-dialog, autocomplete, avatar, button, checkbox, checkbox-group, collapsible, combobox, context-menu, dialog, direction-provider, field, fieldset, form, input, menu, menubar, meter, navigation-menu, number-field, popover, preview-card, progress, radio, radio-group, scroll-area, select, separator, slider, switch, tabs, toast, toggle, toggle-group, toolbar, tooltip.

Build Output Improvements

Fixed critical compatibility issues with Jest and React Server Components by improving the build configuration.

Problems Fixed

1. Jest Parsing Errors - The previous build used preserveModules: true, which preserved the pnpm directory structure (node_modules/.pnpm/) in dist. This caused Jest to fail parsing ESM imports because Jest's transformIgnorePatterns blocks nested node_modules by default.
2. Missing "use client" Directives - The rollup-plugin-preserve-directives plugin only works with preserveModules: true. When bundling with preserveModules: false, all "use client" directives were stripped, breaking components in Next.js App Router (RSC).

Solutions Implemented

• Flat bundle structure - Changed to preserveModules: false to eliminate nested node_modules/.pnpm/ paths
• "use client" injection - Added output.banner to inject the directive into all output chunks (since the plugin doesn't work without preserveModules)
• Manual code splitting - Implemented manualChunks to split large vendor dependencies for better caching:
  • vendor-base-ui (598 KB, 152 KB gzipped) - Base UI components
  • vendor-styling (74 KB, 13 KB gzipped) - clsx + tailwind-merge
  • vendor-floating-ui (33 KB, 10 KB gzipped) - Floating UI positioning
  • vendor-utils (24 KB, 7 KB gzipped) - tabbable, reselect, etc.

kumo cli

semantic text colors - consolidation

Removed label prop from input components. Prefer using Field to compose a label with an input.

consolidate blue text to match banner blue text across: badge, expandable, text components

consolidate on the green text tokens

Update kumo package to use literal depdency versions for better yarn linking/portal support.

improve input group label to be semantic and use htmlFor

Combobox Type Fixes

• Removed any type and eslint-disable comments
• Used proper ComboboxBase.Root.Props<Value, Multiple> from base-ui's namespace
• Simplified generic parameters from 3 (ItemValue, SelectedValue, Multiple) to 2 (Value, Multiple) to match base-ui's actual API

fix remaining lint errors and increase lint warn -> error

Update reamde documentation

Consolidate AGENTS.md and CLAUDE.md LLM instructions

fix resource-list href lint errors

Improve expandable component semantics

Update Storybook imports from @storybook/react to @storybook/react-vite for Storybook 10 compatibility. Also removes generatedAt timestamp from component registry to prevent merge conflicts during rebases.

improve sensitive input component - semantics, button nesting, labelling, screen reader experience

Fix: Resolve type check errors across components/blocks/layouts Fix: Export Kumo Breadcrumb as Breadcrumbs + Documentation Improvements Fix: MenuBar -Bypass the React 19 type checking issue with IconContext.Provider

improve semantics and labelling for date picker component

docs updates and semantic colors for banner

ship dark-mode color scheme styles from kumo lib instead of setting it at the app

Adds Storybook 10 integration to the Kumo component library for interactive component development, testing, and documentation. Includes stories for 29 components, automated plop generator updates, and documentation.

enforce button background transparency for tabs

Combobox - Adjust multiple select height with standard Kumo component height

Checkbox indeterminate state

Improve development workflow with 10x faster rebuilds and comprehensive documentation

Add development mode with optimized builds, skip minification and enable incremental TypeScript compilation. Update all READMEs and contributing docs with clear guidance on Storybook (recommended) vs watch build workflows. Add story file documentation to scaffolding sections and two-terminal setup instructions for testing components in docs.

Enhance CICD to publish beta releases

Fix: Resolve type check erros across components/blocks/layouts Fix: Export Kumo Breadcrumb as Breadcrumbs + Documentation Improvements Fix: MenuBar -Bypass the React 19 type checking issue with IconContext.Provider

Semantic color improvements

Improve select components

Fix Input borders

Fix exports

Compile Tailwind and Standalone CSS, update installation documentation

Adding changesets