vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hextaui-auth-otp-verify

auth-formminimal-flat

A client-side React card for entering and resending a one-time verification code. It ships as a HextaUI shadcn registry block and composes registry button, card, field, OTP input, and select primitives. It also relies on Tailwind classes, React state, Lucide icons, the input-otp and Radix packages, and the @/lib/utils alias.

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

Verdict

A capable OTP step with useful delivery, resend, loading, and error hooks. It builds and mounts in the prepared harness, but the bare mount fails because it needs a shadcn-style setup, including the shared utility alias and registry primitives. Choose it when that foundation already matches your app.

Use it if

  • You already have an OTP backend and need a ready-made verification step with loading and error states.
  • Users may switch among email, SMS, or WhatsApp delivery and need the destination displayed safely.
  • You want resend cooldown and optional auto-submit behavior exposed through component callbacks.

Skip it if

  • You need the component to send or verify codes itself, since all authentication work is delegated to callbacks.
  • Your app does not use shadcn-style primitives and you do not want to recreate its registry components, aliases, and theme tokens.
  • Your form architecture requires native form submission or externally controlled code state rather than internal component state.

Install

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

For a non-shadcn project, add Tailwind theme tokens, the shared cn utility and @ alias, plus compatible button, card, field, OTP input, and select primitives. Install input-otp, the required Radix packages, and Lucide React, then connect the submit, resend, and delivery callbacks to your authentication 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 auth-form pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.