vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-dusk-hero-section-3

herodark-futuristic

A dark fitness hero for Next.js, shipped as a Tailark shadcn registry block. It composes separate Tailark header and logo-cloud blocks, uses Next.js Image for a meditation backdrop and app screenshot, and expects Tailwind utilities plus shadcn-style theme tokens and path aliases.

Specimen
Harness screenshot of tailark-dusk-hero-section-3 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-dusk-hero-section-3 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-dusk-hero-section-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-dusk-hero-section-3
BuildOK
MountOK
Console errors2
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious1
Axe moderate3
Axe minor0
Gzip marginal68.8 KB (134.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)

BARE BUILD

✗ Build failed in 928ms
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-78d932aae900/src/components/hero-section-3-header.tsx".

Verdict

Do not adopt this registry item as published. Installation fails because its Tailark header dependency resolves to a missing registry URL, so the component never builds or mounts. It also needs a shadcn-style setup before it can work in a bare project.

Use it if

  • You already use Next.js, Tailwind, and a shadcn-style component setup.
  • You can repair or replace the unavailable Tailark header registry dependency.
  • Your landing page suits a centered fitness message, partner logos, and a phone mockup over photography.

Skip it if

  • You need a registry item that installs and builds without manual dependency repair.
  • Your project is not based on Next.js or does not support its Image component.
  • You do not want to supply the referenced local meditation and app screenshot assets.
  • You need verified runtime or accessibility behavior, since the failed build prevented those checks.

Install

Installation record for tailark-dusk-hero-section-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 tokens, the at-sign component alias, and Next.js Image support or an equivalent image wrapper. It must also provide the header and logo-cloud components, repair the missing header registry reference, copy both local image assets, and confirm support for the less common aspect and radius utilities.

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 hero pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.