Measured entry
ruixen-breadcrumb-icon
A client-side React breadcrumb distributed as a shadcn registry component. It renders optional Lucide icons, chevron separators, and a hover-tracking highlight, with Tailwind utility classes and a project-local cn helper backed by clsx and tailwind-merge.



Measured
Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 2 |
| Axe moderate | 1 |
| Axe minor | 0 |
| Gzip marginal | 31.4 KB (96.9 KB build, 65.5 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 1m 12s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/components/ruixen/breadcrumb-icon.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
Visually useful and stable across the tested layouts, but not ready to ship unchanged because its icon-only links and list structure trigger serious accessibility findings. It also needs a shadcn-style setup to build.
Use it if
- You want an icon-assisted breadcrumb whose intermediate items are ordinary anchor links.
- Your app already uses Tailwind and a shadcn-style cn utility.
- You can correct its list semantics and accessible naming before release.
Skip it if
- You need an accessible icon-only mode out of the box, because its links lose their discernible names.
- You require valid list markup without modification, because the animated highlight is a direct non-list child of the ordered list.
- You expect the hover highlight to provide equivalent keyboard-focus feedback.
- You need the final breadcrumb item to remain clickable, since the component always renders it as the current-page span.
Install
| Declared dependencies | lucide-react, clsx, tailwind-merge |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add Tailwind, Lucide React, clsx, and tailwind-merge, then provide the expected cn utility or replace its alias import with your own class-merging helper. Also ensure the client-component directive fits your framework.
Source and credit
This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.
Author repository
github.com/ruixenui/ruixen.comAlternatives
Other published entries for the navbar pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-headers-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 19.1KB
- Bare
- pass
- Prov
- NO
- kibo-dialog-stackminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 33.4KB
- Bare
- pass
- Prov
- NO
- ruixen-floating-navbarunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 59.9KB
- Bare
- pass
- Prov
- NO
- ruixen-hover-gradient-navbargradient-glow
- Renders
- YES
- A11y
- 0
- Gzip
- 60.9KB
- Bare
- pass
- Prov
- NO
- ruixen-expandable-menu-navbarunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 61.8KB
- Bare
- pass
- Prov
- NO
- hextaui-cardminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 26.7KB
- Bare
- fail
- Prov
- NO