vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-correct-number-input

inputliquid-glassmotion on file

A client-side React quantity field shipped as a shadcn registry component. It combines an internally managed text input, floating label, bounded stepper controls, Motion animation, injected light and dark CSS, and an optional Web Audio tick. It depends on React and the Motion package, with no provider required.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of ruixen-correct-number-input at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-correct-number-input at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-correct-number-input 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-correct-number-input
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical2
Axe serious1
Axe moderate0
Axe minor0
Gzip marginal62.3 KB (127.8 KB build, 65.5 KB baseline)
Bare modeOK
Provider requiredNO
Demo usedwritten from the component source API

Verdict

It builds and mounts without special project scaffolding, but it is not production-ready unchanged. The interaction model is useful and self-contained, yet the missing accessible names and label association, weak contrast, and blank widest capture require investigation and fixes before release.

Use it if

  • You need a compact quantity or amount field with configurable bounds, stepping, and a change callback.
  • You want a liquid-glass presentation and are comfortable adopting its embedded styles and entrance animation.
  • Your form can use internally managed state initialized by a default value.

Skip it if

  • You need an accessible control without modification, since the input lacks an associated label, the icon buttons lack accessible names, and some text contrast is insufficient.
  • You require a fully controlled field, because the component exposes a default value and callback but no value prop.
  • You need dependable visibility across wide layouts, since the widest harness capture rendered blank.
  • Your product cannot use browser-generated audio feedback or include the Motion dependency.

Install

Installation record for ruixen-correct-number-input
Declared dependenciesmotion
Missing on installnone
Bare installbuilds and mounts without the shadcn-style helpers
Providerno provider required in the harness

In a non-shadcn React project, add the Motion package, copy the client component into the app, and ensure the bundler supports client directives and CSS injected from JSX. Add a real label association, accessible names for both stepper buttons, stronger contrast, and disable or remove the Web Audio tick if sound is unsuitable.

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/ruixenui/ruixen.com
License
MIT
Record published
2026-08-16

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.