Measured entry
tailark-mist-features-4
A client-side React feature section with a heading, supporting copy, and a card grid containing code and scheduling illustrations. It ships as a shadcn registry block and relies on Tailwind theme utilities, a cn helper, Lucide icons, and Tailark Mist button, card, and toggle-group primitives.



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 | 1 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 41.3 KB (106.7 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 652ms error during build: [vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-dbc07ee12f9b/src/cut/components/features-4.tsx".
Verdict
Do not adopt it from the registry as published. The build fails because the referenced Tailark Mist button registry endpoint returns a missing-resource response, so the dependency chain cannot install. It also needs a shadcn-style setup. Teams unwilling to vendor or repair that primitive should avoid it.
Use it if
- You want a compact product-feature section with custom inline illustrations rather than screenshots.
- Your app already uses the Tailark Mist registry primitives and matching Tailwind theme tokens.
Skip it if
- You need a registry item that installs and builds without repairing upstream dependency references.
- Your design system does not provide compatible button, card, and toggle-group primitives.
- You want generic feature copy and imagery that can be driven directly from data.
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 button, card, and toggle-group components, a class-name merge helper, Lucide React icons, Tailwind utilities and theme tokens, then replace or locally vendor the unresolved Tailark Mist button 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