vibecodng.com

Free MCP betaIndex and tools live

Measured entry

8bitcn-login-page

auth-formskeuomorphism

A full-page retro login screen distributed as a shadcn registry page. It combines a responsive split layout with an email and password card, pixel-styled wrappers, a Google-hosted display font, Lucide branding, and Next.js Image. It relies on the usual shadcn utility alias and base button, card, input, and label components.

Specimen
Harness screenshot of 8bitcn-login-page at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of 8bitcn-login-page at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of 8bitcn-login-page 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 8bitcn-login-page
BuildOK
MountOK
Console errors1
Uncaught page errors0
Horizontal overflowflagged at 375
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal41.0 KB (106.4 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

CONSOLE

Failed to load resource: the server responded with a status of 404 (Not Found)

BARE BUILD

✗ Build failed in 865ms
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-8b50f1ce8ac7/src/cut/app/login/page.tsx".

Verdict

Treat this as design source, not a drop-in page. The tested build fails because its pixel label wrapper imports a missing base label component, and the bare build also lacks the shared utility module. It needs a shadcn-style setup before it can compile; teams seeking a framework-neutral login should avoid it.

Use it if

  • You already run a shadcn-style Next.js app and want a retro authentication shell to customize.
  • Your product can accommodate a pixel display font and hard-edged form controls.
  • You are prepared to connect the placeholder links, image, and form actions to real authentication flows.

Skip it if

  • You need a registry item that builds immediately in the tested harness.
  • Your project does not use Next.js or shadcn-compatible path aliases and primitives.
  • You need a finished authentication flow rather than a styled, nonfunctional form shell.
  • Loading a font from Google is incompatible with your privacy, security, or offline requirements.

Install

Installation record for 8bitcn-login-page
Declared dependenciesradix-ui, clsx, 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 compatible button, card, input, and label primitives; a class-name merge utility at the expected alias; Tailwind theme tokens and alias resolution; class-variance-authority, Radix support, and Lucide; plus a replacement for Next.js Image when applicable. Include the retro stylesheet and decide whether to self-host its font.

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/TheOrcDev/8bitcn-ui
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.