vibecodng.com

Free MCP betaIndex and tools live

Measured entry

shadcn-block-login-01

auth-formminimal-flat

A centered, minimal login card shipped as a shadcn registry block with a route page and a separate React form component. It composes the shadcn Button, Card, Input, Label, and Field primitives, uses the cn utility and utility-class styling, and leaves authentication, recovery, signup, and Google login behavior to the host app.

Specimen
Harness screenshot of shadcn-block-login-01 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of shadcn-block-login-01 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of shadcn-block-login-01 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 shadcn-block-login-01
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal30.3 KB (95.7 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usednone

What the harness recorded

BARE BUILD

✗ Build failed in 28.58s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/blocks/login-01/components/login-form.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A sound starter for a standard login route, with clean mounting and no reported accessibility or overflow issues in the configured harness. It needs a shadcn-style setup and does not mount in a bare app because its shared utility and registry primitives are assumed. Authentication behavior still needs implementation.

Use it if

  • You need a conventional email and password sign-in screen that can be wired to your existing authentication flow.
  • Your app already uses shadcn components and utility-class styling, so the registry imports fit its structure.
  • You want a compact card that adapts cleanly across narrow and wide layouts without a provider.

Skip it if

  • You need a working authentication flow rather than a presentation layer with placeholder links and handlers.
  • Your design system does not use shadcn primitives or utility classes and you do not want to recreate that foundation.
  • Your sign-in experience requires identity selection, multifactor steps, passkeys, or validation states in the initial component.

Install

Installation record for shadcn-block-login-01
Declared dependenciesradix-ui
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 the Button, Card, Input, Label, and Field primitives, the shared cn class-merging utility, compatible utility-class styling and theme tokens, and the required Radix package. Then rewrite the registry aliases to local paths and connect submit, recovery, signup, and provider login actions.

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/shadcn-ui/ui
License
MIT
Record published
2026-08-13

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.