vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-dusk-integrations-1

feature-griddark-futuristic

A dark integrations feature section shipped as a shadcn registry block for Next.js. It uses Tailwind utility classes, theme tokens, an aliased button primitive, Next Link, and a set of registry-supplied product logo components. The declared dusk button dependency currently points to a missing registry endpoint, so the block cannot install or build as published.

Specimen
Harness screenshot of tailark-dusk-integrations-1 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-dusk-integrations-1 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-dusk-integrations-1 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-integrations-1
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious1
Axe moderate0
Axe minor0
Gzip marginal57.0 KB (122.4 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 849ms
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-911b02245c7e/src/components/ui/button.tsx".

Verdict

A usable layout trapped behind a broken registry dependency. The missing dusk button endpoint prevents installation and build, so teams needing a drop-in block should avoid it for now. It also needs a shadcn-style setup, plus content and link cleanup before production use.

Use it if

  • You want a compact integrations pitch with branded tool cards beside a call to action.
  • Your app already follows shadcn conventions and you are willing to repair or replace the unresolved button dependency.
  • You can replace the placeholder links and repeated card copy with real integration content.

Skip it if

  • You need a registry block that installs and builds without manual dependency repair.
  • Your project does not use Next.js, Tailwind utilities, or shadcn-style import aliases.
  • You need working integration controls rather than a static promotional section.
  • You cannot validate and maintain the imported brand marks yourself.

Install

Installation record for tailark-dusk-integrations-1
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

In a non-shadcn project, add Tailwind and the expected theme tokens, configure the component import alias, provide a compatible outline button with child composition, add Next.js Link or substitute your router link, and supply the referenced logo components. You must also bypass or replace the unresolved dusk button registry entry.

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