Measured entry
tailark-veil-call-to-action-4
A static, split-layout call-to-action block with a benefits list and pricing panel. It ships as a registry component for Next.js, using Tailwind utility classes, Next Link, Lucide icons, and Tailark variants of the shadcn Button and Card 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 | flagged at 375 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 51.1 KB (116.5 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 1.15s error during build: [vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-41b1a80b6cd1/src/cut/components/call-to-action-4.tsx".
Verdict
Do not adopt this registry item as published. Its Tailark veil-button dependency resolves through the shadcn registry to a missing resource, so installation and build fail. It also needs a shadcn-style setup before it can mount.
Use it if
- You want a compact signup prompt that pairs product benefits with a pricing summary.
- Your app already uses Next.js and can supply Tailark-compatible Button and Card components.
- You are comfortable replacing the placeholder copy, price, and link before release.
Skip it if
- You need a registry item that installs and builds without repairing upstream dependency resolution.
- Your project does not use Next.js or Tailwind utilities and you do not want to port the markup.
- You need checkout, plan selection, or analytics behavior rather than a static call-to-action.
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 Tailwind theme tokens and container-query support, provide compatible Button and Card components, install Lucide React, configure the component import alias, and use Next Link or replace it with the project's router. The missing Tailark button registry dependency must be sourced or recreated manually.
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 cta pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- meraki-cta-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- hyperui-ctas-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.8KB
- Bare
- pass
- Prov
- NO
- meraki-cta-gridminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.8KB
- Bare
- pass
- Prov
- NO
- meraki-cta-formminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-ctas-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO
- meraki-cta-cardminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO