33 Releases·Semantic Versioning

Changelog

Every update to @7onic-ui/react and @7onic-ui/tokens, documented.

v0.3.202026-11-11
@7onic-ui/react1 changes
Fixed1
  • ChatInputField no longer submits while an IME is composing. Pressing Enter to confirm a Korean, Japanese or Chinese composition sent the message before the last character was committed, and that character was then left in the field to be sent again as a second message. Enter now submits only after the composition ends (isComposing, plus keyCode 229 for Safari, which reports isComposing as false on the confirming Enter). Shift+Enter still inserts a line break.
v0.3.192026-11-10
@7onic-ui/tokens4 changes
Fixed4
  • Component animations now stop under `prefers-reduced-motion: reduce`. variables.css defines the .animate-* classes outside any cascade layer, so in Tailwind v4 they always won over motion-reduce:animate-none and every enter/exit animation kept playing for users who asked for reduced motion. 50 of the 55 animations now turn off (Modal, Drawer, Popover, Tooltip, Toast, Accordion, NavigationMenu, Checkbox, RadioGroup, fade, Skeleton, Progress stripes, typing cursor): variables.css ships a reduced-motion block for the plain classes, and the Tailwind v3 preset and v4 theme carry the same rule inside each animate-* utility, so variant classes such as data-[state=open]:animate-drawer-right-enter are covered too. The final state shows at once and closing still unmounts. It works the same with Tailwind v3, Tailwind v4 and plain CSS.
  • Loading indicators keep running. animate-spin and animate-spinner-orbit / -dot / -bar / -morph are left on, because a stopped spinner reads as "frozen".
  • Keeping one animation on. Override it in your own CSS with !important inside @media (prefers-reduced-motion: reduce). An animate-* utility cannot switch it back on, with or without !.
  • npx sync-tokens generates the same block from your own figma-tokens.json.
@7onic-ui/react2 changes
Fixed2
  • TypingIndicator stops and dims under reduced motion. The component already carried motion-reduce:animate-none, but the class lost to the unlayered .animate-* rule and the dots kept pulsing. It now uses the important modifier, so the dots and the cursor stop at 60% opacity as documented.
  • Skeleton `animation="wave"` hides its shimmer under reduced motion. With the animation off the shimmer would stay as a still stripe across the placeholder.
v0.3.182026-11-06
@7onic-ui/react4 changes
Added2
  • `statusLabels` on ChatMessageFooter. The built-in statuses always showed "Sending...", "Sent", "Read" and "Failed" in English. Pass the page language, for example statusLabels={{ sent: '送信済み', read: '既読' }}. Keys you leave out keep the English text, and the built-in colors still apply.
  • `srLabel` on MetricCardTrend. Screen readers always heard "Increased", "Decreased" or "No change" in English. Pass the page language, for example srLabel="増加". Without it, the English text for each direction stays.
Fixed2
  • A closing animation on DropdownMenuContent now plays. A context provider sat between the menu portal and the content, so Radix could not see the content element and removed the menu at once on close. An animation you add with className (for example on data-[state=closed]) now runs before the menu is removed. The menu still has no animation of its own.
  • AvatarFallback `colorVariant="soft"` text is easier to read in red and orange. Two of the twelve colors were below the 4.5:1 contrast ratio on their pastel background (orange 3.11, red 3.95). The text is now one step darker: orange #C2410C (4.52) and red #B91C1C (5.30). The color each name gets does not change.
v0.3.172026-11-06
@7onic-ui/react2 changes
Fixed2
  • DropdownMenu no longer scrolls the page when it returns focus after a keyboard close. In 0.3.16 the trigger was focused without preventScroll, so a trigger in a sticky header pulled the page up (Escape at 1200px went back to about 770px, and a menu item linking to an anchor stopped short of it). Focus still returns to the trigger, and the scroll position stays.
  • Menu items no longer show your project's link or button focus outline on hover. DropdownMenu items (including checkbox, radio and submenu items) and Select items moved real focus on hover, so a project-wide a:focus-visible or button:focus-visible outline drew a box around the hovered item, for example an asChild link. The highlight background stays the focus indicator for mouse and keyboard.
v0.3.162026-11-06
@7onic-ui/react3 changes
Added1
  • `closeLabel` on Alert, DrawerContent, ModalContent, PopoverContent and Toaster. The built-in close (X) button was always announced as "Close" by screen readers, even on Japanese or Korean pages. Pass the page language, for example closeLabel="閉じる". The default stays 'Close'.
