Measured entry
tailark-veil-sign-up-3
A Tailark sign-up page shipped as a shadcn registry block. Its source is a Next.js component styled with Tailwind utilities, using Next Link plus aliased Logo, Button, Input, and Label components. It presents email and password fields alongside Google and GitHub options, but supplies 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 | 54.8 KB (120.2 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 759ms error during build: [vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-f9796cb5e72d/src/components/ui/button.tsx".
Verdict
Do not adopt this registry item as-is. The build fails because its Tailark button dependency resolves to a missing registry endpoint, so the component never mounts. It needs a shadcn-style setup plus manual dependency repair. Teams seeking a verified drop-in auth form should avoid it until the registry is fixed.
Use it if
- You already use the Tailark registry and can repair or replace its unresolved UI dependencies.
- You want a compact account creation shell with email, password, and social sign-up choices.
- Your app already has compatible Logo, Button, Input, and Label components behind the expected aliases.
Skip it if
- You need a registry block that installs and builds without dependency repair.
- You need working submission, validation, provider authentication, or error handling out of the box.
- Your project does not use Next.js or Tailwind and you do not want to adapt routing and styles.
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 or substitute compatible Button, Input, Label, and Logo components, configure the import aliases and Tailwind theme classes, and replace Next Link if another router is used. The broken Tailark registry dependency must be bypassed or repaired, and real form and provider authentication handlers must 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