An open source design system that's fully customizable and agent ready
TypeScript
docs: add PR references to all 19 v0.4.4 changesets
Cindy Zhang6b6ec634ec09
diff --git a/.changeset/banner-endcontent-wrap.md b/.changeset/banner-endcontent-wrap.mdindex 1dccbbb14f..5641105684 100644--- a/.changeset/banner-endcontent-wrap.md+++ b/.changeset/banner-endcontent-wrap.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Banner: `endContent` wraps to its own row on a narrow header instead of squeezing the title to one word per line.+[fix] Banner: `endContent` wraps to its own row on a narrow header instead of squeezing the title to one word per line (#5116).@cixzhangdiff --git a/.changeset/bottom-sheet-continuous-handoff.md b/.changeset/bottom-sheet-continuous-handoff.mdindex 7a1a15d1a1..31a2189328 100644--- a/.changeset/bottom-sheet-continuous-handoff.md+++ b/.changeset/bottom-sheet-continuous-handoff.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] BottomSheet: a swipe that scrolls to the end of the sheet's content and keeps pulling now expands the sheet, instead of stopping dead at the last line. The handoff used to be decided once, when the finger landed: a gesture that started mid-content stayed a scroll for its whole life, so the natural motion — swipe up through the list, reach the bottom, keep pulling — never reached the sheet. Reaching the end of the content is now enough. The sheet is anchored at the point where the content ran out, so only the travel past it moves the sheet, and the pull is left to the content when the finger comes back down or when there is no taller detent to expand into.+[fix] BottomSheet: a swipe that scrolls to the end of the sheet's content and keeps pulling now expands the sheet, instead of stopping dead at the last line. The handoff used to be decided once, when the finger landed: a gesture that started mid-content stayed a scroll for its whole life, so the natural motion — swipe up through the list, reach the bottom, keep pulling — never reached the sheet. Reaching the end of the content is now enough. The sheet is anchored at the point where the content ran out, so only the travel past it moves the sheet, and the pull is left to the content when the finger comes back down or when there is no taller detent to expand into (#5172).@imdreamrunnerdiff --git a/.changeset/bottom-sheet-lint-suppressions.md b/.changeset/bottom-sheet-lint-suppressions.mdindex d30690208c..24feeeeb1b 100644--- a/.changeset/bottom-sheet-lint-suppressions.md+++ b/.changeset/bottom-sheet-lint-suppressions.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[chore] Clear the mechanically fixable ESLint suppressions from the Bottom Sheet promotion: `BottomSheet` and `BottomSheetSwitcher` now use the React 19 context APIs (`<Context>` as provider, `use()`), the panel drops its duplicate body-element ref in favor of the one the gesture hook already tracks, and `useSheetGestures` reads `prefers-reduced-motion` through the shared `useMediaQuery` subscription so an open sheet follows a preference change.+[chore] Clear the mechanically fixable ESLint suppressions from the Bottom Sheet promotion: `BottomSheet` and `BottomSheetSwitcher` now use the React 19 context APIs (`<Context>` as provider, `use()`), the panel drops its duplicate body-element ref in favor of the one the gesture hook already tracks, and `useSheetGestures` reads `prefers-reduced-motion` through the shared `useMediaQuery` subscription so an open sheet follows a preference change (#5155).@imdreamrunnerdiff --git a/.changeset/bottom-sheet-scroll-drag-handoff.md b/.changeset/bottom-sheet-scroll-drag-handoff.mdindex f95a948392..adbbe31cd1 100644--- a/.changeset/bottom-sheet-scroll-drag-handoff.md+++ b/.changeset/bottom-sheet-scroll-drag-handoff.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] BottomSheet: an upward pull at the bottom of scrolled content no longer hijacks the gesture when the sheet is already fully expanded. It used to hand off to a sheet drag with nowhere to expand to, producing a rubber-band the release threw straight back, and — because the handoff swallows the rest of the gesture — leaving the content unscrollable until the finger lifted, so dragging back down collapsed the sheet instead of scrolling. The bottom edge now hands off only when a taller detent exists.+[fix] BottomSheet: an upward pull at the bottom of scrolled content no longer hijacks the gesture when the sheet is already fully expanded. It used to hand off to a sheet drag with nowhere to expand to, producing a rubber-band the release threw straight back, and — because the handoff swallows the rest of the gesture — leaving the content unscrollable until the finger lifted, so dragging back down collapsed the sheet instead of scrolling. The bottom edge now hands off only when a taller detent exists (#5161).@imdreamrunnerdiff --git a/.changeset/bottom-sheet-showcase-checkbox-state.md b/.changeset/bottom-sheet-showcase-checkbox-state.mdindex 58a8124416..c070f6b8e9 100644--- a/.changeset/bottom-sheet-showcase-checkbox-state.md+++ b/.changeset/bottom-sheet-showcase-checkbox-state.md@@ -2,7 +2,7 @@'@astryxdesign/cli': patch----[fix] Bottom Sheet showcase block: the filter checkboxes are interactive again.+[fix] Bottom Sheet showcase block: the filter checkboxes are interactive again (#5157).`CheckboxInput` is fully controlled — `value` is required and the input only moves when the owner updates it. The showcase passed a literal `value={false}` with no `onChange`, so the three filters ("In stock", "On sale", "Free shipping") rendered but could never be toggled: on the docs site the first thing a reader tries in a Bottom Sheet does nothing, and anyone copying the block inherits three dead controls. Each filter now has its own `useState` and `onChange`, matching the checkbox wiring already used in the Bottom Sheet Switcher showcase.diff --git a/.changeset/bottom-sheet-viewport-resize.md b/.changeset/bottom-sheet-viewport-resize.mdindex 6560b91244..ba74049d42 100644--- a/.changeset/bottom-sheet-viewport-resize.md+++ b/.changeset/bottom-sheet-viewport-resize.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] BottomSheet: a sheet resting at a detent now follows the viewport. Its detents were resolved to pixels at gesture time and never revisited, so rotating the device or resizing the window left the sheet frozen at the old geometry — a half-height sheet covering three quarters of a shorter window, and a peek detent whose slide-down could exceed the new viewport entirely, leaving a modal dialog on screen with no sheet in it. Snap fractions are also read from the layout viewport now, so the mobile keyboard no longer moves the detents out from under the sheet it is measuring.+[fix] BottomSheet: a sheet resting at a detent now follows the viewport. Its detents were resolved to pixels at gesture time and never revisited, so rotating the device or resizing the window left the sheet frozen at the old geometry — a half-height sheet covering three quarters of a shorter window, and a peek detent whose slide-down could exceed the new viewport entirely, leaving a modal dialog on screen with no sheet in it. Snap fractions are also read from the layout viewport now, so the mobile keyboard no longer moves the detents out from under the sheet it is measuring (#5159).@imdreamrunnerdiff --git a/.changeset/cli-theme-build-multi.md b/.changeset/cli-theme-build-multi.mdindex 6a0e54f340..b44d84da2c 100644--- a/.changeset/cli-theme-build-multi.md+++ b/.changeset/cli-theme-build-multi.md@@ -2,6 +2,6 @@'@astryxdesign/cli': patch----[feat] `astryx theme build` takes any number of theme files — `astryx theme build themes/*.ts` compiles them all in one process, so an app with several themes no longer hand-rolls a loop that re-enters the CLI once per theme. Outputs are byte-identical to the serial invocations; the run stops at the first failure and names the theme that failed. The CLI's Node floor (>=22.13) is now declared in `engines`, so a package manager can enforce it at install instead of the build failing later.+[feat] `astryx theme build` takes any number of theme files — `astryx theme build themes/*.ts` compiles them all in one process, so an app with several themes no longer hand-rolls a loop that re-enters the CLI once per theme. Outputs are byte-identical to the serial invocations; the run stops at the first failure and names the theme that failed. The CLI's Node floor (>=22.13) is now declared in `engines`, so a package manager can enforce it at install instead of the build failing later (#5121).@cixzhangdiff --git a/.changeset/datetime-input-icon-targets.md b/.changeset/datetime-input-icon-targets.mdindex 7987d3ff94..af9325b713 100644--- a/.changeset/datetime-input-icon-targets.md+++ b/.changeset/datetime-input-icon-targets.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] DateTimeInput: expose `date-time-input-toggle-icon` (calendar glyph, with open/closed `state`) and `date-time-input-clock-icon` (leading time glyph) theme targets, so a theme can size and color the leading icons — matching the `date-input-toggle-icon` seam DateInput already offers.+[feat] DateTimeInput: expose `date-time-input-toggle-icon` (calendar glyph, with open/closed `state`) and `date-time-input-clock-icon` (leading time glyph) theme targets, so a theme can size and color the leading icons — matching the `date-input-toggle-icon` seam DateInput already offers (#5148).@freddymetadiff --git a/.changeset/i18n-announce-strings.md b/.changeset/i18n-announce-strings.mdindex aff461a5cf..2ca61d1070 100644--- a/.changeset/i18n-announce-strings.md+++ b/.changeset/i18n-announce-strings.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Screen-reader announcements are now localizable. MultiSelector, Selector, Typeahead, FileInput, Tokenizer, and Lightbox spoke several live-region messages in hardcoded English — selection and result counts, file selections, token add/remove, and gallery position — so they stayed English under an `InternationalizationProvider`. They now resolve through the message catalog like the rest of the UI, and the counts use ICU plurals instead of appending an English "s", so locales with other plural rules read correctly.+[fix] Screen-reader announcements are now localizable. MultiSelector, Selector, Typeahead, FileInput, Tokenizer, and Lightbox spoke several live-region messages in hardcoded English — selection and result counts, file selections, token add/remove, and gallery position — so they stayed English under an `InternationalizationProvider`. They now resolve through the message catalog like the rest of the UI, and the counts use ICU plurals instead of appending an English "s", so locales with other plural rules read correctly (#4920).@nynexman4464diff --git a/.changeset/ime-composition-editable-fields.md b/.changeset/ime-composition-editable-fields.mdindex 4e6c00cae6..c2b3f45e90 100644--- a/.changeset/ime-composition-editable-fields.md+++ b/.changeset/ime-composition-editable-fields.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] The editable text fields in `Selector`, `MultiSelector`, `Typeahead`, `DateInput`, `DateTimeInput`, `TimeInput`, and `NumberInput` no longer misinterpret the keydown that commits or cancels an IME composition (Korean/Japanese/Chinese input) as a command. Previously a composing Enter would select/toggle the highlighted option or commit a typed date, a composing Escape would exit `Typeahead`'s edit mode, and a composing arrow would step a time or number value — all before the composition finished. Each field now lets the IME finish first, matching the guard already in place for `BaseTypeahead` and the Chat composer.+[fix] The editable text fields in `Selector`, `MultiSelector`, `Typeahead`, `DateInput`, `DateTimeInput`, `TimeInput`, and `NumberInput` no longer misinterpret the keydown that commits or cancels an IME composition (Korean/Japanese/Chinese input) as a command. Previously a composing Enter would select/toggle the highlighted option or commit a typed date, a composing Escape would exit `Typeahead`'s edit mode, and a composing arrow would step a time or number value — all before the composition finished. Each field now lets the IME finish first, matching the guard already in place for `BaseTypeahead` and the Chat composer (#4908).@cixzhangdiff --git a/.changeset/ime-guard-utils-home.md b/.changeset/ime-guard-utils-home.mdindex 4bc53f106f..fb964ab856 100644--- a/.changeset/ime-guard-utils-home.md+++ b/.changeset/ime-guard-utils-home.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[chore] `isImeKeyEvent` — the guard that stops an IME composition keystroke being read as a command — now lives at `@astryxdesign/core/utils` alongside the other pure helpers, with the reasoning for its two signals written down in one place. It stays exported from `@astryxdesign/core/hooks` for this release but is deprecated there: it is a plain predicate, not a hook, and that barrel is a `'use client'` boundary, so importing it from `hooks` pulls a server-safe function onto a client path. Move imports to `@astryxdesign/core/utils`; the `hooks` re-export will be removed in an upcoming major.+[chore] `isImeKeyEvent` — the guard that stops an IME composition keystroke being read as a command — now lives at `@astryxdesign/core/utils` alongside the other pure helpers, with the reasoning for its two signals written down in one place. It stays exported from `@astryxdesign/core/hooks` for this release but is deprecated there: it is a plain predicate, not a hook, and that barrel is a `'use client'` boundary, so importing it from `hooks` pulls a server-safe function onto a client path. Move imports to `@astryxdesign/core/utils`; the `hooks` re-export will be removed in an upcoming major (#4907).@nynexman4464diff --git a/.changeset/loud-broken-integration-manifest.md b/.changeset/loud-broken-integration-manifest.mdindex ef8020bce0..f3da45f21e 100644--- a/.changeset/loud-broken-integration-manifest.md+++ b/.changeset/loud-broken-integration-manifest.md@@ -2,7 +2,7 @@'@astryxdesign/cli': patch----[fix] An integration whose manifest fails to load is no longer silent. A manifest that throws on import — the common case being one still calling a `create*` authoring factory, removed in 0.3.0 — contributes nothing, and the CLI treated that as if the package had never been configured: `astryx discover` answered `No integrations configured.` while `astryx.config.mjs` plainly configured one, and no command said a word. The only way to find out was to already suspect it and run `validate-integration` by name. Meta's internal `@nest/xds-meta` sat invisible to CLI discovery for a week that way, and the app team's conclusion was that the components did not exist.+[fix] An integration whose manifest fails to load is no longer silent. A manifest that throws on import — the common case being one still calling a `create*` authoring factory, removed in 0.3.0 — contributes nothing, and the CLI treated that as if the package had never been configured: `astryx discover` answered `No integrations configured.` while `astryx.config.mjs` plainly configured one, and no command said a word. The only way to find out was to already suspect it and run `validate-integration` by name. Meta's internal `@nest/xds-meta` sat invisible to CLI discovery for a week that way, and the app team's conclusion was that the components did not exist (#5119).The load error now counts as an integration issue, so the existing one-line stderr nudge fires on `component`, `template` and `upgrade`, and `discover` — the command whose whole job is listing integrations — nudges too, as does `search`. `discover` also stops reporting `configured: false` for a project that configured an integration that failed to load; the empty state now distinguishes "you configured nothing" from "what you configured contributed nothing", which is the distinction `meta.configured` was introduced to carry.diff --git a/.changeset/promote-bottom-sheet-to-core.md b/.changeset/promote-bottom-sheet-to-core.mdindex 7a45cf8811..1ca2c45016 100644--- a/.changeset/promote-bottom-sheet-to-core.md+++ b/.changeset/promote-bottom-sheet-to-core.md@@ -3,6 +3,6 @@'@astryxdesign/core': patch----[component] Promote `BottomSheet` and `BottomSheetSwitcher` from the canary-only Lab package to Core. The stable package now includes their existing native-dialog, drag-detent, transition, and mobile-keyboard behavior, plus Core documentation and examples.+[component] Promote `BottomSheet` and `BottomSheetSwitcher` from the canary-only Lab package to Core. The stable package now includes their existing native-dialog, drag-detent, transition, and mobile-keyboard behavior, plus Core documentation and examples (#5080).@imdreamrunnerdiff --git a/.changeset/switch-hidden-label-gap.md b/.changeset/switch-hidden-label-gap.mdindex 896ec330e2..486fa656db 100644--- a/.changeset/switch-hidden-label-gap.md+++ b/.changeset/switch-hidden-label-gap.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `Switch` with `isLabelHidden` no longer reserves the label gap. The hidden label is `sr-only`, but its wrapper stayed a flex item, so the row still painted the 8px gap beside it: the field box measured 8px wider than the track it contains, and a hidden-label switch stopped 8px inside the edge every neighbouring control lined up on. The gap now collapses with the label, so the field is exactly as wide as the painted track — matching `CheckboxInput`, which already did this.+[fix] `Switch` with `isLabelHidden` no longer reserves the label gap. The hidden label is `sr-only`, but its wrapper stayed a flex item, so the row still painted the 8px gap beside it: the field box measured 8px wider than the track it contains, and a hidden-label switch stopped 8px inside the edge every neighbouring control lined up on. The gap now collapses with the label, so the field is exactly as wide as the painted track — matching `CheckboxInput`, which already did this (#5112).@cixzhangdiff --git a/.changeset/textarea-tooltip-status-pointer-events.md b/.changeset/textarea-tooltip-status-pointer-events.mdindex ec190ba36d..cd38d576d9 100644--- a/.changeset/textarea-tooltip-status-pointer-events.md+++ b/.changeset/textarea-tooltip-status-pointer-events.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Inputs (`statusVariant="tooltip"`): the focusable status button now opens its tooltip on hover inside `TextArea`, whose absolutely-positioned trailing slot is `pointer-events: none`. Keyboard focus already worked; pointer hover did not.+[fix] Inputs (`statusVariant="tooltip"`): the focusable status button now opens its tooltip on hover inside `TextArea`, whose absolutely-positioned trailing slot is `pointer-events: none`. Keyboard focus already worked; pointer hover did not (#5147).@freddymeta