Measured entry

tripled-newsletter-signup-block-shadcnui

pricinggradient-glowmotion on file

An animated newsletter callout shipped as a client-side shadcn registry block. It combines a responsive card, email form, feature badges, gradient glow, and temporary success state. It depends on React, Framer Motion, Lucide icons, shadcn Badge, Button, Card, and Input components, plus Tailwind theme utilities.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of tripled-newsletter-signup-block-shadcnui at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tripled-newsletter-signup-block-shadcnui at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tripled-newsletter-signup-block-shadcnui at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

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.

Harness measurements recorded for tripled-newsletter-signup-block-shadcnui
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal73.5 KB (138.9 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 2m 17s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/input.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A polished, responsive starting point with a clear success transition, but it is presentation code rather than a working newsletter integration. It needs a shadcn-style setup to mount, and teams should wire the form, consent link, and claims before shipping.

Use it if

  • You want a prominent newsletter callout with responsive stacking and motion already composed.
  • Your app already uses shadcn components, Tailwind theme tokens, and the standard path alias.
  • You can connect the submit handler to a real mailing-list service and replace the sample claims.

Skip it if

  • You need a production subscription flow that already validates, persists, and confirms signups.
  • You are keeping animation and client-side dependency overhead out of a simple email form.
  • Your design system does not use shadcn primitives or Tailwind utility classes.
  • You need consent copy, privacy links, or subscriber claims driven by your own data without editing the component.

Install

Installation record for tripled-newsletter-signup-block-shadcnui
Declared dependenciesframer-motion, react, radix-ui
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, add compatible Badge, Button, Card, and Input primitives; configure the at-sign path alias; provide the shared lib/utils class helper; and add Tailwind theme tokens, Lucide React, and Framer Motion. Replace the local submit state with your newsletter API and make the privacy copy actionable.

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.

Alternatives

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.