Measured entry
tailark-veil-sign-up-1
A full-page account creation screen shipped as a shadcn registry block. It uses Next.js Link, Tailwind theme classes, and local Tailark components for the logo, card, labels, inputs, and buttons. The form includes email and password fields plus Google and GitHub options, but no authentication behavior.



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 859ms error during build: [vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-44fa511f0101/src/components/ui/button.tsx".
Verdict
Do not adopt this registry item as published. Its button dependency points to a missing shadcn registry resource, so installation stops before build or mount verification. It needs a shadcn-style setup and repaired or locally supplied Veil components before it can be evaluated fairly.
Use it if
- You already use the Tailark Veil component set and want a conventional registration screen.
- You can connect the static form and social buttons to your own authentication flows.
- Your app uses Next.js routing and Tailwind theme tokens compatible with the source.
Skip it if
- You need a registry block that installs and builds from its published dependencies today.
- Your project does not use Next.js or a shadcn-style local component structure.
- You need working validation, submission, error handling, or social authentication out of the box.
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 Tailwind theme tokens, compatible Button, Card, Input, Label, and Logo components, a Next.js Link equivalent, and the required import aliases. The missing Veil button registry entry must be replaced with a local implementation or corrected registry source. Authentication handlers and validation must also be supplied.
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