vibecodng.com

Free MCP betaIndex and tools live

Measured entry

originui-input-02

inputunclassified

A compact required email field example that pairs a visible label and required marker with a native input. It ships through a shadcn registry and depends on React, Tailwind theme classes, the registry's Input and Label primitives, the shared cn helper, and Radix UI for the label primitive.

Specimen
Harness screenshot of originui-input-02 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of originui-input-02 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of originui-input-02 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-input-02
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal14.2 KB (78.8 KB build, 64.6 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 1.04s
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, narrowly scoped required email field for teams already using the same component conventions. It builds and mounts cleanly in that environment, but it needs a shadcn-style setup and will not work as a bare drop-in.

Use it if

  • You need a labeled required email field that retains native browser validation.
  • Your app already uses shadcn conventions, Tailwind theme tokens, and the shared cn utility.
  • You want a small field example whose label association and responsive layout are already sound.

Skip it if

  • Your design system already provides a field wrapper with required, error, and help text states.
  • You need a framework-neutral input without Tailwind, registry aliases, or Radix UI.
  • You need validation messaging or an error state in the component itself rather than adding that behavior around it.

Install

Installation record for originui-input-02
Declared dependenciesradix-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 the Input and Label registry files, Radix UI, a compatible cn class-merging helper, Tailwind styles and theme tokens, then replace the registry path aliases with local imports.

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-12

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.