Measured entry
tailark-veil-login-1
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.



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.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 55.4 KB (120.8 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written 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
| Declared dependencies | clsx, tailwind-merge |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no 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/blocksAlternatives
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.
- meraki-auth-sign-in-card-with-side-imageminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.9KB
- Bare
- pass
- Prov
- NO
- shadcn-block-login-01minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 30.3KB
- Bare
- fail
- Prov
- NO
- shadcn-block-login-02minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 31.9KB
- Bare
- fail
- Prov
- NO
- shadcn-block-login-05minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 31.9KB
- Bare
- fail
- Prov
- NO
- 8bitcn-login-formskeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 33.2KB
- Bare
- fail
- Prov
- NO
- 8bitcn-advanced3skeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 33.3KB
- Bare
- fail
- Prov
- NO