Do not use / 11 components that failed the harness / vibecodng

kokonut-beams-background

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the mount. Recorded output follows, trimmed to the message and with the stack frames removed.

BARE BUILD

✗ Build failed in 1m 50s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/components/kokonutui/beams-background.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

A convincing atmospheric hero effect for the stack it targets, but not a neutral drop-in. It builds in the prepared harness yet needs a shadcn-style setup to resolve its utility helper and alias, and the unsuccessful mount result warrants an integration check before adoption.

Renders: NO
A11y: 0
Gzip: 67.7KB
Bare: fail
Prov: NO

magicui-word-rotate

text-effectunclassifiedMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the mount. Recorded output follows, trimmed to the message and with the stack frames removed.

BARE BUILD

✗ Build failed in 20m 13s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/word-rotate.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

A focused, customizable rotator that builds, mounts, and stays within its viewport in the prepared harness. It needs a shadcn-style setup as shipped because the bare build cannot resolve the aliased cn helper. Best for an existing Motion stack, not a lightweight standalone effect.

Renders: NO
A11y: 0
Gzip: 71.2KB
Bare: fail
Prov: NO

No frame on record

8bitcn-calendar

calendarskeuomorphismMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

✗ Build failed in 1m 29s
error during build:
Could not resolve "./select" from "src/cut/components/ui/8bit/calendar.tsx"

PAGE ERROR

build failed

BARE BUILD

✗ Build failed in 1m 52s
error during build:
Could not resolve "./button" from "src/cut/components/ui/8bit/calendar.tsx"

Do not publish this registry item as verified yet. The build fails because the packaged source cannot resolve its sibling select component, while the bare build also lacks the sibling button. It needs a shadcn-style setup and the complete 8bit dependency set before it can mount.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO

No frame on record

8bitcn-dashboard-01

navbarskeuomorphismMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

unable to resolve registry dependency button from https://8bitcn.com/r/button.json

Treat this as an incomplete dashboard starter, not a verified drop-in. The build fails because the data table imports a missing mobile hook, while the bare build also lacks the shared utility module. It needs a shadcn-style setup and source repair; teams unwilling to maintain those pieces should avoid it.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO

No frame on record

8bitcn-toggle-group

switchskeuomorphismMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

✗ Build failed in 37.47s
error during build:
Could not resolve "../toggle-group" from "src/cut/components/ui/8bit/toggle-group.tsx"

PAGE ERROR

build failed

BARE BUILD

✗ Build failed in 34.88s
error during build:
Could not resolve "../toggle-group" from "src/cut/components/ui/8bit/toggle-group.tsx"

Do not adopt the published item unchanged. Its wrapper cannot resolve the sibling base toggle-group import, so the build stops before mounting or accessibility checks. It needs a shadcn-style setup plus an explicit base toggle-group installation and import verification.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO

No frame on record

animata-hero-section

hero-effectgradient-glowMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

✗ Build failed in 34.34s
error during build:
Could not resolve "../text/typing-text" from "src/cut/component.tsx"

PAGE ERROR

build failed

BARE BUILD

✗ Build failed in 53.95s
error during build:
Could not resolve "../text/typing-text" from "src/cut/component.tsx"

Treat this as an Animata composition recipe, not a drop-in hero. The build fails because the copied source cannot resolve its TypingText sibling, and more local pieces sit behind it. It needs a shadcn-style setup as well. Teams unwilling to vendor that component tree should avoid it.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO

No frame on record

hextaui-auth-account-delete

auth-formminimal-flatMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

✗ Build failed in 1m 20s
error during build:
Could not resolve "../../ui/label" from "src/cut/blocks/auth/auth-account-delete.tsx"

PAGE ERROR

build failed

BARE BUILD

✗ Build failed in 1m 56s
error during build:
Could not resolve "../../ui/label" from "src/cut/blocks/auth/auth-account-delete.tsx"

Do not adopt it as published: the build fails because the label import points to a missing local module. It needs a shadcn-style setup plus an import correction before it can mount. Teams unwilling to maintain that local primitive stack should avoid it.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO

No frame on record

kibo-choicebox

selectminimal-flatMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

✗ Build failed in 1m 7s
error during build:
[vite]: Rollup failed to resolve import "@repo/shadcn-ui/components/ui/radio-group" from "<sandbox>/src/cut/index.tsx".

PAGE ERROR

build failed

BARE BUILD

✗ Build failed in 1m 34s
error during build:
[vite]: Rollup failed to resolve import "@repo/shadcn-ui/components/ui/radio-group" from "<sandbox>/src/cut/index.tsx".

Do not adopt the registry output unchanged. It fails to build because its radio-group and utility imports point at the author's private monorepo alias. It needs a shadcn-style setup plus import repair before it can be evaluated or shipped, so teams seeking drop-in code should avoid it.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO

No frame on record

kibo-glimpse

tooltipminimal-flatMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

✗ Build failed in 1m 44s
error during build:
[vite]: Rollup failed to resolve import "@repo/shadcn-ui/lib/utils" from "<sandbox>/src/cut/index.tsx".

PAGE ERROR

build failed

BARE BUILD

✗ Build failed in 1m 47s
error during build:
[vite]: Rollup failed to resolve import "@repo/shadcn-ui/lib/utils" from "<sandbox>/src/cut/index.tsx".

Useful as a small composition layer, but this package fails to build because its class-name helper imports an unresolved repository-internal path. It needs a shadcn-style setup plus a corrected utility import. Teams seeking a verified drop-in component should avoid it until the registry source is fixed.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO

No frame on record

kibo-image-crop

imageminimal-flatMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

✗ Build failed in 1m 27s
error during build:
[vite]: Rollup failed to resolve import "@repo/shadcn-ui/components/ui/button" from "<sandbox>/src/cut/index.tsx".

PAGE ERROR

build failed

BARE BUILD

✗ Build failed in 1m 33s
error during build:
[vite]: Rollup failed to resolve import "@repo/shadcn-ui/components/ui/button" from "<sandbox>/src/cut/index.tsx".

Useful primitives for a shadcn app, but this publication fails because its Button import points at the author's private repository alias. It needs a shadcn-style setup and source edits before it can build, and the ineffective output-size retry deserves correction before production use.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO

No frame on record

kibo-spinner

progressminimal-flatMIT

What we ran. Installed it into a clean Vite app, built it, mounted the demo in Chromium at 375, 768 and 1440, ran axe on the result, measured the gzipped cost, then rebuilt it with the shadcn-style helpers removed.

What broke. The run stopped at the production build. Recorded output follows, trimmed to the message and with the stack frames removed.

BUILD

✗ Build failed in 1m 45s
error during build:
[vite]: Rollup failed to resolve import "@repo/shadcn-ui/components/ui/spinner" from "<sandbox>/src/cut/index.tsx".

PAGE ERROR

build failed

BARE BUILD

✗ Build failed in 1m 36s
error during build:
[vite]: Rollup failed to resolve import "@repo/shadcn-ui/components/ui/spinner" from "<sandbox>/src/cut/index.tsx".

Do not publish this item unchanged. The build fails because its default branch imports a base spinner through an unresolved repository-only alias. It needs a shadcn-style setup plus a corrected local import before it can mount; teams seeking drop-in code should avoid it.

Renders: NO
A11y: 0
Gzip: n/a
Bare: fail
Prov: NO