vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hextaui-settings-notifications

formminimal-flat

A client-side React settings card for editing notification frequency and delivery channels, plus optional quiet hours. It ships as a HextaUI shadcn registry block with local state and an async save callback, and depends on the project utility alias, Lucide icons, and the registry's button, card, field, input-group, select, separator, and switch primitives.

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

Verdict

A practical, responsive starting point for an established HextaUI app, but not production-ready until its critical accessibility failures are fixed. It does not mount bare and needs a shadcn-style setup with the expected aliases and registry primitives.

Use it if

  • You need a ready-made notification preferences screen with email, push, in-app, and SMS controls.
  • Your app already uses shadcn-style aliases and compatible HextaUI primitives.
  • You can connect the supplied save callback to your own persistence layer and validation.

Skip it if

  • You need an accessible drop-in without remediation, because the verified render has unsupported ARIA attributes and unnamed buttons.
  • You want a standalone package that works without copied registry primitives and a project utility alias.
  • Your notification rules require server-enforced dependencies, consent logic, or per-channel availability beyond simple local toggles.

Install

Installation record for hextaui-settings-notifications
Declared dependencies@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

A non-shadcn project must add the utility alias and cn helper, Lucide React, Tailwind-compatible styling and theme tokens, the required HextaUI UI primitives, and their Radix dependencies. Rewrite the registry import aliases if your source layout differs, then repair the switch ARIA output and give every icon button an accessible name.

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.