Measured entry
tailark-veil-pricing-2
A compact usage-based pricing section with stacked plan cards, a highlighted tier, linked calls to action, and an overage notice. It ships as a Next.js TSX registry block and depends on Tailark variants of shadcn Button and Card, Lucide icons, Tailwind container-query utilities, and a local cn helper.



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 | 51.4 KB (116.8 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 850ms error during build: [vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-ac1cbd5bd669/src/cut/components/pricing-2.tsx".
Verdict
The layout is sensible for usage-led plans, but the published registry item does not build because the referenced Tailark Button cannot be fetched. It also needs a shadcn-style setup. Avoid adopting it until the registry dependency is restored or replace that dependency manually.
Use it if
- You want a row-based pricing comparison where request limits matter more than feature matrices.
- Your Next.js app already uses Tailwind and compatible Tailark or shadcn component conventions.
Skip it if
- You need an installable registry block today, because its Tailark Button dependency currently resolves to a missing registry endpoint.
- Your pricing needs detailed feature comparisons, billing toggles, or interactive usage calculations.
- Your project does not use Next.js or you do not want to adapt its Link component and path aliases.
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 and Card components with the used variants and as-child behavior, a cn class-merging helper, Lucide React, Tailwind theme tokens and container-query support, Next.js Link or an equivalent adapter, and matching path aliases. The missing Tailark Button registry item must also be supplied locally 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 pricing pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-pricing-1unclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 3.8KB
- Bare
- pass
- Prov
- NO
- hyperui-pricing-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.2KB
- Bare
- pass
- Prov
- NO
- meraki-pricing-side-by-sideminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.8KB
- Bare
- pass
- Prov
- NO
- efferd-pricing-2glassmorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 29.8KB
- Bare
- pass
- Prov
- NO
- ruixen-pricing-plansunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 60.6KB
- Bare
- pass
- Prov
- NO
- tripled-glassmorphism-pricing-block-shadcnuiglassmorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 30.4KB
- Bare
- fail
- Prov
- NO