vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hextaui-settings-domains

formminimal-flat

A client-side React settings card for listing custom domains, adding one in a dialog, showing verification and SSL states, copying DNS records, and confirming removal. It ships as a shadcn registry component and relies on React state, Lucide icons, shadcn UI primitives, Tailwind theme classes, and the cn utility alias.

Specimen
Harness screenshot of hextaui-settings-domains at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-domains at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-domains 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-domains
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal51.8 KB (117.2 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 49s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/settings/settings-domains.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A solid presentation layer for a domain settings workflow, with sensible states and callback boundaries, but it is not a complete domain-management feature. The bare mount fails, so it needs a shadcn-style setup and real service wiring before its controls do meaningful work.

Use it if

  • You need a settings surface for domain status, DNS instructions, SSL controls, and removal in one card.
  • Your app already uses shadcn conventions and can connect the create, verify, SSL, and delete callbacks to real services.
  • You want responsive empty and populated states that fit an existing Tailwind design system.

Skip it if

  • You need domain provisioning, DNS checks, certificate issuance, or persistence included rather than supplied by your backend.
  • Your project does not use shadcn-style aliases, primitives, and Tailwind theme tokens and you do not want to adopt them.
  • You need the component to own and refresh its domain data after actions instead of receiving it from a parent.
  • You need strict domain syntax validation beyond checking that the field is not empty.

Install

Installation record for hextaui-settings-domains
Declared dependencies@radix-ui/react-alert-dialog, @radix-ui/react-slot, @radix-ui/react-dialog, @radix-ui/react-label, @radix-ui/react-separator
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 card, dialog, alert dialog, badge, button, field, and input-group components; install their Radix dependencies and Lucide icons; provide the cn utility and import aliases; map the Tailwind theme tokens; and wire every action callback to your domain service.

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 form pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.