vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-veil-login-3

auth-formminimal-flat

A centered sign-in page with email and password fields, Google and GitHub buttons, and account recovery links. It ships as a shadcn registry block for Next.js and relies on Tailwind theme utilities, next/link, Tailark-provided Button, Input, Label, and Logo components. The form and provider buttons are presentation only until wired to authentication.

Specimen
Harness screenshot of tailark-veil-login-3 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-login-3 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-login-3 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-3
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
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 831ms
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-label" from "<sandbox>re-7550e60f48c9/src/components/ui/label.tsx".

Verdict

A sensible auth shell, but the registry install fails because the Tailark button dependency resolves to a missing shadcn registry resource. It also needs a shadcn-style setup and does not mount bare. Avoid it for a drop-in build; adopt it only if you are willing to repair or replace the dependency chain.

Use it if

  • You already use Next.js, Tailwind, and shadcn-style component aliases.
  • You want a compact standalone sign-in screen with email and social provider entry points.
  • You are prepared to connect the form, provider buttons, and recovery links to your own authentication flow.

Skip it if

  • You need a registry block that installs and builds without repairing an unavailable Tailark dependency.
  • Your app is not based on Next.js and you do not want to replace its Link usage.
  • You need working validation, submission, password recovery, or social login behavior out of the box.
  • Your design system cannot supply compatible Button, Input, Label, Logo, and theme utility implementations.

Install

Installation record for tailark-veil-login-3
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 Tailwind-compatible theme utilities, supply Button, Input, Label, and Logo components, configure the component import alias, and either use Next.js routing or replace next/link. The unavailable Tailark button registry item must be replaced or sourced manually, then the form actions and authentication routes must be implemented.

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.