Measured entry
tailark-veil-features-3
A client-side React and Next.js feature section with selectable feature rows that swap decorative integration, sync, developer, and security illustrations. It ships as a shadcn registry block and depends on Tailwind theme utilities, a shadcn Button and cn helper, lucide-react, Next Link, and Tailark-provided brand SVG components.



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 | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 55.8 KB (121.2 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 760ms error during build: [vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-d67835c77038/src/cut/components/features-3.tsx".
Verdict
Do not publish this as a working drop-in block. The build fails because its Tailark button registry dependency resolves through a missing shadcn registry URL. It needs a shadcn-style setup plus manual dependency repair before the component can be evaluated in the browser.
Use it if
- You want an interactive feature overview with compact navigation and a changing visual panel.
- Your app already follows shadcn conventions and can supply the referenced theme tokens, utilities, button, and brand icons.
- You are prepared to repair or replace the unavailable Tailark button registry dependency before installation.
Skip it if
- You need a registry block that installs and builds without manual dependency repair.
- Your project is not based on React, Next.js, and Tailwind conventions.
- You need the feature controls to expose tab semantics and panel relationships without accessibility work.
- You do not want product-specific integration logos or bespoke decorative illustrations.
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 |
In a non-shadcn project, add a compatible Button component and cn utility, lucide-react, the referenced Tailark brand SVG components, Tailwind theme tokens and advanced utility support, and either Next.js Link or a local link replacement. The unavailable Tailark button registry item must be supplied manually or replaced.
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