Measured entry
tailark-veil-features-1
A static feature-grid section that ships as one TSX registry block with four outline cards and decorative integration graphics. It depends on Tailark's Veil card, several Tailark brand SVG entries, Lucide's shield icon, Tailwind theme and container-query utilities, and shadcn-style import aliases.



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.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | flagged at 375 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 34.7 KB (100.1 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 631ms error during build: [vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-a87d3335f0f1/src/cut/components/features-1.tsx".
Verdict
Do not adopt it from the current registry. Installation stops because the Veil card dependency is requested from a shadcn style registry location that returns not found, so the block never builds or mounts. It needs a shadcn-style setup even after that registry reference is repaired. Teams needing a drop-in component should avoid it.
Use it if
- You want a compact product-feature section with mixed card illustrations and short supporting copy.
- Your app already uses Tailark's Veil components and can resolve its private registry references.
- You are prepared to replace the placeholder integration brands and claims with product-specific content.
Skip it if
- You need a registry block that installs successfully from the published source today.
- Your project does not use Tailwind theme tokens, container queries, or shadcn-style aliases.
- You want semantic product visuals rather than decorative brand logos and abstract line art.
Install
| Declared dependencies | clsx, tailwind-merge |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
A non-shadcn project must add compatible Tailwind theme tokens and container-query utilities, recreate the outline Card API, install Lucide React, supply the referenced brand SVG components, configure the at-sign import alias, and replace or repair the unavailable Veil card registry dependency.
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/blocksAlternatives
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.
- hyperui-feature-grids-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.3KB
- Bare
- pass
- Prov
- NO
- meraki-feature-grid-list-with-imageminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.5KB
- Bare
- pass
- Prov
- NO
- meraki-feature-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 20.2KB
- Bare
- pass
- Prov
- NO