vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-veil-integrations-2

feature-gridminimal-flat

A static integrations promo section with a central product mark, orbiting service logos, supporting copy, and a linked call to action. It ships as a Tailark shadcn registry block for Next.js and relies on Tailwind theme utilities, Lucide React, Tailark's Button and Logo components, and local SVG components for each service.

Specimen
Harness screenshot of tailark-veil-integrations-2 at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of tailark-veil-integrations-2 at 768 pixels wide
Harness screenshot at 768 pixels wide. This viewport scrolled sideways.
Harness screenshot of tailark-veil-integrations-2 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-veil-integrations-2
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowflagged at 375, 768
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal54.2 KB (119.6 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 736ms
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-cbeb865e46a5/src/cut/components/integrations-2.tsx".

Verdict

Do not adopt this registry entry as-is. The build fails because its Tailark Button dependency resolves to a missing registry route, so the component never mounts. Even after that dependency is repaired, it needs a shadcn-style setup or equivalent local replacements.

Use it if

  • You already use the Tailark Veil component set and want a compact integrations section.
  • Your Next.js site has matching theme tokens and can supply the referenced service marks.
  • You are willing to repair or replace the unavailable button registry dependency before adoption.

Skip it if

  • You need a registry block that installs and builds without manual dependency repair.
  • Your stack does not use Next.js or shadcn-style path aliases and component conventions.
  • You need real integration status, interaction, or accessible service links rather than a decorative illustration.
  • Your brand policy does not permit bundling third-party service marks.

Install

Installation record for tailark-veil-integrations-2
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 theme tokens and container-query utilities, Lucide React, a Button that supports child composition, a framework-compatible Link, the product logo, all referenced service SVGs, and matching path aliases. The unavailable Tailark Button registry entry must be replaced or repaired first.

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.