Measured entry

ruixen-pricing-section-vertical

pricingunclassified

A client-side React pricing section distributed as a shadcn registry item. It pairs a service overview with stacked plan cards, feature checklists, and call-to-action buttons. It depends on shadcn Card, Button, and Separator primitives, the usual path alias and utility behind those primitives, plus lucide-react.

Specimen
Harness screenshot of ruixen-pricing-section-vertical at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-pricing-section-vertical at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-pricing-section-vertical 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 ruixen-pricing-section-vertical
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate1
Axe minor0
Gzip marginal30.6 KB (96.0 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 31.76s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/card.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A practical starting point for service-led pricing pages, with responsive rendering and a clearly emphasized plan. It needs a shadcn-style setup to build and mount, and the heading order needs correction before production use.

Use it if

  • You want a split layout that explains services beside a short set of vertically stacked plans.
  • Your product has straightforward tier features that can be edited directly in the component.
  • Your app already uses shadcn primitives and theme tokens.

Skip it if

  • Pricing must come from a billing system, CMS, or reusable data model without refactoring the hardcoded plan array.
  • You need working checkout or contact behavior out of the box, because the buttons have no handlers or links.
  • You require a clean heading hierarchy without first correcting the section labels flagged by the accessibility check.
  • You want plans visible early on narrow screens, where the explanatory column comes before every card.

Install

Installation record for ruixen-pricing-section-vertical
Declared dependencieslucide-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

A non-shadcn project must add Tailwind theme tokens and utilities, configure the path alias, provide the shared class-name utility, and install compatible Card, Button, and Separator primitives with their Radix dependency and lucide-react. Wire each button to the intended flow.

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.