vibecodng.com

Free MCP betaIndex and tools live

Measured entry

originui-comp-50

inputminimal-flat

A client-side React credit-card field that groups card number, expiry, and security-code inputs, with card-brand detection and formatting from react-payment-inputs. It ships as a shadcn registry component and relies on the registry Input, Lucide icon, Tailwind theme utilities, and project alias conventions.

Specimen
Harness screenshot of originui-comp-50 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of originui-comp-50 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of originui-comp-50 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 originui-comp-50
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal69.6 KB (135.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 26.83s
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 solid checkout input for an existing shadcn-based app: it builds, mounts, adapts across tested layouts, and produced no detected accessibility issues. The dependency cost is notable for one field, and it needs a shadcn-style setup before it can run in a bare React project.

Use it if

  • You need a compact card-details control with formatting and card-brand feedback already wired.
  • Your app already uses shadcn registry components, Tailwind theme tokens, and the expected import aliases.
  • You are comfortable validating and submitting payment data through a separate payment flow.

Skip it if

  • You need a provider-hosted card field that keeps sensitive input outside your React application.
  • You want a dependency-light set of plain inputs without card detection or formatting logic.
  • Your design system does not use shadcn-style Input primitives or Tailwind utility classes.

Install

Installation record for originui-comp-50
Declared dependenciesreact-payment-inputs, 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 react-payment-inputs and Lucide React, install or recreate the registry Input primitive, configure Tailwind with the referenced theme tokens and variants, provide the project import alias, and add the class-name utility required by that Input implementation. Preserve the client-component boundary where the framework requires it.

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/origin-space/originui
License
MIT
Record published
2026-08-13

Alternatives

Other published entries for the input pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.