vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hextaui-auth-verify-email

auth-formminimal-flat

A client-side React card for presenting pending, verifying, verified, expired, and error states in an email-confirmation flow. It ships as a shadcn registry item and composes shadcn Card and Button primitives, Lucide icons, Tailwind theme utilities, React state, and the shared cn helper.

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

Verdict

A credible presentation shell with clean status coverage and a responsive mount, but it is not a finished auth flow. It needs a shadcn-style setup, backend wiring, and cleanup of the unused verification and loading props before production use.

Use it if

  • Your product already uses shadcn conventions and needs a compact email-verification status screen.
  • You have backend verification and resend endpoints ready to connect through component props.
  • You want pending, success, expiry, and failure messaging to share one consistent card shell.

Skip it if

  • You need the component itself to read a token and perform verification, because its verification callback is exposed but never called.
  • You need built-in navigation after success or failure.
  • Your design system does not use Tailwind theme tokens or shadcn primitives and you do not want to port the styling.
  • You expect the loading prop to control the interface, because it is currently unused.

Install

Installation record for hextaui-auth-verify-email
Declared dependencies@radix-ui/react-slot
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 React, Lucide React, Radix Slot, compatible Card and Button primitives, Tailwind utilities with the referenced theme tokens, a cn class-merging helper, and matching import aliases. Then wire resend, token verification, and post-verification navigation in the host application.

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