@viraui/react 2026.6.3 → 2026.6.4

package/README.md

@@ -1,9 +1,7 @@
 <!-- PROJECT LOGO -->
 <br />
 <div align="center">
-  <h3 align="center" title="ViraUI">
-    <img alt="ViraUI" src="https://viraui.dev/viraui-logo-midgray.png" height="30" draggable="false" />
-  </h3>
+  <h1 align="center">ViraUI</h1>
   <br />
   <h2 align="center" style="font-weight: 500;">
     Ship real UI at the speed of thought.

package/dist/components/tabs/tabs-tab.js

@@ -14,6 +14,7 @@ var TabsTab = ({ addon, addonPosition = "start", children, className, ...otherPr
 	}),
 	...otherProps,
 	children: /* @__PURE__ */ jsx(Text, {
+		fluid: false,
 		tone: "muted",
 		whiteSpace: "nowrap",
 		className: tabs_module_default.Label,

package/dist/components/typewriter/typewriter.css

@@ -1 +1 @@
-@layer viraui.preflight, viraui.components, viraui.overrides;@layer viraui.components{@property --vui-typewriter-caret-color{syntax:"<color>";inherits:true;initial-value:currentcolor}.viraui__typewriter-module__Typewriter_R3sbb{position:relative;isolation:isolate}.viraui__typewriter-module__Ghost_R-Yy-{visibility:hidden;white-space:pre-wrap}.viraui__typewriter-module__Typed_00NZ8{white-space:pre-wrap}.viraui__typewriter-module__Typewriter_R3sbb[data-preserve-space]>.viraui__typewriter-module__Typed_00NZ8{position:absolute;inset-inline-start:0;inset-block-start:0}.viraui__typewriter-module__Caret_96Yfs{display:inline-block;vertical-align:initial;color:var(--vui-typewriter-caret-color);animation:viraui__typewriter-module__typewriter-caret-blink_yLCpV 1.1s step-start infinite;&[data-type=block]{inline-size:.55em;block-size:.95em;margin-inline-start:.04em;background-color:var(--vui-typewriter-caret-color);transform:translateY(.08em)}&[data-type=pipe]:before{content:"|"}&[data-type=underscore]:before{content:"_"}}.viraui__typewriter-module__A11y_B-rjF{position:absolute;inset-block-start:0;inset-inline-start:0;inline-size:1px;block-size:1px;padding:0;margin:-1px;overflow:hidden;clip-path:inset(50%);white-space:nowrap;border:0;pointer-events:none}@keyframes viraui__typewriter-module__typewriter-caret-blink_yLCpV{50%{opacity:0}}}
+@layer viraui.preflight, viraui.components, viraui.overrides;@layer viraui.components{@property --vui-typewriter-caret-color{syntax:"<color>";inherits:true;initial-value:currentcolor}.viraui__typewriter-module__Typewriter_R3sbb{position:relative;isolation:isolate}.viraui__typewriter-module__Typewriter_R3sbb[data-preserve-space]{display:flex}.viraui__typewriter-module__Ghost_R-Yy-{visibility:hidden;white-space:pre-wrap}.viraui__typewriter-module__Typed_00NZ8{white-space:pre-wrap}.viraui__typewriter-module__Typewriter_R3sbb[data-preserve-space]>.viraui__typewriter-module__Typed_00NZ8{position:absolute;inset-inline:0;inset-block-start:0}.viraui__typewriter-module__Caret_96Yfs{display:inline-block;vertical-align:initial;color:var(--vui-typewriter-caret-color);animation:viraui__typewriter-module__typewriter-caret-blink_yLCpV 1.1s step-start infinite;&[data-type=block]{inline-size:.55em;block-size:.95em;margin-inline-start:.04em;background-color:var(--vui-typewriter-caret-color);transform:translateY(.08em)}&[data-type=pipe]:before{content:"|"}&[data-type=underscore]:before{content:"_"}}.viraui__typewriter-module__A11y_B-rjF{position:absolute;inset-block-start:0;inset-inline-start:0;inline-size:1px;block-size:1px;padding:0;margin:-1px;overflow:hidden;clip-path:inset(50%);white-space:nowrap;border:0;pointer-events:none}@keyframes viraui__typewriter-module__typewriter-caret-blink_yLCpV{50%{opacity:0}}}

package/dist/specs/PROTOCOL.md

@@ -44,9 +44,10 @@ Prefer opening via package export / that `dist/specs/` tree. The `version` attri
 Consumer agents build screens **with** ViraUI — public parts, compounds, and props from the units — not **around** it with immediate CSS overrides.
 
 1. Index → activity load → open `meta` / `props` / `usage` for every Vira surface you touch **before** JSX that invents classNames or a CSS module targeting those roots.
-2. Prefer another Vira part or public prop over custom CSS (layout → `Stack`/`Grid`/`Masonry`/`Bleed`/`Surface`; fill → `fullWidth` / `expandChildren`; type → `Text`/`Title` props; chrome → `Surface` / `Elevator`).
-3. Custom CSS defaults to **app chrome the system does not own** (page backdrop image, document scrollport, one-off marketing layout). It is **not** a license to reshape Vira control geometry, reinvent owned props, or “fix” controls that already look correct under theme + preflight — **unless the consumer expressly requests** that override / personalization. A future override layer will own formal customization hooks; until then, still open `props`/`usage` first and apply only the asked CSS.
-4. If `usage.xml` lists a **dont** against the CSS you are about to write and the consumer did **not** expressly override that guidance — stop. Do not ship it.
+2. Prefer another Vira part or public prop over custom CSS (layout → `Stack`/`Grid`/`Masonry`/`Bleed`/`Surface`; fill → `fullWidth` / `expandChildren`; one-sided inset → `hPadding`/`vPadding` `[start, end]` tuples — not `paddingBlock*`/`paddingInline*` style; type → `Text`/`Title` props; chrome → `Surface` / `Elevator`).
+3. **Omit `render` when it restates the component’s default root.** Confirm the default in that surface’s `props`/`usage` (e.g. Stack → `div`). Do **not** write `render={<div />}` on Stack, or any other `render={<SameDefault />}` noop. Use `render` only to change the host (semantic tag, `Surface`, another component).
+4. Custom CSS defaults to **app chrome the system does not own** (page backdrop image, document scrollport, one-off marketing layout). It is **not** a license to reshape Vira control geometry, reinvent owned props, or “fix” controls that already look correct under theme + preflight — **unless the consumer expressly requests** that override / personalization. A future override layer will own formal customization hooks; until then, still open `props`/`usage` first and apply only the asked CSS.
+5. If `usage.xml` lists a **dont** against the CSS you are about to write and the consumer did **not** expressly override that guidance — stop. Do not ship it.
 
 Opening a CSS module on a Vira root without having opened that surface’s `props.xml` + `usage.xml` is a protocol defect. Unsolicited reshape CSS (no consumer ask) is the same defect.
 

package/dist/specs/activity-hints.xml

@@ -20,6 +20,7 @@
     <forbid>Opening every component props.xml in the package</forbid>
     <forbid>Writing unsolicited className / CSS module / utility styles on a Vira root before opening that surface props.xml and usage.xml</forbid>
     <forbid>Treating Vira controls as raw HTML to reshape without an express consumer request for override / personalization — compose with public parts and props first</forbid>
+    <forbid>Passing render that restates the component default root (e.g. Stack render={&lt;div /&gt;}; confirm default in props/usage) — omit render unless the host changes</forbid>
   </activity>
   <activity id="foundation-attrs">
     <description>Mode, vibrancy, elevation, grow/shrink hooks.</description>
@@ -63,6 +64,7 @@
       <step unit="usage" note="confirm stack/surface/grid (etc.) do/dont after pattern" />
       <step unit="props" note="verify spacing / render / fullWidth names" />
     </load>
-    <forbid>Inventing display:flex / display:grid / CSS gap/padding/border chrome when Stack, Grid, Masonry, Bleed, or Surface cover it</forbid>
+    <forbid>Inventing display:flex / display:grid / CSS gap/padding/paddingBlock*/paddingInline*/border chrome when Stack, Grid, Masonry, Bleed, or Surface cover it — one-sided inset → hPadding/vPadding [start, end] tuples</forbid>
+    <forbid>Passing render={&lt;div /&gt;} (or any render that matches the component default root) — omit render; use it only for a different host</forbid>
   </activity>
 </activity_hints>

package/dist/specs/components/grid/props.xml

@@ -24,7 +24,7 @@
     <description>Controls `repeat(auto-fill|auto-fit, …)` when `columns` is unset. Pass `false` to skip the filling data attribute.</description>
   </prop>
   <prop name="hPadding" kind="react">
-    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset — never `style`/`paddingInline*` CSS when this prop covers it.</description>
   </prop>
   <prop name="Item.column" kind="react">
     <description>Sets explicit `grid-column` placement via `--vui-grid-item-column`.</description>
@@ -63,7 +63,7 @@
     <description>Fixes the number of row tracks via `--vui-grid-rows`.</description>
   </prop>
   <prop name="vPadding" kind="react">
-    <description>Sets block padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets block padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset (e.g. bottom only `vPadding={[0, &apos;l&apos;]}`) — never `style`/`paddingBlock*` CSS when this prop covers it.</description>
   </prop>
   <prop name="column-gap" kind="css">
     <description>Grid column gap on the root.</description>

package/dist/specs/components/grid/usage.xml

@@ -8,7 +8,7 @@
   <do>Token-spaced grids with optional axis padding without custom grid CSS</do>
   <dont>Using Masonry when you need explicit row/column placement or full-width/full-height spans</dont>
   <dont>Re-declaring `grid-template` and `gap` in app CSS when Grid can own the layout</dont>
-  <dont>Inventing CSS `gap` / `padding` on this root when public spacing props cover it</dont>
+  <dont>Inventing CSS `gap` / `padding` / `paddingBlock*` / `paddingInline*` / side paddings (`style` or className) when public spacing props cover it — one-sided inset uses `hPadding`/`vPadding` `[start, end]` tuples</dont>
   <dont>Setting both `fullWidth` and `column` (or `fullHeight` and `row`) and expecting the explicit placement to win — full-* data attrs override</dont>
   <dont>Using Grid for simple one-axis flex spacing — prefer Stack</dont>
 </usage>

package/dist/specs/components/stack/props.xml

@@ -34,7 +34,7 @@
     <description>Aligns content on the horizontal axis from the consumer point of view.</description>
   </prop>
   <prop name="hPadding" kind="react">
-    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset — never `style`/`paddingInline*` CSS when this prop covers it.</description>
   </prop>
   <prop name="inline" kind="react">
     <description>Displays the stack as `inline-flex` instead of `flex`.</description>
@@ -58,7 +58,7 @@
     <description>Aligns content on the vertical axis from the consumer point of view.</description>
   </prop>
   <prop name="vPadding" kind="react">
-    <description>Sets block padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets block padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset (e.g. bottom only `vPadding={[0, &apos;l&apos;]}`) — never `style`/`paddingBlock*` CSS when this prop covers it.</description>
   </prop>
   <prop name="wrap" kind="react">
     <description>Allows direct children to wrap onto additional lines when space is constrained.</description>

package/dist/specs/components/stack/usage.xml

@@ -9,10 +9,11 @@
   <do>Semantic/native roots via `render` (`header`, `main`, `nav`, `section`, …) while keeping Stack as the layout engine</do>
   <do>Opt into `@container stack` with `enableContainer` when layout should follow this Stack&apos;s inline-size, not the viewport</do>
   <dont>Reaching for a plain wrapper `div` when Stack (optionally with `render` for a semantic tag) can own the box</dont>
+  <dont>Passing `render={&lt;div /&gt;}` (or any host that matches Stack&apos;s default root) — omit `render`; use it only for a different host (`header`, `Surface`, …)</dont>
   <dont>Assuming Stack expands direct children by default — pass `expandChildren` when children should grow on the flex main axis</dont>
   <dont>Using `expandChildren` to fill parent width under `hAlign=&quot;center&quot;` — that is `fullWidth` on the child Stack (self `inline-size`), not child flex-grow</dont>
   <dont>Inventing `width: 100%` / `inline-size: 100%` / `w-full` / `.fullWidth` / size-fill `className` on content-sized children when this Stack can own the fill — or when children are intentionally fixed-size (e.g. IconButton)</dont>
-  <dont>Inventing CSS `gap` / `padding` on this root when public spacing props cover it</dont>
+  <dont>Inventing CSS `gap` / `padding` / `paddingBlock*` / `paddingInline*` / side paddings (`style` or className) when public spacing props cover it — one-sided inset uses `hPadding`/`vPadding` `[start, end]` tuples (e.g. `vPadding={[0, &apos;l&apos;]}`), not `paddingBlockEnd: &apos;1rem&apos;`</dont>
   <dont>Putting `data-grow=&quot;false&quot;` on an ancestor to control nested `expandChildren` — set it on the child that should not grow</dont>
   <dont>Combining `fullWidth` with `inline` — prefer block flex when the root must fill parent inline size</dont>
   <dont>Using viewport media queries when `@container stack` against this Stack&apos;s inline-size matches the design intent</dont>

package/dist/specs/components/surface/props.xml

@@ -33,7 +33,7 @@
     <description>Sets the hover background on hover-capable pointers using a base ramp layer (`1`–`3`), a literal CSS value, or the named token `primary` (`data-surface-hover-color=&quot;primary&quot;`; CSS owns light/dark opacity via `--global-primary`).</description>
   </prop>
   <prop name="hPadding" kind="react">
-    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset — never `style`/`paddingInline*` CSS when this prop covers it.</description>
   </prop>
   <prop name="overflow" kind="react">
     <description>Sets root overflow through the `--vui-surface-overflow` custom property.</description>
@@ -48,7 +48,7 @@
     <description>Replaces the default `div` root using Base UI render semantics.</description>
   </prop>
   <prop name="vPadding" kind="react">
-    <description>Sets block padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets block padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset (e.g. bottom only `vPadding={[0, &apos;l&apos;]}`) — never `style`/`paddingBlock*` CSS when this prop covers it.</description>
   </prop>
   <prop name="background" kind="css">
     <description>Resting surface background on the root.</description>

package/dist/specs/components/surface/usage.xml

@@ -9,7 +9,7 @@
   <do>Inset content with `hPadding` / `vPadding` — nest Stack/Grid for child gaps</do>
   <do>Set `radius` to a token (or four-value tuple) on the outermost Surface that needs rounded corners; `radius=&quot;auto&quot;` on nested Surfaces for concentric corners</do>
   <dont>Passing `elevation={…}` on Surface — wrap with Elevator / `getElevationProps`</dont>
-  <dont>Inventing CSS `padding` / `gap` on this root when public padding props (and nested Stack) cover it</dont>
+  <dont>Inventing CSS `padding` / `paddingBlock*` / `paddingInline*` / `gap` (`style` or className) when public padding props (and nested Stack) cover it — one-sided inset uses `hPadding`/`vPadding` `[start, end]` tuples (e.g. `vPadding={[0, &apos;l&apos;]}`), not `paddingBlockEnd`</dont>
   <dont>Inventing `width: 100%` on Surface when a parent Stack `fullWidth` can own the fill</dont>
   <dont>Overwriting transition shorthand without composing box-shadow when `data-elevation` is present</dont>
   <dont>Assuming `hoverColor` applies on touch devices</dont>

package/dist/specs/components/text/props.xml

@@ -30,7 +30,7 @@
     <description>Overrides font width as a percentage (100 = normal); maps to `font-stretch` and `wdth`.</description>
   </prop>
   <prop name="hPadding" kind="react">
-    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset — never `style`/`paddingInline*` CSS when this prop covers it.</description>
   </prop>
   <prop name="lineHeight" kind="react">
     <description>Controls line height through foundation leading tokens.</description>
@@ -69,7 +69,7 @@
     <description>Selects the `text-box` trim basis when `trim` is active.</description>
   </prop>
   <prop name="vPadding" kind="react">
-    <description>Sets block padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets block padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset — never `style`/`paddingBlock*` CSS when this prop covers it.</description>
   </prop>
   <prop name="weight" kind="react">
     <description>Selects a semantic weight keyword or a numeric weight (`font-weight` + `wght` axis).</description>

package/dist/specs/components/text/usage.xml

@@ -9,6 +9,6 @@
   <do>Ellipsis: ClampText `render={&lt;Text … /&gt;}` — FitText when copy must scale to fill width instead of truncate</do>
   <do>Letter-spacing via `tracking`; text-transform via `transform`; width via `maxWidth` or parent Stack `fullWidth`</do>
   <dont>Using Text for headings — use Title (`render` for h1–h6)</dont>
-  <dont>Inventing CSS `letter-spacing` / `text-transform` / `width: 100%` when `tracking` / `transform` / Stack `fullWidth` cover it</dont>
+  <dont>Inventing CSS `letter-spacing` / `text-transform` / `width: 100%` / `paddingBlock*` / `paddingInline*` when `tracking` / `transform` / Stack `fullWidth` / `hPadding`/`vPadding` tuples cover it</dont>
   <dont>Setting body color with raw `--global-*` when `tone` covers the role</dont>
 </usage>

package/dist/specs/components/title/props.xml

@@ -28,7 +28,7 @@
     <description>Overrides font width as a percentage (100 = normal); maps to `font-stretch` and `wdth`.</description>
   </prop>
   <prop name="hPadding" kind="react">
-    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets inline padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset — never `style`/`paddingInline*` CSS when this prop covers it.</description>
   </prop>
   <prop name="lineHeight" kind="react">
     <description>Controls line height through foundation leading tokens.</description>
@@ -64,7 +64,7 @@
     <description>Selects the `text-box` trim basis when `trim` is active.</description>
   </prop>
   <prop name="vPadding" kind="react">
-    <description>Sets block padding using one token for both sides or a `[start, end]` tuple.</description>
+    <description>Sets block padding using one token for both sides or a `[start, end]` tuple (`0` allowed). Prefer the tuple for one-sided inset — never `style`/`paddingBlock*` CSS when this prop covers it.</description>
   </prop>
   <prop name="weight" kind="react">
     <description>Overrides the size preset weight (`font-weight` + `wght` axis).</description>

package/dist/specs/components/title/usage.xml

@@ -9,5 +9,5 @@
   <do>Letter-spacing via `tracking`; text-transform via `transform`; width via `maxWidth` or parent Stack `fullWidth`</do>
   <dont>Assuming `size` changes the HTML tag — choose `render` explicitly</dont>
   <dont>Using Title for long body paragraphs — use Text</dont>
-  <dont>Inventing CSS `letter-spacing` / `text-transform` / `width: 100%` when props / Stack cover it</dont>
+  <dont>Inventing CSS `letter-spacing` / `text-transform` / `width: 100%` / `paddingBlock*` / `paddingInline*` when props / Stack / `hPadding`/`vPadding` tuples cover it</dont>
 </usage>

package/dist/specs/components/typewriter/usage.xml

@@ -2,6 +2,7 @@
 <usage surface="typewriter">
   <do>Nest inside Title or Text so size/tone/heading `render` live on the parent — Typewriter stays decorative typed copy</do>
   <do>Hero / marketing phrase cycles via `texts` + `preserveSpace` so layout holds through type/delete (see auth Title compose)</do>
+  <do>Wrapped `preserveSpace` copy: keep phrase lengths similar so reserved height stays honest across the cycle</do>
   <do>Caret via `caret` / `caretColor`; timing via `speed` / `deleteSpeed` / `pause` / `delay` / `loop`</do>
   <do>Loading shimmer on static copy is Shimmer inside Text/Title — Typewriter when progressive letter reveal is the intent</do>
   <dont>Using Typewriter as the only source of critical status without a labeled surrounding region</dont>

package/dist/specs/index.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<index package="@viraui/react" version="2026.6.3" generated="2026-09-25T13:06:12.744Z">
+<index package="@viraui/react" version="2026.6.4" generated="2026-10-01T09:52:11.032Z">
   <categories>
     <category id="layout" />
     <category id="action" />

package/dist/specs/patterns/compose-layout-first.xml

@@ -10,7 +10,7 @@
     <ref id="bleed" units="meta,usage" />
   </uses>
   <do>Prefer Vira layout roots (`Stack`, `Grid`, `Masonry`, `Bleed`, `Surface`) and their public props for every consumer layout. Treat `Stack` as the default box: an enriched `div` (flex + gap/padding/align/`fullWidth`/`render`/…) — prefer it over bare wrapper `div`s even for simple nesting. Compose **with** these parts; default custom CSS = **app chrome** the system does not own. Prefer another Vira component (e.g. `Surface` for border/fill/radius) or `render` merge over a CSS class for chrome the library already owns. Do not open a CSS module to reshape a Vira control unless the consumer **expressly asked** for that override (still read `props`/`usage` first; a future override layer will formalize hooks).</do>
-  <dont>Do not invent bare wrapper `div`s (or `display:flex` / `display:grid` / CSS `gap` / `padding` / `width` / `inline-size` / border/radius chrome on raw tags or Vira control roots) when `Stack` or another layout primitive / `Surface` / a public `fullWidth` prop covers it. Do not skip composition to reach for a one-off stylesheet — including size-fill classNames that would do nothing on fixed-size controls.</dont>
+  <dont>Do not invent bare wrapper `div`s (or `display:flex` / `display:grid` / CSS `gap` / `padding` / `paddingBlock*` / `paddingInline*` / `width` / `inline-size` / border/radius chrome on raw tags or Vira control roots) when `Stack` or another layout primitive / `Surface` / a public `fullWidth` or `hPadding`/`vPadding` tuple covers it. Do not skip composition to reach for a one-off stylesheet — including size-fill classNames that would do nothing on fixed-size controls. Do not pass `render` that restates a component&apos;s default root (e.g. Stack `render={&lt;div /&gt;}`) — omit `render` unless the host changes.</dont>
   <tsx><![CDATA[
 {/* Flex row + panel chrome: one DOM node via Stack render={<Surface />} */}
 <Stack

package/dist/specs/patterns/page-chrome.xml

@@ -6,7 +6,7 @@
     <ref id="button" units="meta" />
   </uses>
   <do>Own page/section flex with Stack. Pick semantic tags (`header`, `main`, `nav`, `section`, …) via `render={&lt;tag /&gt;}` — keep Stack as the layout engine. CSS modules may set min-block-size / scroll; never `display:flex`.</do>
-  <dont>Do not use raw `header`/`main`/`nav` + `display:flex` / CSS gap for jobs Stack owns. Tag choice ≠ layout engine.</dont>
+  <dont>Do not use raw `header`/`main`/`nav` + `display:flex` / CSS gap for jobs Stack owns. Tag choice ≠ layout engine. Do not pass `render={&lt;div /&gt;}` — Stack already defaults to `div`; omit `render` unless the host changes.</dont>
   <tsx><![CDATA[
 <Stack rowGap="m" expandChildren>
   <Stack

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@viraui/react",
-  "version": "2026.6.3",
+  "version": "2026.6.4",
   "private": false,
   "files": [
     "dist"
@@ -28,7 +28,7 @@
   },
   "devDependencies": {
     "@base-ui/react": ">=1.8.0",
-    "@viraui/foundation": "2026.6.3",
+    "@viraui/foundation": "2026.6.4",
     "@viraui/icons": "2026.1.0",
     "@viraui/postcss-config": "2026.0.0",
     "@viraui/tsconfig": "2026.0.0",