vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hextaui-settings-advanced

feature-gridminimal-flat

A client-side advanced settings card for debug controls, logging, rate limits, feature flags, and cache clearing. It ships as shadcn registry source rather than a standalone package, and depends on React, lucide-react, a cn helper, utility-theme classes, and local shadcn UI primitives backed by Radix.

Specimen
Harness screenshot of hextaui-settings-advanced at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-advanced at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-advanced at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

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.

Harness measurements recorded for hextaui-settings-advanced
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical2
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal72.1 KB (137.5 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 1m 15s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/settings/settings-advanced.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A useful admin settings scaffold with sensible responsive composition and clear extension points, but it should not ship unchanged because of the critical accessibility findings. It needs a shadcn-style setup, plus real persistence wiring and controlled feature-flag state.

Use it if

  • You need an admin-facing settings shell with save, toggle, select, numeric input, and confirmation flows already composed.
  • Your app already uses shadcn conventions and can connect the optional callbacks to real persistence and cache operations.
  • You want a responsive card that turns its main controls into a wider grid without horizontal overflow.

Skip it if

  • You need production-ready accessibility without first repairing the unlabeled switches and unsupported ARIA usage.
  • Your design system does not provide shadcn-compatible cards, fields, inputs, dialogs, selects, switches, and theme tokens.
  • You expect feature flags to update themselves, since the parent must persist each toggle and pass the changed values back.

Install

Installation record for hextaui-settings-advanced
Declared dependencies@radix-ui/react-alert-dialog, @radix-ui/react-slot, @radix-ui/react-label, @radix-ui/react-separator, @radix-ui/react-select, @radix-ui/react-switch
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, add the referenced Radix packages and lucide-react, recreate the local UI primitives and cn utility, configure the source aliases, and supply utility CSS with the expected theme tokens. Then wire the save, feature-toggle, and cache callbacks and add accessible names to the switches.

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/HextaUI
License
MIT
Record published
2026-08-14

Alternatives

Other published entries for the feature-grid pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.