Measured entry

kibo-comparison

feature-gridminimal-flatmotion on file

A client-side before-and-after comparison slider shipped as source through a shadcn registry. It layers two supplied React views with an animated clipping boundary and supports drag or hover interaction. It relies on Tailwind utilities, a shadcn-style cn helper, Motion, and Lucide React.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of kibo-comparison at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of kibo-comparison at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of kibo-comparison 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 kibo-comparison
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowflagged at 375
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal71.9 KB (137.4 KB build, 65.5 KB baseline)
Bare modeOK
Provider requiredNO
Demo usedwritten from the component source API

Verdict

A clean, composable reveal control that builds and mounts without special providers. It is a practical pick for media comparisons, but teams should add keyboard controls and make the surrounding dimensions responsive before treating it as production-ready.

Use it if

  • You need an image or UI before-and-after reveal with either drag or hover behavior.
  • Your React app already uses Tailwind and can absorb Motion and Lucide React.
  • You want composable comparison panels rather than an image-only widget.

Skip it if

  • The comparison must fit a narrow viewport without adapting the fixed dimensions supplied by the caller.
  • You need complete keyboard operation out of the box, since the slider is focusable but has no arrow-key handling.
  • You want to avoid adding a substantial client-side animation dependency for one interaction.

Install

Installation record for kibo-comparison
Declared dependencieslucide-react, motion, clsx, tailwind-merge
Missing on installnone
Bare installbuilds and mounts without the shadcn-style helpers
Providerno provider required in the harness

In a non-shadcn project, add Motion and Lucide React, configure Tailwind, provide the background and muted foreground theme tokens used by the classes, and supply a cn utility backed by clsx and tailwind-merge. Keep it in a client-rendered React boundary.

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.

License
MIT
Record published
2026-08-17

Alternatives

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