Measured entry
tailark-mist-contact-1
A Tailark contact section delivered as a shadcn registry block. It combines contact details with a responsive sales inquiry form and imports Next.js Link plus Tailark Mist card, input, textarea, button, label, and select primitives styled with Tailwind utility and theme classes.



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 | 1 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 82.7 KB (148.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 990ms error during build: [vite]: Rollup failed to resolve import "@radix-ui/react-label" from "<sandbox>re-ae5e6706dd72/src/components/ui/label.tsx".
Verdict
Do not adopt the registry item as published: its Mist button dependency resolves to a missing registry URL, so installation stops before build or mount. It needs a shadcn-style setup even after that dependency is repaired, and the form still requires application wiring.
Use it if
- You already use the Tailark Mist registry and want a sales inquiry section with contact details beside the form.
- Your Next.js app already has the expected component aliases, Tailwind theme tokens, and shadcn-compatible primitives.
- You are prepared to connect the presentational form to your own validation and submission flow.
Skip it if
- You need a registry item that installs and builds from the published dependency URLs today.
- Your project does not use Next.js or shadcn-style component aliases and you do not want to adapt the imports.
- You need a production-ready form with a submission endpoint, named fields, success states, and error handling included.
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 styling and matching theme tokens, create or map the component import alias, provide compatible card, input, textarea, button, label, and select primitives, replace or configure Next.js Link, and wire form handling. The broken Mist button registry reference must also be repaired or replaced before installation can complete.
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 contact-form pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-contact-forms-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.4KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.6KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-5editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.4KB
- Bare
- pass
- Prov
- NO
- efferd-contact-2minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 30.4KB
- Bare
- fail
- Prov
- NO