Fixed2
  • DropdownMenu and Select return focus to the trigger after a keyboard close. Closing with Escape, Enter or Space left focus on the page body, so the next Tab started from the top of the page. Focus now returns to the trigger and shows the focus ring. After a mouse close, nothing changes: focus is not moved and no ring appears.
  • Segmented shows the focus ring on the selected item. The selected item's shadow replaced the keyboard focus ring. The ring now shows while the selected item has keyboard focus.
v0.3.152026-11-02
@7onic-ui/react1 changes
Fixed1
  • `asChild` keeps the component styles on Button, IconButton, Badge and vertical NavigationMenuLink. With asChild these components passed several children (icons, a dot, wrappers and your element) to the slot, so the classes never reached your element: <Button asChild><a> rendered a plain unstyled link, and Badge or a vertical NavigationMenuLink threw React.Children.only. Icons, the status dot and the text wrapper are now placed inside your element, which receives the component classes. Without asChild the rendered HTML is unchanged. With asChild, Badge does not render the removable button, because a button inside a link is invalid HTML.
v0.3.142026-10-30
@7onic-ui/react1 changes
Fixed1
  • Breadcrumb `maxItems` collapses in Server Components. In 0.3.13 the list only collapsed when it was rendered in a Client Component. Children passed from a React Server Component (the Next.js App Router default) and items wrapped in your own component were not recognized, so every item stayed visible. Items and separators are now also identified by their alternating order, and the server-rendered HTML is already collapsed.
v0.3.132026-10-29
@7onic-ui/react1 changes
Fixed1
  • Breadcrumb `maxItems` now collapses the list. maxItems, itemsBeforeCollapse and itemsAfterCollapse were documented but had no effect, and were passed through to the <nav> element. When there are more items than maxItems, BreadcrumbList now keeps the first itemsBeforeCollapse (default 1) and last itemsAfterCollapse (default 1) items and replaces the rest with one ellipsis item. Your own separators are reused, and items rendered as <Fragment>{separator}{item}</Fragment> from a list are counted too.
v0.3.122026-10-29
@7onic-ui/tokens3 changes
Added1
  • `gray-dark` palette (`primitive.color.gray-dark.50`–`900`) — a dark-mode-only neutral scale. Dark semantic tokens (background, text, border, disabled, secondary.tint, warning.text) now reference it instead of reusing the light gray scale in reverse. Changing light grays through token sync no longer changes dark-mode text.
Changed1
  • Dark mode surfaces and text. Background #222225 → #18181B, paper #232327, muted #2C2C30, elevated #343438; muted text #9C9C9D (4.5:1 or more on every dark surface); subtle text #818182; borders #3B3B40 / subtle #2C2C30 / strong #55555A. Light mode is unchanged. Projects that sync their own figma-tokens.json keep their current colors until they add gray-dark.
Fixed1
  • `sync-tokens` generates palettes whose name contains a hyphen. Tailwind v3 preset and type definitions now quote keys like 'gray-dark', and the v3 / v4 palette lists include gray-dark.
v0.3.112026-10-29
@7onic-ui/react10 changes
Fixed7
  • Checkboxes and switches in one `Field` each toggle from their own label. A Checkbox or Switch inside a Field took the Field's id, so several of them shared one id: clicking the label "SMS" toggled the first checkbox, and assistive technology could not tell the items apart. A Checkbox / Switch with its own label (or startLabel / endLabel) now keeps a unique id, and the Field becomes role="group" named by its FieldLabel; the group title no longer points at a single input. A bare Checkbox / Switch (no label) still takes the Field id, as before. No visual change.
  • `RadioGroup` inside a `Field` is named by the `FieldLabel`. The label used to point at an id no element had; the radio group now references it with aria-labelledby.
  • `Select` connects to `Field`. Inside a Field, SelectTrigger takes the Field id (so FieldLabel names it) and Select inherits the Field's disabled state, as Input and Textarea do. Previously neither happened, although the docs said they did.
  • `Slider` can be given an accessible name. aria-label / aria-labelledby were applied to the root element, but screen readers read the thumb (role="slider"), which had no name. They now go on the thumb(s); inside a Field the FieldLabel names the slider automatically.
  • `PaginationItems` renders a valid list. The page items were wrapped in a display: contents <div> inside PaginationContent's <ul>, which breaks list semantics for assistive technology. The items now render directly into the list. The component still accepts its former props and ref, which have no element to attach to any more. No visual change.
  • Vertical `NavigationMenu`: `NavigationMenuGroup` keeps the list structure valid. The group (<div role="group">) sat directly inside NavigationMenuList's <ul>; it is now wrapped in an <li>, and a group with a label is named by it. Spacing between groups is unchanged.
  • NavigationMenuItem closes its sub-menu when the menu collapses without an extra render pass, and ChatInputField merges refs through a helper; both behave as before and no longer trip the React Compiler lint rules.
