Repository navigation
v1.3.13
Install an item at this release, npx shadcn@latest add ourostack/ouro-ui/<item>#v1.3.13; its Ouro dependencies install from the same tag. Every install from GitHub needs a release tag: main has no registry.json, so an address without one fails. In an app with Tailwind CSS v4 and an "@/*" path alias, run shadcn's init once first, with the Base UI base:
npx shadcn@latest init --base base --preset nova --yes --no-monorepo
npx shadcn@latest add ourostack/ouro-ui/ouro-base#v1.3.13 ourostack/ouro-ui/dialog#v1.3.13The tests, stories and specs are optional, one item per component: npx shadcn@latest add ourostack/ouro-ui/dialog#v1.3.13 ourostack/ouro-ui/dialog-tests#v1.3.13, or ourostack/ouro-ui/ouro-tests#v1.3.13 for all of them. List every item with npx shadcn@latest search 'ourostack/ouro-ui#v1.3.13'.
Changes in this release
- Changed: an icon-only Button sizes its svg child as it sizes
startIconunless the icon has a size class of its own, so a Lucide icon matchesstartIconinstead of keeping its own fixed size, and an icon without a size is drawn. - Fixed: a Carousel that is drawn scaled when it mounts, as a Lightbox viewer is while it opens, starts on the slide it was given: it used to land a slide short or long of it, so a Lightbox opened on a late image showed the wrong one (test).
- Fixed: Lightbox's shipped loop spec presses Next once the viewer has grown from the thumbnail, since a press while it still grew could end off the button in WebKit.
- Fixed: MessageList waits for the wheel to rest before it corrects a small drift of the reader's place, so WebKit's scroll keeps moving while older history loads.
- Changed: Skeleton's shimmer moves a band with a transform instead of animating the background, so a page with skeletons can rest between frames.
- Fixed: the testing kit's
commands.emulateMediareturns once the test frame matches the preference it set, so a test can read the new styles on its next line. - Fixed: Toolbar's shipped fade spec lets the held clock run until the tooltip has gone, instead of reading the tooltip after a set run of the clock, which failed at random in WebKit.
- Fixed: a Toolbar's tooltip closes in the same update that fades the bar, so the bar fades out with its tooltip already closed.
Upgrading from v0.1.0
v0.1.0 installed each component with its tests, and v0.2.0 moves some shared helpers to new files, so update every Ouro component in one go.12 Run the commands in your app's root, the folder with components.json. They find your folders the way shadcn does, from the aliases in components.json and the paths in your tsconfig (npx shadcn@latest info shows them), so they work in a src/ or an app/ layout as written.
What changed, by version
What an app on v0.1.0 has to know beyond these steps.3 The release notes list every change.4
-
v0.2.0: each component's tests became an optional
<name>-testsitem, some helpers moved to new files (step 4), and v0.1.0's self-referential theme lines can go (step 2).2 -
v0.3.0: sheets and dialogs stack at
--ouro-layer, a z-index of 50 by default, instead of level 0, so an app element at z-index 1 to 49 that used to show above an open sheet or dialog now sits under it.5 Raise the token in a:rootrule of your own if your app has fixed bars above z-50 (see "Theme" in the README), and drop any portal z-index workaround. A controlledDialogopened by a touch or pen tap focuses its popup instead of its first input, andConfirmDialog'sfinalFocusapplies only after a confirmed action; drop workarounds for either. Every coverage hint is/* istanbul ignore … @preserve */, so a build plugin that kept the hints can go.6 A-testsitem sets Vitest to^5. -
v0.3.1: every component starts with
"use client", so Next.js App Router pages can render them, and the@ouronamespace serves the newest release instead ofmain.7 -
After v0.7.0: a required field's
*is drawn with CSS on a new element around the label and is no longer a<span data-ouro-required>inside it, so tests that expected the label text "Email*" now find "Email".8 The clear, show-password and choose-date buttons in TextField and DatePicker are named by hidden text, notaria-label, so replacebutton[aria-label="…"]selectors with[data-ouro-clear],[data-ouro-show-password]or[data-ouro-choose-date]. The same goes for a file's remove button in FileField ([data-ouro-file-remove]), Combobox's clear and chip remove buttons ([data-ouro-combobox-clear],[data-ouro-combobox-chip-remove]) and NumberField's steppers ([data-ouro-increment],[data-ouro-decrement]). A remove button's hidden text holds the file or item name, so a loosegetByText("pasta.png")now finds it too; pass{ exact: true }.FieldLabel'sclassNamenow goes on the new element around the label, which also carries[data-ouro-required], and a group's labelidis on the inner<span>;style,id,data-*and handlers still go on the<label>. A numericsizeon TextField is now a type error and a development warning; set a width withclassName="w-40".FormErrorsvalues are nowErrorMessages | null | undefined, so code that readserrors.emailasstring | string[]no longer type checks until it handlesnulland React nodes.8 For action answers, importformErrorsfrom@/lib/ouro/form-answerand passerrors={formErrors(actionData, actionData?.errors)}from the initial render; this replaces the unreleased separateresultprop. It identifies equal new answers while keeping cleared fields masked on pending/client renders and rendering current uncleared messages. Cached/reused answers need{ key: acceptedAnswerKey }, changed on actual acceptance, not submit start. Raw records remain compatible but content-only. Reconstruct the value beside Form after JSON/spread/cloning or server-component transport: only messages serialize, not private identity; a safely transported acceptance key can identify the locally reconstructed answer. On a phone, a Link that is not in running text is now a box at least 44px tall and wide that takes its room in the layout, so a column of links grows; passinlineto a link in a sentence inside your own<div>or<span>.9 A Form's top message element exists only while there is a message. Component roots no longer setm-0, so a parent'sspace-y-*now spaces them; remove any margin you added to work around that.8 -
v0.8.0: no component installs
ouro-base; add it once (step 1 does), and later adds leave your stylesheet alone.8 A component installs only the helpers it imports, one item per file inlib/ouro, and a-testsitem brings the tests of everything its component installs.8 The-testsitems no longer set a version for Vitest, Storybook or Playwright.10 The specs importtestandexpectfrome2e/ouro-fixtures.ts, a file of yours (step 1).8lib/ouro/use-dev-warnings.tsis nowlib/ouro/use-dev-messages.ts(step 4).8 Earlier releases installed every helper inlib/ourowith any component, and an update deletes nothing: audit references before deleting unused historical helpers and their own tests (step 5).8OuroProvidernow comes only with the components that render links and withtooltip; your copy stays, and a new app addslib-ouro-providerby name. -
After v0.8.2:
ouroTestProjects({ page })also sizes the touch project's Playwright host, preventing Vitest 4 from scaling landscape touch frames.11 The logical touch viewport still starts at 390x844 with mobile/touch input, but an explicitly enlarged host changes outer-window/screen dimensions and screen orientation; do not treat those as hardware-phone measurements.11 Withoutpage, the touch host stays 390x844.11 On Vitest 4, retain a host large enough for every requested test viewport, such as the Testing guide's 1600x1200 example.11 -
v1.0.0: the first stable release keeps the component APIs, theme tokens, defaults and test-tool minimums from v0.8.4.12 An app already on v0.8.4 needs no component API migration: review the update with
--dry-runand--diff, then overwrite only the items it already uses and reapply its local edits.12 Runtime components and their optional-testsitems remain separate; keep your app-owned fixtures and test configuration. Apps on older releases still need the applicable migration steps above and below. -
After v1.0.2: sheets, and a Menu shown as a bottom sheet, read their shadow from
--ouro-shadow-sheet-<side>, and Checkbox's tick draws over--ouro-duration-draw, both of which only a freshouro-baseadds (step 1 adds it again); without it a sheet draws no shadow and the tick appears at once.13 Every other shadow reads shadcn's--shadow-*tokens, and headings and overlay titles--font-heading, so a theme that sets them now restyles Ouro too.1314 -
After v1.0.1:
formErrorsnow declares its already-frozen message arrays readonly.15 Keep mutableFormErrorsandErrorMessagesfor raw builders; annotate returned snapshots asFormErrorValueorReadonlyFormErrors, or let their type infer. Form, EditSheet, fielderrorprops and the normalization helper accept readonly projections. This corrects a false mutation permission, so a snapshot no longer fits a mutable raw-map annotation.15 TypeScript'sArray.isArraynarrows toany[]and can bypass readonly; unchanged runtime freezing still rejects container mutation, without deeply freezing React nodes. -
After v1.2.2:
ButtonacceptsreloadDocumentfor a document request through an internalhref, and its downloads use a plain anchor likeLink's.16 A false or nulldownloadno longer forces document navigation; passreloadDocumentwhen a resource route needs it without a download.16 -
After v1.2.4: Select, Menu, Combobox, Popover, Tooltip, HoverCard and NavigationMenu open their popups at the end of
<body>unlessOuroProvideris given aportalContainer, and in development each warns once when it opens outside every landmark of a page with a<main>.17 To keep popups in a landmark, makeconst popups = useRef<HTMLDivElement>(null), wrap the app in<OuroProvider portalContainer={popups}>and render<div ref={popups} />last inside<main>, outside any element with atransform,filterorcontain, which would clip or move the popups. In a Next.js App Router layout, which is a server component, put the provider and the ref in a small client component. Inside a dialog your app draws itself, wrap its content in<OuroProvider portalContainer={null}>so its popups open where Base UI puts them.18 Dialogs, sheets and toasts still open at the end of<body>. The landmark warning goes toconsole.warn, so a test that fails on console output fails until the popups are in a landmark. SidebarLayout'sheadernow renders in a<header>, the page's banner, so remove a banner your page draws around SidebarLayout.19 Thetesting/axekit has a newaudit, which fails every violation at any impact and every result axe could not decide unless it measures it, in both color schemes.20 Theouro-testingitem now namesaxe-coreamong its devDependencies, so an update adds it to an app that lacks it.21 -
After v1.2.8: the Toaster's Notifications region is no longer a live region: two live regions last inside it say each toast's message and description, the assertive one a
role="alert", so for its first seven seconds a toast's words are in the page twice.22 Find a toast in a test by its role and name,getByRole("dialog", { name: "Saved" }), or"alertdialog"for a destructive toast, not withgetByText, and expect noaria-liveon the region. Dismiss buttons and destructive toasts are no longer hidden from screen readers while the stack is collapsed.23 Thetesting/axekit'sauditnow leaves focus, the selection and every scroll position as it found them, and throws, naming what changed, when its Tab walk closes a popup it cannot open again; audit the page before that popup opens.24 -
After v1.2.14: Avatar's initials take a hue from the name, from the tokens
--avatar-1to--avatar-8, which only a freshouro-baseadds (step 1 adds it again); without them the initials show with no tint.25 Passcolor="neutral"to keep the plain grey. Avatar's presence dot sits over its edge, so the picture now rounds its own corners instead of the avatar clipping it.26 -
After v1.3.3: Avatar's initials and AvatarGroup's "+N" count are drawn with CSS from a data attribute and are no longer text in the page, so a link or button that wraps an avatar and names itself passes WCAG 2.5.3, Label in Name.27 A test that found an avatar by its letters,
getByText("AL"), or expected them in a row's text, now finds it by role and name,getByRole("img", { name: "Ana Lind" }), or readsdata-ouro-avatar-initials.27 -
After v1.3.9: Ouro check has new gated rules (
giant-picture,cramped-heading,nested-frame,baked-corner,type-scale,shadow-scale,grey-on-colour,heading-hierarchy,jank,repaintand, for a site on the web,https), andblurry-imagecovers videos, so a run that passed can now report findings.28 Fix them, or let a rule report without failing while you do: waive it inouro-check.jsonwith the reason, and remove the waiver once its findings are fixed.jankwalks every page at one size and theme;"walk": falseturns it off.28 -
After v1.3.10: Ouro check has new gated rules,
console-error(an uncaught error,console.errororconsole.warnwhile a page loads),failed-request(a request to the page's own server that fails),off-screen(text or a control the screen cuts off),duplicate-control(the same control twice in view),stray-scrollbar(a region that scrolls by a few pixels),leaked-value(undefined,NaN,[object Object], an id, a translation key or aTODO:on screen) andodd-timestamp(Invalid Date,1 January 1970, a raw or machine timestamp, a negative age)stretched-image(a picture or a video drawn out of its own shape),focus-ring(a control that shows no keyboard focus),dark-miss(a light surface left on a dark page) anddisabled-no-reason(a disabled control with no reason tied to it), so a run that passed can now report findings.29 Fix them, or mark people's own words, such as a message list, withdata-ouro-allow="leaked-value odd-timestamp"and a reason.29check.tsimports four new files,text-check.ts,layout-check.ts,theme-check.tsandinteraction-check.ts: if your app pins the check's files in a list, addregistry/ouro/check/text-check.ts,registry/ouro/check/layout-check.ts,registry/ouro/check/theme-check.tsandregistry/ouro/check/interaction-check.tsto it.29blurry-imagecan no longer be waived: it holds a picture to exactly its file's pixels at the density, checks raster CSS backgrounds too, reportsdata-ouro-allow="blurry-image"as a finding of its own, and a waiver of it inouro-check.jsonmakes the check exit 2.30 Give each picture it reports a larger source;--images-report <file.json>lists them with the width each needs.ouro-imagesrefuses a picture too small to draw sharp, and exits 1 for it.30 -
After v1.3.10 (Skeleton): Skeleton's shimmer slides a band with
translateon the keyframesouro-shimmer-band, which only a freshouro-baseadds (step 1 adds it again); without it the band holds still in the middle, as it does with reduced motion.31
0. Commit first
--overwrite replaces every Ouro file, including files you edited.32 Commit before you start. Afterwards, git diff shows your own edits being overwritten, so reapply the ones you need.
Review the diff of your Tailwind CSS file too, the one components.json names in tailwind.css, because step 1 adds ouro-base, the one item that writes there, and shadcn add rewrites more than Ouro's tokens. It adds @custom-variant dark (&:is(.dark *)); when the file has no @custom-variant (shadcn@4.21.1 does this for any item with theme variables on Tailwind CSS v4), adds the tokens your file lacks to :root, .dark and @theme inline (among them --input, --radius and the radius scale, if your theme has none), and collapses blank lines.33 Keep the new lines and step 2's deletions, and revert the rest. After this upgrade no component add opens the file again.8
1. Update every Ouro component, with its tests
Update every Ouro component in your app, not only the items you typed: v0.1.0 added each component's dependencies too, so an app that added only dialog also has button and sheet. Each component is one .tsx file in your components/ouro/ folder (dialog/ holds dialog and confirm-dialog, and text/ holds text and heading).1 Add each one as <name> and <name>-tests, plus ouro-base, in one command at the same ref, with --overwrite (without it the CLI stops to ask about each file). For the app that added only dialog, that is ouro-base button button-tests dialog dialog-tests sheet sheet-tests. No component installs ouro-base any more, so this is where your stylesheet gets the tokens added since v0.1.0.8
This command finds the components, prints them and adds them. If it finds none, it stops before adding anything34; run it in the folder with components.json. If you use the Ouro theme, add ourostack/ouro-ui/ouro-theme#v1.3.13 to the add in it.
( p() { npx shadcn@latest info --json | node -p "JSON.parse(require('fs').readFileSync(0, 'utf8')).config.resolvedPaths.$1"; }; ouro="$(p components)/ouro"; items=$(find "$ouro" -name '*.tsx' ! -name '*-parts.tsx' ! -name '*.test.tsx' ! -name '*.stories.tsx' 2>/dev/null | sed -E 's|.*/(.*)\.tsx$|\1|' | sort); [ -n "$items" ] || { echo "No Ouro components in $ouro. Run this in the folder with components.json." >&2; exit 1; }; echo "Updating: $(echo "$items" | paste -sd " " -)"; npx shadcn@latest add $(echo "$items" | sed -E 's|.*|ourostack/ouro-ui/&#v1.3.13 ourostack/ouro-ui/&-tests#v1.3.13|') ourostack/ouro-ui/ouro-base#v1.3.13 --overwrite )This keeps the tests v0.1.0 installed, deletes none of your files and adds no component you didn't have. shadcn may print Skipped N files: (files might be identical, use --overwrite to overwrite) even with --overwrite: those files already equal the release's, so nothing was missed.32 The -tests items name Vitest, Storybook and Playwright without a version, so the versions in your package.json stay as they are. v0.7.0's items still carry versions: after an add at v0.7.0, restore every test-tool version you had pinned (git diff package.json): Vitest and its companions, Playwright and Storybook.35 The tests need Vitest 4.1.11 or later, Playwright 1.58.1 or later and Storybook 10.2.10 or later; update those yourself if yours are older (the README's "Details" links the Testing page).36 The specs in e2e/ouro now import test and expect from e2e/ouro-fixtures.ts, a file of yours: add it with the one line export { expect, test } from "@playwright/test";, or export your own fixtures from it.
2. Remove the self-referential theme lines
v0.1.0 wrote a line into @theme inline for each Ouro token that points at itself, such as --ouro-press-scale: var(--ouro-press-scale);, and --color-ouro-backdrop-color: var(--ouro-backdrop-color);.37 Delete them from your Tailwind CSS file, the one components.json names in tailwind.css. The values stay in :root and .dark. This command finds the file and deletes the lines:
perl -i -ne 'print unless /^\s*--(color-)?ouro-[\w-]+:\s*var\(--ouro-[\w-]+\);\s*$/' "$(npx shadcn@latest info --json | node -p "JSON.parse(require('fs').readFileSync(0, 'utf8')).config.resolvedPaths.tailwindCss")"3. Optional: drop Ouro's tests
To keep only the components, delete the files Ouro owns for its tests: the test, type-test and story files in your components/ouro/ and lib/ouro/ folders, the test kit in lib/ouro/testing and the specs in e2e/ouro. The command stops if it can't find those folders.
( p() { npx shadcn@latest info --json | node -p "JSON.parse(require('fs').readFileSync(0, 'utf8')).config.resolvedPaths.$1"; }; c="$(p components)/ouro"; l="$(p lib)/ouro"; [ -d "$c" ] && [ -d "$l" ] || { echo "No Ouro folders at $c and $l. Run this in the folder with components.json." >&2; exit 1; }; find "$c" "$l" \( -name '*.test.ts' -o -name '*.test.tsx' -o -name '*.test-d.ts' -o -name '*.stories.tsx' \) -delete; find "$l/testing" e2e/ouro -delete )Then remove the ouroTestProjects import and call from your Vitest config. Only if Ouro's tests were the only tests using them, also delete vitest.config.ts, playwright.config.ts and .storybook/, and uninstall vitest, @vitest/browser-playwright, playwright, @playwright/test, storybook and @storybook/react-vite with your package manager.
4. Change imports of moved helpers
If your own code imports these helpers, change the import:
useOuro: fromlib/ouro/ouro-providertolib/ouro/use-ouro.sheetSides,sideWarning,sheetHint,iosBackdropandfooterClass: fromcomponents/ouro/sheet/sheet-partstocomponents/ouro/sheet/sheet-styles.dialogSizesanddialogSizeWarning: fromcomponents/ouro/dialog/dialog-partstocomponents/ouro/dialog/dialog-styles.alignClassesandcheckAlign: fromcomponents/ouro/text/texttocomponents/ouro/text/text-styles.useDevWarnings: fromlib/ouro/use-dev-warningstolib/ouro/use-dev-messages. Delete the oldlib/ouro/use-dev-warnings.ts; nothing imports it after step 1.
5. Delete the helpers nothing imports
Releases before v0.8.0 installed every helper in lib/ouro with any component.8 From v0.8.0 a component installs only the helpers it imports, but an update deletes nothing.8 Remove unused historical helpers rather than excluding them from coverage.
Before deleting anything, perform a read-only import/reference audit across the whole app, including scripts, tests, stories and configuration outside src/. Use the app's actual tsconfig and bundler aliases to resolve references to each helper's full path. Check relative imports, explicit extensions, re-exports and dynamic imports too; an importing file with the same basename is still a different file. A text search for lib/ouro/<name> alone cannot prove a helper is unused.
Delete a helper and its own tests only after verifying that no remaining app file or retained Ouro file references it (references from that helper's own tests do not require keeping an otherwise unused helper). Check again after each removal: another historical helper may have been used only by the one you removed. If a reference is unresolved or you cannot verify a file's use, keep it until you can. Keep ouro-provider.tsx if you mean to use it and have not yet, and retain ambient declarations such as env.d.ts that the app's type check needs even without an import.
Then type check and build your app. CI runs steps 1 to 3 on a v0.1.0 app, with these commands read from this file (scripts/install-test.sh upgrade).3
Or through the @ouro namespace, which serves the newest release: this one, once main is prepared for the next release. Add it to components.json once:
"registries": { "@ouro": "https://ui.ouroboros.bot/r/{name}.json" }npx shadcn@latest add @ouro/ouro-base @ouro/dialogRehearsed: the rehearsal of v1.3.13 passed on main's commit a7368f6d01977911e719cfa1b3f495a527d9c1b8, which this release is cut from.
Items, by name. The docs describe each component, and the tag's registry.json holds every item's description:
ouro-base, ouro-theme, ouro-lib, ouro-testing, lib-announce, lib-appearance-hints, lib-celebration-cap, lib-claims, lib-class-name-check, lib-cn, lib-color-scheme, lib-color-scheme-script, lib-control-ref, lib-current-path, lib-dev, lib-env, lib-feedback, lib-floating, lib-focus-handoff, lib-form-answer, lib-halve, lib-insert-text, lib-keep-clear, lib-key-shortcuts, lib-last-input, lib-measure-interaction, lib-navigation-key, lib-open-mode, lib-ouro-provider, lib-page-scroll-hold, lib-people-cache, lib-portal-container, lib-porthole-view, lib-refs, lib-router-link, lib-row-hover, lib-scroll-fade, lib-server-element, lib-share, lib-spring, lib-stretched-link, lib-toast, lib-tones, lib-touch-target, lib-use-backdrop-anchor, lib-use-command-shortcut, lib-use-dev-messages, lib-use-drag, lib-use-field, lib-use-install-prompt, lib-use-keyboard-scrollable, lib-use-media-query, lib-use-mounted-open, lib-use-ouro, lib-use-person, lib-use-reduced-motion, lib-use-sheet-presentation, lib-use-timer, button, text, heading, sheet, dialog, confirm-dialog, field, fieldset, link, text-field, text-area, checkbox, checkbox-group, radio-group, switch, form, edit-sheet, select, native-select, number-field, slider, combobox, toaster, spinner, progress, skeleton, avatar, badge, alert, separator, kbd, popover, tooltip, hover-card, menu, command, tabs, segmented-control, accordion, collapsible, show-more, card, item, item-group, empty, scroll-area, aspect-ratio, stack, row, navbar, sidebar, sidebar-layout, stacked-layout, auth-layout, breadcrumb, pagination, navigation-menu, table, description-list, toggle, toggle-group, button-group, otp-field, file-field, color-field, swipe-actions, reorderable, calendar, date-picker, carousel, resizable, chart, message, message-list, attachment, thread-summary, checklist, inspector, skip-link, tab-bar, route-progress, color-scheme-toggle, page-header, copy-button, code-block, timer, timer-tray, celebrate, choice-card, image-cropper, image-field, share-button, sync-status, local-date, relative-time, install-prompt, conversation-list, attention-card, reaction-bar, lightbox, composer, emoji-picker, navigation-rail, time-grid, toolbar, agent-presence, autocomplete, emoji, level-meter, live-captions, media-tile, moment, snap-pip, family-bar, family-footer, hero, porthole, lib-announce-tests, lib-appearance-hints-tests, lib-celebration-cap-tests, lib-claims-tests, lib-class-name-check-tests, lib-cn-tests, lib-color-scheme-script-tests, lib-color-scheme-tests, lib-control-ref-tests, lib-current-path-tests, lib-dev-tests, lib-feedback-tests, lib-floating-tests, lib-focus-handoff-tests, lib-form-answer-tests, lib-halve-tests, lib-insert-text-tests, lib-keep-clear-tests, lib-key-shortcuts-tests, lib-last-input-tests, lib-measure-interaction-tests, lib-navigation-key-tests, lib-ouro-provider-tests, lib-page-scroll-hold-tests, lib-people-cache-tests, lib-portal-container-tests, lib-porthole-view-tests, lib-row-hover-tests, lib-scroll-fade-tests, lib-server-element-tests, lib-share-tests, lib-spring-tests, lib-use-command-shortcut-tests, lib-use-dev-messages-tests, lib-use-drag-tests, lib-use-install-prompt-tests, lib-use-keyboard-scrollable-tests, lib-use-media-query-tests, lib-use-mounted-open-tests, lib-use-person-tests, lib-use-reduced-motion-tests, lib-use-sheet-presentation-tests, lib-use-timer-tests, button-tests, text-tests, heading-tests, sheet-tests, dialog-tests, confirm-dialog-tests, field-tests, fieldset-tests, link-tests, text-field-tests, text-area-tests, checkbox-tests, checkbox-group-tests, radio-group-tests, switch-tests, form-tests, edit-sheet-tests, select-tests, native-select-tests, number-field-tests, slider-tests, combobox-tests, toaster-tests, spinner-tests, progress-tests, skeleton-tests, avatar-tests, badge-tests, alert-tests, separator-tests, kbd-tests, popover-tests, tooltip-tests, hover-card-tests, menu-tests, command-tests, tabs-tests, segmented-control-tests, accordion-tests, collapsible-tests, show-more-tests, card-tests, item-tests, item-group-tests, empty-tests, scroll-area-tests, aspect-ratio-tests, stack-tests, row-tests, navbar-tests, sidebar-tests, sidebar-layout-tests, stacked-layout-tests, auth-layout-tests, breadcrumb-tests, pagination-tests, navigation-menu-tests, table-tests, description-list-tests, toggle-tests, toggle-group-tests, button-group-tests, otp-field-tests, file-field-tests, color-field-tests, swipe-actions-tests, reorderable-tests, calendar-tests, date-picker-tests, carousel-tests, resizable-tests, chart-tests, message-tests, message-list-tests, attachment-tests, thread-summary-tests, checklist-tests, inspector-tests, skip-link-tests, tab-bar-tests, route-progress-tests, color-scheme-toggle-tests, page-header-tests, copy-button-tests, code-block-tests, timer-tests, timer-tray-tests, celebrate-tests, choice-card-tests, image-cropper-tests, image-field-tests, share-button-tests, sync-status-tests, local-date-tests, relative-time-tests, install-prompt-tests, conversation-list-tests, attention-card-tests, reaction-bar-tests, lightbox-tests, composer-tests, emoji-picker-tests, navigation-rail-tests, time-grid-tests, toolbar-tests, agent-presence-tests, autocomplete-tests, emoji-tests, level-meter-tests, live-captions-tests, media-tile-tests, moment-tests, snap-pip-tests, family-bar-tests, family-footer-tests, hero-tests, porthole-tests, ouro-lib-tests, ouro-tests, ouro-census, ouro-source-rules, ouro-check, ouro-images, ax-checks, ax-claims, ax-cli, ax-command, ax-component, ax-dev-commands, ax-effects, ax-example, ax-exit-codes, ax-flows, ax-lint, ax-mcp, ax-outcome, ax-output, ax-precise-copy, ax-problem, ax-terminal, ax-voice, ax-wait, ax-work-event, ax-xray, ax-checks-tests, ax-claims-tests, ax-cli-tests, ax-command-tests, ax-component-tests, ax-dev-commands-tests, ax-effects-tests, ax-exit-codes-tests, ax-flows-tests, ax-lint-tests, ax-mcp-tests, ax-outcome-tests, ax-output-tests, ax-precise-copy-tests, ax-problem-tests, ax-terminal-tests, ax-voice-tests, ax-wait-tests, ax-work-event-tests, ax-xray-tests, ouro-ax, ouro-ax-tests
-
https://github.com/ourostack/ouro-ui/releases/tag/v0.1.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.1.0) ↩ ↩2
-
https://github.com/ourostack/ouro-ui/releases/tag/v0.2.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.2.0) ↩ ↩2
-
scripts/install-test.sh; scripts/upgrade-note.mjs verify:testExists(scripts/upgrade-note.test.mjs::the upgrade install test runs the note's commands and copies none) verify:ciJob(install-upgrade) ↩ ↩2
-
https://github.com/ourostack/ouro-ui/releases; .github/workflows/release.yml; scripts/release-commit.sh verify:urlOk(https://github.com/ourostack/ouro-ui/releases) verify:fileLine(.github/workflows/release.yml, /scripts/release-commit.sh "$VERSION"/) verify:fileLine(scripts/release-commit.sh, /changes.mjs assemble/) ↩
-
https://github.com/ourostack/ouro-ui/releases/tag/v0.3.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.3.0) verify:fileLine(registry/ouro/theme/ouro-base.css, /--ouro-layer: 50;/) ↩
-
scripts/source-rules.mjs verify:testExists(scripts/source-rules.test.mjs::every istanbul hint in registry/ carries @preserve, so it survives esbuild in an app) ↩
-
https://github.com/ourostack/ouro-ui/releases/tag/v0.3.1 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.3.1) ↩
-
https://github.com/ourostack/ouro-ui/releases/tag/v0.8.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.8.0) verify:testExists(scripts/registry.test.mjs::only ouro-base and ouro-theme touch the app's stylesheet, and no other item installs them) verify:testExists(scripts/registry.test.mjs::each lib helper is its own item, so an item installs only the helpers it imports) ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12
-
registry/ouro/components/ouro/link/link.touch.test.tsx verify:testExists(registry/ouro/components/ouro/link/link.touch.test.tsx::gives a link on its own line a 44px box, centred on its text) ↩
-
test:scripts/registry.test.mjs::devDependencies are named without a version, so the CLI installs it only when the app lacks it and never changes a version the app has verify:testExists(scripts/registry.test.mjs::devDependencies are named without a version, so the CLI installs it only when the app lacks it and never changes a version the app has) ↩
-
registry/ouro/lib/ouro/testing/vitest.ts; https://github.com/ourostack/ouro-ui/releases/tag/v0.8.3 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.8.3) verify:testExists(scripts/testing-kit.test.mjs::page sizes every Playwright host while the touch frame keeps its phone viewport and input) verify:testExists(scripts/testing-kit.test.mjs::ouroTestProjects leaves the page size to Vitest unless the app sets one) verify:fileLine(registry/ouro/lib/ouro/testing/vitest.ts, /390x844/) verify:fileLine(docs/guides/testing.md, /1600/) ↩ ↩2 ↩3 ↩4
-
https://github.com/ourostack/ouro-ui/releases/tag/v1.0.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v1.0.0) ↩ ↩2
-
https://github.com/ourostack/ouro-ui/releases/tag/v1.1.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v1.1.0) verify:fileLine(registry/ouro/theme/ouro-base.css, /--ouro-shadow-sheet-/) verify:fileLine(registry/ouro/theme/ouro-base.css, /--ouro-duration-draw:/) ↩ ↩2
-
test/theme-tokens.test.tsx verify:testExists(test/theme-tokens.test.tsx::standard shadow and font tokens > falls back to the inherited font for headings when the theme names none, and Kbd always keeps it) ↩
-
https://github.com/ourostack/ouro-ui/releases/tag/v1.0.2 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v1.0.2) verify:fileLine(registry/ouro/lib/ouro/form-answer.ts, /Snapshot arrays are readonly/) ↩ ↩2
-
https://github.com/ourostack/ouro-ui/releases/tag/v1.2.2; registry/ouro/components/ouro/button/button.test.tsx; registry/ouro/components/ouro/link/link.test.tsx verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v1.2.2) verify:testExists(registry/ouro/components/ouro/button/button.test.tsx::link branch > uses the document for reloadDocument and downloads, retaining router navigation otherwise) verify:testExists(registry/ouro/components/ouro/link/link.test.tsx::Link > treats only a present download as document navigation, including an empty filename) ↩ ↩2
-
registry/ouro/lib/ouro/portal-container.test.tsx verify:testExists(registry/ouro/lib/ouro/portal-container.test.tsx::usePortalContainer > leaves a popup at the end of , Base UI's default, without a portalContainer) verify:testExists(registry/ouro/lib/ouro/portal-container.test.tsx::usePortalContainer > warns once, in development, when a popup opens outside every landmark of a page that has a main) ↩
-
registry/ouro/lib/ouro/portal-container.test.tsx verify:testExists(registry/ouro/lib/ouro/portal-container.test.tsx::usePortalContainer > gives popups Base UI's own place again inside an OuroProvider whose portalContainer is null, as an app's own dialog needs) ↩
-
registry/ouro/lib/ouro/testing/axe.test.ts verify:testExists(registry/ouro/lib/ouro/testing/axe.test.ts::audit > fails a violation whatever its impact: content outside every landmark is only moderate) ↩
-
scripts/registry.test.mjs verify:testExists(scripts/registry.test.mjs::npm dependencies are pinned to the ranges this repository tests) ↩
-
registry/ouro/components/ouro/toast/toaster.test.tsx verify:testExists(registry/ouro/components/ouro/toast/toaster.test.tsx::Toaster > renders an empty Notifications landmark in a portal, which holds its own live regions) ↩
-
registry/ouro/components/ouro/toast/toaster.test.tsx verify:testExists(registry/ouro/components/ouro/toast/toaster.test.tsx::toast() > keeps every toast, its action and its dismiss button reachable by a screen reader while the stack rests collapsed) ↩
-
registry/ouro/lib/ouro/testing/axe.test.ts verify:testExists(registry/ouro/lib/ouro/testing/axe.test.ts::audit > fails, naming what changed, when its Tab walk closes a popup that focus leaving closes, which it cannot open again) ↩
-
registry/ouro/theme/ouro-base.css verify:fileLine(registry/ouro/theme/ouro-base.css, /--avatar-8:/) verify:testExists(registry/ouro/components/ouro/avatar/avatar.test.tsx::Avatar colors > picks the same hue for the same name, and spreads names across the hues) ↩
-
registry/ouro/components/ouro/avatar/avatar.test.tsx verify:testExists(registry/ouro/components/ouro/avatar/avatar.test.tsx::Avatar shapes and icons > clips a square's picture to its corners) ↩
-
registry/ouro/components/ouro/avatar/avatar.test.tsx verify:testExists(registry/ouro/components/ouro/avatar/avatar.test.tsx::Avatar inside a link or button that has its own name > the same link around initials written as text fails the rule, so the check can fail) verify:testExists(registry/ouro/components/ouro/avatar/avatar.test.tsx::Avatar > shows initials from the name, and the name to screen readers) ↩ ↩2
-
registry/ouro/check/check.ts verify:fileLine(registry/ouro/check/check.ts, /^ "giant-picture": "giant picture",$/) verify:testExists(scripts/check/check.test.mts::Ouro check's design rules > fails each seed case where a person saw it, with numbers that say why) ↩ ↩2
-
registry/ouro/check/text-check.ts verify:fileLine(registry/ouro/check/check.ts, /^ "odd-timestamp": "odd timestamp",$/) verify:testExists(test/check-text-in-page.test.ts::findTextIssues: leaked-value > finds each kind of value the program meant for itself, quoting what it shows) ↩ ↩2 ↩3
-
test:scripts/check/check.test.mts::Ouro check > never waives a blurry picture, and lists each one, with the file it needs, in the images report; test:scripts/images/images.test.mts::Ouro images' refusal of pictures too small to draw sharp > writes nothing for a refused picture, and the rest as before verify:testExists(scripts/check/check.test.mts::Ouro check > never waives a blurry picture, and lists each one, with the file it needs, in the images report) verify:testExists(scripts/images/images.test.mts::Ouro images' refusal of pictures too small to draw sharp > writes nothing for a refused picture, and the rest as before) ↩ ↩2
-
registry/ouro/theme/ouro-base.css verify:fileLine(registry/ouro/theme/ouro-base.css, /@Keyframes ouro-shimmer-band/) verify:testExists(registry/ouro/components/ouro/skeleton/skeleton.test.tsx::Skeleton > shimmers a band that moves by translate only, and holds it still in the middle with reduced motion) ↩
-
https://ui.shadcn.com/docs/cli verify:urlOk(https://ui.shadcn.com/docs/cli) ↩ ↩2
-
https://github.com/shadcn-ui/ui/blob/3502dbcde11d1eaf967a47ac375744dc336641f3/packages/registry/src/utils/updaters/update-css-vars.ts#L91-L124 verify:urlOk(https://github.com/shadcn-ui/ui/blob/3502dbcde11d1eaf967a47ac375744dc336641f3/packages/registry/src/utils/updaters/update-css-vars.ts#L91-L124) verify:testExists(scripts/install-check.test.mjs::a complete install passes, for each variant and stage) ↩
-
UPGRADING.md verify:fileLine(UPGRADING.md, /[ -n "$items" ] || { echo "No Ouro components/) ↩
-
https://github.com/ourostack/ouro-ui/releases/tag/v0.7.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.7.0) ↩
-
scripts/registry.mts verify:fileLine(scripts/registry.mts, /vitest: "4.1.11"/) verify:fileLine(scripts/registry.mts, /playwright: "1.58.1"/) verify:fileLine(scripts/registry.mts, /storybook: "10.2.10"/) ↩
-
https://github.com/ourostack/ouro-ui/releases/tag/v0.2.0; scripts/install-check.mjs verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.2.0) verify:testExists(scripts/install-check.test.mjs::a token that refers to itself fails) ↩