Measured entry
hextaui-settings-activity-log
A client-side React card for browsing account activity, with text and action filters, date inputs, status badges, an empty state, and an async export callback. It ships through the HextaUI shadcn registry and composes registry-provided card, field, input-group, select, badge, button, and separator primitives, plus React, Lucide icons, Radix-backed controls, Tailwind classes, and a local class-name utility.



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 | 1 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 68.6 KB (134.0 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 1m 45s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/settings/settings-activity-log.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A practical settings block for teams already in the HextaUI or shadcn ecosystem, but it needs a shadcn-style setup and is not drop-in for a bare React app. Fix the critical ARIA issue and wire the date fields into visible filtering if users will expect them to change the list.
Use it if
- You need a presentational activity feed that accepts typed entries and leaves data loading to the parent.
- Your product already uses shadcn-style registry primitives, Tailwind theme tokens, and path aliases.
- You want built-in search, action filtering, status treatment, and an export callback in one settings card.
Skip it if
- You need the date fields to filter the visible entries, because they are only passed to the export callback.
- You require a clean accessibility audit before adoption, because the verified render contains a critical unsupported ARIA attribute.
- You need server-side filtering, pagination, virtualization, or audit-log fetching rather than a client-side presentation layer.
- You want a standalone component with no shadcn registry conventions or local UI primitives.
Install
| Declared dependencies | @radix-ui/react-slot, @radix-ui/react-label, @radix-ui/react-separator, @radix-ui/react-select |
|---|---|
| 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 the referenced card, field, input-group, select, badge, button, and separator implementations; install their Radix packages and Lucide React; configure Tailwind theme tokens and the source alias; and provide the local class-name merge utility. Review the generated primitives to remove the unsupported ARIA attribute before release.
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 input pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- clay-inputclaymorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- neu-search-inputneumorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 18.1KB
- Bare
- pass
- Prov
- NO
- clay-search-inputclaymorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 18.3KB
- Bare
- pass
- Prov
- NO
- originui-comp-33minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 20.7KB
- Bare
- pass
- Prov
- NO
- hextaui-labelminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 31.3KB
- Bare
- pass
- Prov
- NO
- ruixen-circular-stepper-inputliquid-glass
- Renders
- YES
- A11y
- 0
- Gzip
- 61.1KB
- Bare
- pass
- Prov
- NO