Measured entry

hextaui-auth-change-password

auth-formminimal-flat

A client-side React password-change card distributed through a shadcn registry. It includes current, new, and confirmation fields, visibility controls, local validation, loading and success states, and external error support. It relies on HextaUI button, card, field, and input-group primitives, plus Lucide icons and a cn utility.

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

Verdict

A solid account-settings block with clear errors, accessible visibility controls, and controlled loading and success states. It builds and mounts in its intended environment, but it needs a shadcn-style setup and is not a dependency-free drop-in. Review the trimming and fixed password policy before production use.

Use it if

  • You need a complete account-settings password form with validation and status states already wired.
  • Your app already uses shadcn-style registry components, Tailwind theme tokens, and path aliases.
  • You want submission to remain application-owned through a simple callback.

Skip it if

  • Your password policy allows meaningful leading or trailing spaces, because submitted passwords are trimmed.
  • You need server-derived password rules instead of the component's fixed client-side policy.
  • You want a standalone form without adopting its registry primitives and project aliases.

Install

Installation record for hextaui-auth-change-password
Declared dependencies@radix-ui/react-slot, @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 React client-component support, Tailwind and the expected theme tokens, Lucide React, the declared Radix packages, a cn class-merging utility, and equivalents for HextaUI's button, card, field, and input-group components. Replace the registry path aliases with local imports.

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.

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.