Measured entry

tailark-veil-login-1

auth-formminimal-flat

A centered Next.js login block with email and password fields, recovery and signup links, plus Google and GitHub buttons. It ships through a shadcn registry and imports Tailark wrappers for the logo, card, controls, and labels, along with Tailwind theme utilities and next/link. The build fails because the registry URL for its Veil button dependency is missing.

Specimen
Harness screenshot of tailark-veil-login-1 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-login-1 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-login-1 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 tailark-veil-login-1
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal55.4 KB (120.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 781ms
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-4b4113a90e5c/src/components/ui/button.tsx".

Verdict

Do not adopt it from the current registry as-is: its button dependency cannot be resolved, so neither build nor mount verification completes. Even after that registry issue is repaired, it needs a shadcn-style setup and real authentication wiring.

Use it if

  • You can repair or replace the unresolved Veil button dependency before adoption.
  • Your app already uses Next.js, Tailwind theme tokens, and shadcn-style component aliases.
  • You want a conventional credential form shell and will connect authentication, recovery, signup, and social providers yourself.

Skip it if

  • You need a registry block that installs and builds without dependency repair.
  • Your application does not use Next.js or path aliases compatible with the supplied imports.
  • You need working authentication behavior rather than a presentational form with placeholder links and an empty form action.

Install

Installation record for tailark-veil-login-1
Declared dependenciesclsx, tailwind-merge
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 compatible logo, button, card, input, and label components; map the component aliases; provide Tailwind and the referenced theme tokens; support Next.js links or replace them; and wire form submission plus every destination. The missing Veil button registry entry must also be repaired or substituted.

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/tailark/blocks
License
MIT
Record published
2026-08-15

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.