Changed3
  • Input and Textarea register with their Field so a FieldLabel keeps pointing at them when a Field also holds labelled checkboxes. Existing single-input Fields render the same markup as before.
  • llms.txt: the Field section describes how single controls, groups, RadioGroup and Slider are labelled, and the Slider section documents aria-label on the thumb.
  • llms.txt: the Pagination compound example wraps PaginationPrevious / PaginationNext in PaginationItem, as the docs site does. The old example put buttons directly inside the <ul>, which is not a valid list.
v0.3.102026-10-27
@7onic-ui/react3 changes
Fixed1
  • Tree-shaking now works for the ESM build. Through 0.3.9 the ESM output was a single file, and bundlers keep most of a single file because top-level forwardRef, cva and displayName assignments count as side effects. Measured in a Vite + Tailwind v4 app, importing only Button added 332 KB on top of React — almost the whole library (368 KB). The ESM build is now split per component with shared chunks, so importing Button alone adds 28 KB. Import paths (@7onic-ui/react, @7onic-ui/react/chart), the CommonJS build, type declarations and 'use client' behavior for React Server Components are unchanged. This makes the "only the components you import ship" note in 0.3.0 hold.
Added1
  • @7onic-ui/react/package.json is exported, so tools that read a package's version (require('@7onic-ui/react/package.json')) no longer fail with ERR_PACKAGE_PATH_NOT_EXPORTED.
Changed1
  • llms.txt (shipped in the package) lists sub-components by their exported names (PopoverTrigger, TooltipProvider, …) instead of the dot notation removed in 0.3.0. The CLI guide (llms-cli.txt on the docs site) no longer describes a dot-notation pattern that would fail at render; it points to the Compound Recipe instead.
@7onic-ui/tokens1 changes
Added1
  • @7onic-ui/tokens/package.json is exported, for the same reason.
v0.3.92026-10-27
@7onic-ui/react4 changes
Fixed4
  • Select and Dropdown menus no longer open behind a Modal, Drawer or Popover. Their content used the z-dropdown layer (1000), which sits below z-modal (2000) and z-popover (2100), so a Select or Dropdown placed inside one of those opened underneath it and could not be used. Select and Dropdown content now use the z-popover layer; within the same layer the most recently opened element stays on top. z-dropdown is now used only by NavigationMenu sub-menus. No token values changed.
  • Chart tooltip: label and value no longer touch. ChartTooltipContent rows had no minimum spacing, so a long series label ran straight into a four-digit value. Rows now keep gap-4 between the label and the value.
  • Popover no longer runs off the bottom of the screen. PopoverContent now stops at the space left in the viewport and scrolls its content inside, while the arrow stays visible. Children are wrapped in an inner scroll area, so put layout classes (flex, grid, gap-*) on your own child element rather than on PopoverContent.
  • Tabs: no focus ring after a mouse click. Radix Tabs 1.2+ focuses the trigger from script on mouse down, so after any keyboard input a clicked tab showed the keyboard focus ring. TabsTrigger now shows the ring only for keyboard navigation (Tab and arrow keys).
@7onic-ui/tokens0 changes
v0.3.82026-10-22
@7onic-ui/react1 changes
Fixed1
  • Removed next-intl and jsonc-parser from the published dependencies. Neither is imported by the library (both are docs-site / CLI build tooling), but since 0.3.0 they were installed into every project — and next-intl's required peer pulled a full Next.js install even into Vite apps. A fresh Vite + @7onic-ui/react install drops from ~381 MB / 173 packages to ~51 MB / 132 packages. No code or API change; the shipped dist/ is byte-identical.
