Measured entry

tailark-veil-sign-up-2

auth-formminimal-flat

A static Next.js sign-up screen shipped as a shadcn registry TSX block. It presents email, Google, and GitHub choices but supplies no authentication logic. The source depends on next/link, Tailwind theme utilities, and Tailark-provided Logo, Button, Input, and Label components.

Specimen
Harness screenshot of tailark-veil-sign-up-2 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-sign-up-2 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-sign-up-2 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-sign-up-2
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious1
Axe moderate0
Axe minor0
Gzip marginal54.9 KB (120.3 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 687ms
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-3b45e8bab8af/src/components/ui/button.tsx".

Verdict

Do not adopt the current registry entry unchanged. The build fails because the Tailark Veil button dependency resolves to a missing registry resource, so the component never mounts. After repairing that reference, it still needs a shadcn-style setup and application-owned authentication behavior.

Use it if

  • You want a compact account creation screen and will connect every action to your own authentication flow.
  • Your app already uses Next.js, Tailwind theme tokens, and shadcn-style component aliases.
  • You are prepared to replace or manually source the broken Tailark button dependency.

Skip it if

  • You need a registry block that installs and builds without repairing dependency references.
  • Your product needs working social sign-in or form submission behavior out of the box.
  • Your stack is not Next.js and you do not want to replace its Link component and import aliases.
  • You require verified runtime or accessibility behavior, since the component never reached the mount stage.

Install

Installation record for tailark-veil-sign-up-2
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

In a non-shadcn project, add Tailwind utilities and matching theme tokens, configure the component import alias, and provide local Logo, Button, Input, and Label equivalents. Use Next.js Link or replace it with your router. Manually repair or replace the missing Veil button registry dependency, then wire form submission and social authentication.

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.