Measured entry
hextaui-card
A shadcn registry card primitive shipped as React source, with composable header, title, description, action, content, and footer parts. It relies on Tailwind utility classes, theme color tokens, the local cn class-merging helper, and the @ path alias rather than an external runtime package.



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 | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 26.7 KB (92.1 KB build, 65.4 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 37.21s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/components/ui/card.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A clean, flexible card primitive with sensible slots and no observed runtime or accessibility trouble in the configured harness. It needs a shadcn-style setup before it will build or mount, so it is a good fit for compatible codebases but not a drop-in choice for a bare React app.
Use it if
- You want a small set of composable card regions that can be styled at the call site.
- Your app already follows shadcn conventions for Tailwind tokens, aliases, and the cn helper.
- You need a card header that can place an optional action beside its title and description.
Skip it if
- You need a ready-made navbar, since the source is a card primitive despite the queue classification.
- Your project does not use Tailwind and you do not want to translate utility classes into its styling system.
- You need semantic heading or section elements built in, since every exported part renders a div by default.
Install
| Declared dependencies | none declared |
|---|---|
| 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 with the referenced card, foreground, and muted theme tokens; provide a cn class-merging utility; configure the @ import alias; and copy the React source into your component tree. Otherwise, replace the alias import and translate the utility classes into your own styling system.
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/preetsuthar17/HextaUIAlternatives
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-breadcrumbminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 31.7KB
- Bare
- fail
- Prov
- NO