@7onic-ui/tokens0 changes
v0.3.72026-10-07
@7onic-ui/react3 changes
Added1
  • llms.txt / llms-full.txt / llms-cli.txt: MCP server pointer in the header — one-command Claude Code plugin install (claude plugin marketplace add itonys/7onic && claude plugin install 7onic-design@7onic) and docs link (https://7onic.design/components/mcp)
Fixed2
  • llms.txt / llms-full.txt documentation fixes: Badge radius documented a non-existent xl value and omitted base (now matches badgeVariants); Chart example was missing Chart in its import line; DropdownMenu.RadioGroup was absent from the DropdownMenu sub-component list
  • llms-full.txt structure: the 4 AI components (TypingIndicator, QuickReply, ChatInput, ChatMessage) moved from SECTION 5 into SECTION 3 under a new "AI Components" category (section title count corrected to 41 measured headers)
@7onic-ui/tokens1 changes
Fixed1
  • cli/sync.js generator comments realigned with the committed variables.css output — re-running npx sync-tokens no longer regresses two comment lines (idempotency drift)
v0.3.62026-04-29
@7onic-ui/react3 changes
Changed3
  • `llms.txt` — lucide-react clarification — Added explicit note that lucide-react is NOT a @7onic-ui/react dependency. 7onic components use inline SVG internally. Users who want lucide icons in their own app code must install separately: npm install lucide-react. Prevents confusion when following Icon Import Pattern examples in LLM-assisted workflows.
  • Installation guide page — Vite boilerplate cleanup section — Updated install documentation to clarify that npx 7onic init on a Vite project automatically removes the npm create vite default CSS boilerplate (src/index.css + src/App.css), with .bak backups preserved. Removed outdated assumption that postcss.config uses .cjs extension (official Vite scaffolding uses .js).
  • CLI `init` documentation — steps simplified (11 → 6) — The init flow documentation now presents 6 user-facing steps instead of 11 internal steps: (1) auto-detect framework/TypeScript/Tailwind, (2) Vite @/ alias setup, (3) base deps install, (4) token CSS import, (5) boilerplate cleanup with .bak backup, (6) cn() utility + 7onic.json generation. Identical CLI behavior, clearer user-facing presentation.
@7onic-ui/tokens0 changes
v0.3.52026-04-28
@7onic-ui/tokens2 changes
Fixed2
  • Body Baseline `color` — Figma direct reference (SSOT) — html body { color } previously resolved through the --foreground Next.js compat alias (v0.3.4 workaround). Now references var(--color-text) directly, the Figma-defined token in themes/light.css (gray-900) and themes/dark.css (gray-100). Behavioral result identical (both produce the same color), but Figma SSOT is honored without alias indirection. Why this matters: variables.css is distributed standalone (Tailwind v3 users, no-Tailwind users) where --color-foreground (Tailwind v4 alias) is not defined; using --color-text guarantees the variable is defined in every supported import combination because themes/light.css + themes/dark.css always ship with variables.css.
  • `scripts/sync-tokens.ts` generator regression (v0.3.3 carry-over) — The internal generator was still emitting color: var(--color-foreground) (the original v0.3.3 bug). Output file variables.css had been manually patched in v0.3.4 to var(--foreground), but the generator was never synced. Re-running npm run sync-tokens would have silently regenerated variables.css with the v0.3.3 IACVT bug (light-mode invisible text under OS dark mode). Generator now emits var(--color-text), matching the output file. Verification: npm run sync-tokens after the fix reports 1 updated, 12 unchanged on first run, then 0 updated, 13 unchanged on subsequent runs (idempotent).
Note on v0.3.4 wording0
    @7onic-ui/react0 changes
    v0.3.42026-04-27
    @7onic-ui/tokens1 changes
    Fixed1
    • Body Baseline `color` typo — html body { color: var(--color-foreground) } referenced an undefined variable (--color-foreground does not exist; --foreground does). When OS is dark mode and the site forces light mode, the invalid declaration caused color to inherit the browser's system text color (white) from html:root { color-scheme: light dark }, making all text without an explicit color class invisible on light backgrounds. Fixed by correcting to var(--foreground).
    @7onic-ui/react1 changes
    Fixed1
    • `ChatMessage` flat variant — explicit `text-foreground` — getBubbleColors returned no text color class for variant="flat", relying on CSS inheritance. Consistent with the bubble variant (which always sets text-foreground), flat now explicitly sets text-foreground for all colors, making it self-contained regardless of parent context.
    v0.3.32026-04-24
    @7onic-ui/tokens2 changes
    Fixed1
    • Monospace font baseline — html body code, html body pre, html body kbd now explicitly set font-family: var(--font-family-mono). Prevents browser default monospace from overriding the token-defined mono font in documentation and code snippets.
    Improved1
    • `llms.txt` font baseline documentation — Added "Font baseline (automatic)" section explaining that variables.css auto-applies html body font-family-sans and code/pre/kbd font-family-mono. AI should not add manual body { font-family } rules.
    @7onic-ui/react2 changes
    Improved2
    • `llms.txt` font loading instructions — Per-framework detail for custom fonts (Next.js: next/font/google, Vite/Remix: Fontsource or CDN) and CJK font setup (noto-sans-jp/kr).
    • `llms.txt` Quick Reference Table note — Clarifies 40 table entries vs 42 documentation pages (4 chart types share one source; field is a form utility sub-component).
    v0.3.22026-04-23

    > **Critical patch** — Fixes v0.3.1 circular reference regression + Next.js font-family override + Vite CLI auto-cleanup. Users on v0.3.1 must upgrade.

    @7onic-ui/react & @7onic-ui/tokens4 changes
    Fixed2
    • v0.3.1 circular CSS variable reference — variables.css had --foreground: var(--color-foreground) and Next.js @theme inline emitted --color-foreground: var(--foreground), creating an infinite loop that browsers resolve to unset. Fixed by Approach Z: single-direction chain — --foreground now points to --color-text (safe island variable) instead of --color-foreground. No breaking change for users.
    • Next.js 15 + Vite font-family override — Next.js create-next-app template ships with body { font-family: Arial, Helvetica, sans-serif } unlayered. Vite ships with :root { font-family: system-ui, Avenir, ... }. Both override our Inter token. Fixed by adding font-family: var(--font-family-sans) to existing html body baseline block in variables.css (specificity 0,0,2 > body 0,0,1).
    Changed2
    • tokens/css/reset.css — removed as separate file. The html body baseline (background-color, color, font-family, display, margin, etc.) is now embedded directly in variables.css at the end (Body Baseline section). Bundle files (all.css, tailwind/v4.css) no longer import reset.css. Users importing variables.css get the baseline automatically. Distribution file count: 12 → 11.
    • tokens/package.json exports — ./css/reset.css subpath export removed.
    @7onic/cli0 changes
    v0.3.12026-04-23

    > **Critical patch** — Fixes Next.js 15 + Vite framework template compatibility. All three issues were 100% reproducible on v0.3.0. Users on v0.3.0 should upgrade.

    @7onic-ui/react & @7onic-ui/tokens11 changes
    Fixed3
    • Next.js 15 + Tailwind v4 light/dark mode broken — compiled CSS showed .bg-background { background-color: var(--background) } referencing Next.js template variable (OS dark mode forced #0a0a0a) instead of our token. data-theme="light" toggle was silently overridden. Fixed by html:root alias in variables.css — cascade specificity wins regardless of source order.
    • Vite + Tailwind v4/v3 body layout broken — Vite template's body { display: flex; place-items: center; min-width: 320px } force-centered all content. Fixed by html body baseline in new reset.css — overrides with higher specificity.
    • Vite + Tailwind v3 UI not rendering — CLI CSS_V3_IMPORTS was missing @tailwind base/components/utilities directives, so v3 generated zero utility classes. Fixed by adding directives to CLI v3 imports (see 7onic CLI 0.1.10).
    Added4
    • tokens/css/reset.css — new bundled file. Framework template baseline. Applies html body { background-color; color; display:block; place-items:initial; min-width:auto; margin:0 }. Bundled into all.css and tailwind/v4.css — users importing either bundle automatically get the reset. Selector specificity (0,0,2) > body (0,0,1) wins over Vite/Next.js template defaults. Override paths: (1) Tailwind class on <body> — .flex (0,1,0) wins, (2) same-selector CSS after our import — source order wins, (3) skip bundle + import individual files for complete opt-out.
    • tokens/css/variables.css — html:root { --background: var(--color-background); --foreground: var(--color-foreground) } alias block appended at end. Specificity (0,1,1) wins over Next.js default :root { --background: #fff } (0,1,0) without source order dependency. Makes Next.js's @theme inline { --color-background: var(--background) } convention automatically flow through our semantic tokens.
    • tokens/package.json exports — ./css/reset.css subpath export added.
    • Distribution file count: 11 → 12 (reset.css added).
    Changed2
    • npx sync-tokens (and internal npm run sync-tokens) now shows per-file status after generation: (NEW) for files created for the first time, (updated) for files whose content changed, (unchanged) for identical regenerations. Top-line summary also shows counts — ✅ sync-tokens complete: 1 new, 3 updated, 10 unchanged. Makes v0.3.0 → v0.3.1 upgrade transparent (users see reset.css (NEW) + bundle files (updated)) and alerts users who modified generated files directly (against the "Never modify generated files" rule) before their changes get overwritten. Info-level log only — no prompt added (follows npm / cargo / pip convention for additive changes). Breaking Changes (W3 — removed or renamed CSS variables) still prompt y/n as before.
    • @7onic-ui/react — no code changes; version bumped to maintain sync with @7onic-ui/tokens.
    Architecture Decision1
    • New ADR docs/decisions/NEXTJS-FRAMEWORK-COMPAT-STRATEGY.md — documents the problem mechanism (@theme inline override cascade), 6 considered alternatives, chosen solution, 4-scenario CSS cascade proof, and industry comparison (shadcn/HeroUI/Radix/Mantine/Chakra/DaisyUI).
    Why this is uniquely 7onic1
    • Industry first combination of 4 properties simultaneously: zero-config install (import → done), no React Provider wrapper, preserves user's globals.css (no file replacement), and standard Tailwind naming (bg-background, text-foreground). No existing library satisfies all four — shadcn wipes globals.css, HeroUI/Radix require Provider + namespaced vars, Mantine/Chakra use CSS-in-JS.
    v0.3.02026-04-22
    @7onic-ui/react & @7onic-ui/tokens26 changes
    Breaking Changes4
    • Compound JSX removed — use Named imports. <Card.Header /> → <CardHeader />
    • TypeScript namespace types removed — Card.HeaderProps → CardHeaderProps
    • Applies to all 25 compound namespaces (Card, Modal, Drawer, Tabs, Accordion, etc.)
    • Rollback if needed: npm dist-tag add @7onic-ui/react@0.2.9 latest
    Migration3
    • import { Card, CardHeader, CardTitle } from '@7onic-ui/react'
    • <Card><CardHeader><CardTitle>...</CardTitle></CardHeader></Card>
    • Prefer dot-notation? Add a Compound Recipe wrapper in your project ('use client' required). All 25 wrappers documented in the migration ADR
    Why4
    • Same behavior everywhere — Named imports work identically in RSC, Client Components, Pages Router, Vite, CRA, CJS. Compound JSX previously broke inside Next.js App Router Server Components
    • Reliable tree-shaking — Named exports map 1:1 to dead-code elimination; only the sub-components you import ship to the bundle
    • Simpler maintenance — adding a sub-component is now one export, not three synchronized locations
    • AI-ready — AI tools no longer randomly emit compound syntax that crashes in RSC
    Source2
    • 24 compound component files rewritten as shadcn-style Named-export-only. No more Object.assign, namespace X {}, or runtime *Root aliases
    • Radix Dialog accessibility fix: added DialogTitle to 5 Modal sidebar examples that were missing it
    Fixed — Playground code output matches rendered JSX 1:15
    • Playground previously shipped unused imports. Dropdown simple menu imported 14 sub-components while using only 5. Users who copy-pasted got noUnusedLocals warnings
    • Import list now derived from the rendered JSX body at generation time. Generated code contains exactly the identifiers used — no more, no less
    • All 42 Playground pages refactored to this pattern. Over-imports are now structurally impossible
    • Chart pages had a mirror bug in the other direction — hardcoded { Chart } only, but rendered 6–8 sub-components. Imports now auto-grow with the JSX
    • Static example fixes: pagination usePagination hook missing useState; typing-indicator had unused useState; quick-reply icon / FAQ examples missing the 7onic import
    Verified3
    • End-to-end browser audit opens every docs page in Playwright, exercises the Playground tabs (JSX / Full / CLI) and the Code tab, captures every code block, and checks every import line against the surrounding code
    • 60 pages · 351+ import lines checked · 0 unused · 0 under-import
    • Sample outputs compile cleanly with tsc strict + noUnusedLocals
    Docs cleanup3
    • Root llms.txt + public/llms*.txt: replaced the old "Compound Import Patterns" section with a concise "Component Import" + opt-in "Compound Recipe" section. ~47 lines shorter per file
    • Locale JSON files: removed 21 obsolete install keys, rewrote 200 dot-notation strings to Named, plus 24 locale-specific phrase updates
    • Installation docs: collapsed into a single "Import & Usage" card
    Architecture Decision Records2
    • New ADR: Named-Primary Migration — covers the rationale, keep/remove decisions, and all 25 Compound Recipe snippets
    • Previous ADR "Namespace Compound Export" marked Superseded (kept as v0.2.x historical record)
    @7onic/cli2 changes
    Changed2
    • Registry regenerated from the v0.3.0 Named-export source (40 components, 0 namespace blocks, 8 internal deps)
    • Added repository / bugs / homepage fields to cli/package.json for npm provenance
    v0.2.92026-04-22
    @7onic-ui/react1 changes
    Fixed — Next.js App Router RSC compatibility1
    • src/components/ui/index.ts: add top-level 'use client' directive; replace every export * from './X' with explicit export { Named, … } from './X' + export type { … } from './X' for types. Each of the 39 component files already carries 'use client', so per-component behaviour is unchanged — only the barrel was missing the directive.
    Docs0 changes
    @7onic-ui/tokens0 changes
    v0.2.82026-04-21
    @7onic-ui/react23 changes
    Fixed — `llms.txt` Props defaults audit23
    • Accordion: type (required → 'single'), collapsible (false → true)
    • Breadcrumb: separator ('/' → <ChevronRightIcon />)
    • ButtonGroup: attached (false → true)
    • Dropdown.Content: radius ('lg' → 'md')
    • MetricCard: radius ('xl' → 'default') with explicit 9-value options
    • Modal.Content: size ('md' → 'sm'), scrollBehavior ('inside' → 'outside')
    • NavigationMenu: radius ('default' → 'lg')
    • Popover.Content: showArrow (false → true)
    • Slider: showTooltip ('auto' → 'never')
    • Tabs.List: radius default ('default' → 'md'), options expanded 6 → 9 values
    • Toaster: richColors (false → true), visibleToasts (3 → 5)
    • Tooltip.Content: showArrow (false → true), sideOffset (4 → 6)
    • Pagination: total (required → 1)
    • NavigationMenu: delayDuration=200, skipDelayDuration=300
    • NavigationMenu.Item: defaultOpen=false (new sub-table)
    • NavigationMenu.Indicator: color='default' (new sub-table)
    • Pagination: withControls=true, withEdges=false + quick-mode example
    • Textarea: rows=4
    • Chart.Pie: paddingAngle=0, cornerRadius=0, startAngle=90, endAngle=-270, innerRadius
    • Toaster: offset=24, gap=8
    • Modal.Content: closeIcon
    • TableCell: align='left' (new sub-table)
    • Avatar.Fallback: colorized type boolean → string (source: colorized?: string)
    @7onic-ui/tokens0 changes
    v0.2.72026-04-16
    @7onic-ui/react2 changes
    Fixed2
    • input.tsx, textarea.tsx, select.tsx — add outline-transparent to prevent focus outline flash on Tailwind v4 (transition-colors now includes outline-color)
    • dropdown.tsx, select.tsx, modal.tsx, drawer.tsx, popover.tsx — add text-foreground to Portal content containers for correct dark mode text color
    v0.2.62026-04-16
    @7onic-ui/react1 changes
    Fixed1
    • pagination.tsx — withControls / withEdges props now work: when no children provided, auto-renders Previous/Next (withControls) and First/Last (withEdges) buttons. Compound mode (with children) is unchanged.
    v0.2.52026-04-15
    7onic (CLI)1 changes
    Fixed1
    • init — auto-configure @/ path alias for Vite projects: patches tsconfig.app.json (JSONC-safe) and vite.config.ts (adds import path + resolve.alias), installs @types/node as devDep automatically
    v0.2.42026-04-15
    @7onic-ui/react3 changes
    Fixed3
    • card.tsx — removed unused sizePaddingMap (caused noUnusedLocals error in Vite strict tsconfig)
    • pagination.tsx — withControls/withEdges extracted via rest pattern (caused noUnusedLocals error in Vite strict tsconfig)
    • toast.tsx — isPaused changed to [, setIsPaused] destructuring (caused noUnusedLocals error in Vite strict tsconfig)
    7onic (CLI)7 changes
    Fixed5
    • init — detect @/ path alias in tsconfig.app.json (Vite split tsconfig support)
    • init — auto-inject @import "tailwindcss" for Tailwind v4 (skip if already present)
    • init — improved Vite-specific warning message with both tsconfig.app.json and vite.config.ts guidance
    • add — auto-inject @source directive for Tailwind v4 CSS (relative path from CSS entry to components dir)
    • install-deps — add --ignore-engines flag for yarn install compatibility
    Added2
    • tsconfig.strict-check.json — consumer-environment tsc verification (noUnusedLocals: true)
    • smoke-test.sh — release smoke test script; 3 environments (Next.js 15 + TW v4 / Vite + TW v4 / Vite + TW v3), 7 scenarios each (init → add → build); runs via npm run smoke, auto-runs in prepublishOnly
    Documentation6 changes
    Added6
    • CLI page: Next.js / Vite framework selector in 7onic.json config example
    • CLI page: Vite note card under init section (tsconfig.app.json detection + @import "tailwindcss" auto-inject)
    • CLI page: Tailwind v4 + Vite note card under add section (@source auto-inject)
    • CLI page: Added 4 AI components to Available Components list (chat-input, chat-message, quick-reply, typing-indicator)
    • Token Installation Font tab: Japanese and Korean Fontsource filename now shows both Next.js and Vite paths
    • llms.txt: Vite Fontsource font setup pattern + @source auto-inject note
    v0.2.32026-04-11
    @7onic-ui/react6 changes
    Added4
    • TypingIndicator component — animated typing indicator with dots/cursor variants, 3 sizes, label support
    • QuickReply component — quick reply chip list with icon support, 3 sizes, compound pattern (QuickReply + QuickReply.Item)
    • ChatInput component — compound AI chat input with auto-resizing textarea, send/stop toggle, loading state, character count, 2 variants, 3 sizes, 6 radius options (ChatInput + ChatInput.Field + ChatInput.Submit)
    • ChatMessage component — compound AI chat message display with assistant/user roles, bubble/flat variants, typing animation, 4 delivery status options, hover actions, 3 sizes, 4 radius options (ChatMessage + ChatMessage.Avatar + ChatMessage.Content + ChatMessage.Footer)
    Fixed1
    • Documentation CSS examples: @import now correctly precedes @tailwind directives (CSS spec compliance)
    Removed1
    • Unused src/index.ts barrel file (build entry is src/components/ui/index.ts)
    @7onic-ui/tokens1 changes
    Added1
    • spacing-3.5 (14px / --spacing-3-5) — completes the 2px sub-grid for the 0–14px range
    v0.2.22026-04-10
    @7onic-ui/react1 changes
    Fixed1
    • peerDependencies — @7onic-ui/tokens range ^0.1.0 rejected tokens@0.2.x. Fixed to >=0.1.0 <1.0.0
    @7onic-ui/tokens0 changes
    v0.2.12026-04-09
    @7onic-ui/react1 changes
    Fixed1
    • llms.txt was shipping tokens-only guide instead of full component guide
    @7onic-ui/tokens0 changes
    v0.2.02026-04-08
    @7onic-ui/react2 changes
    Changed1
    • [Breaking] Chart components moved to separate entry point @7onic-ui/react/chart
    Added1
    • Pre-publish validation script (verify:publish) — tests actual npm pack + install + import
    @7onic-ui/tokens0 changes
    Migration Guide0 changes
    v0.1.12026-04-07
    @7onic-ui/react1 changes
    Added1
    • AI Integration: llms.txt included in npm package (llms.txt standard)
    @7onic-ui/tokens1 changes
    Added1
    • AI Integration: llms.txt included in npm package (llms.txt standard)
    Documentation4 changes
    Added3
    • AI Integration pages (/design-tokens/ai, /components/ai)
    • Setup guides for Claude Code, Cursor, GitHub Copilot, ChatGPT
    • llms.txt entry in Installation page Package Contents
    Changed1
    • README: added AI Integration section, updated AI-ready feature description
    v0.1.02026-04-04

    Initial release of 7onic Design System.

    @7onic-ui/react12 changes
    Components (38)7
    • Form: Button, IconButton, ButtonGroup, Toggle, ToggleGroup, Segmented, Checkbox, RadioGroup, Switch, Slider, Input, Textarea, Select, Dropdown
    • Data Display: Avatar, Badge, Card, Table
    • Chart: BarChart, LineChart, AreaChart, PieChart, MetricCard
    • Layout: Divider
    • Overlay: Modal, AlertModal, Drawer, Tooltip, Popover
    • Feedback: Alert, Toast, Progress, Spinner, Skeleton
    • Navigation: Breadcrumb, NavigationMenu, Pagination, Tabs, Accordion
    Features5
    • Namespace Export pattern for 22 compound components (Card.Header, Modal.Content, etc.)
    • Backward-compatible named exports maintained
    • Radix UI Primitives + CVA + forwardRef + Controlled/Uncontrolled
    • Default dark color (bg-foreground) across all components
    • 5-step size scale: xs(28) / sm(32) / md(36) / default(40) / lg(48)
    @7onic-ui/tokens11 changes
    Token Categories (18)6
    • Colors (72 primitive + semantic with text/tint)
    • Typography (11 sizes), FontWeight (3), FontFamily (2)
    • Spacing (18), BorderRadius (9), BorderWidth (5)
    • Shadows (6), IconSizes (6), ZIndex (13), Opacity (21)
    • Duration (8), Easing (5), Scale (4), Breakpoints (5)
    • ComponentSize (12), Animation (54), SemanticTypography (20)
    Features5
    • Automated token pipeline: figma-tokens.json → sync-tokens → 9 distribution files
    • Tailwind v3/v4 dual support with full opacity modifier (/50) via RGB channels
    • CSS variables, Tailwind v3 preset, Tailwind v4 theme, JS/ESM/TypeScript/JSON outputs
    • CLI tool: npx sync-tokens (--input / --output / --dry-run / --force)
    • Breaking change detection + deprecated alias generation