Measured entry

8bitcn-duel-block

cardskeuomorphism

A client-side pixel-art duel card with alternating attacks, health state, winner and rematch flows, responsive fighter layouts, and default character art. It ships as a shadcn registry block plus retro CSS, and expects Next Image, React, path aliases, a cn helper, local Alert, Badge, Button, and HealthBar components, Radix Progress, utility styling, image assets, and a hosted font.

Specimen
Harness screenshot of 8bitcn-duel-block at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of 8bitcn-duel-block at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of 8bitcn-duel-block 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-duel-block
BuildOK
MountOK
Console errors4
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious1
Axe moderate0
Axe minor0
Gzip marginal42.8 KB (108.2 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)

CONSOLE

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

CONSOLE

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

Verdict

A charming themed block, but not publish-ready from this registry payload. The build fails because the source imports an Alert primitive that the item neither ships nor declares. The bare failure also confirms it needs a shadcn-style setup. Avoid it unless you are willing to repair the registry wiring and own the surrounding 8bitcn stack.

Use it if

  • You want a playful combat vignette for a game landing page or themed demo.
  • Your app already uses the matching 8bitcn primitives and can supply fighter images.
  • You are comfortable treating the attack logic as presentation rather than a game system.

Skip it if

  • You need a registry item that installs and builds without repairing missing component dependencies.
  • Your stack does not use Next Image, shadcn-style aliases, or utility classes.
  • You need deterministic, configurable combat rules or externally controlled duel state.
  • Your product cannot load the hosted retro font or provide the expected character artwork.

Install

Installation record for 8bitcn-duel-block
Declared dependenciesradix-ui, @radix-ui/react-progress, 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

In a non-shadcn project, add equivalent path aliases and a cn helper, bring in or replace Alert, Badge, Button, and HealthBar, install Radix Progress, recreate the required utility styles and theme tokens, include the retro stylesheet and font policy, provide both fighter images, and use Next Image or adapt the image elements. The missing Alert must be added explicitly before the block can build.

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.

License
MIT
Record published
2026-08-15

Alternatives

Other published entries for the card pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.