vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-auto-scrolling-client-carousel

carouselunclassifiedmotion on file

A client-side React logo carousel shipped as a shadcn registry component. It renders two continuously moving ribbons in opposite directions, injects its own CSS keyframes, and accepts custom labels, logos, links, and speed. It has no extra package dependencies, but it expects Tailwind utility classes and the usual cn helper at @/lib/utils.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of ruixen-auto-scrolling-client-carousel at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of ruixen-auto-scrolling-client-carousel at 768 pixels wide
Harness screenshot at 768 pixels wide. This viewport scrolled sideways.
Harness screenshot of ruixen-auto-scrolling-client-carousel 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-auto-scrolling-client-carousel
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowflagged at 375, 768
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal27.2 KB (92.6 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 32.30s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/auto-scrolling-client-carousel.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A focused logo ribbon that builds, mounts, and passes the automated accessibility scan in the prepared harness. It needs a shadcn-style setup because the bare project cannot resolve its cn utility import. Use it when ambient motion fits the page, but fix narrow-screen overflow and reduced-motion behavior before production.

Use it if

  • You need a compact client or partner strip with continuous motion in both directions.
  • Your project already uses Tailwind and a shadcn-style source layout.
  • You want to provide custom React logo nodes or linked client names without adding a carousel library.

Skip it if

  • Your layout must avoid horizontal overflow on phone and tablet widths without further CSS work.
  • You need motion that pauses on hover or respects reduced-motion preferences out of the box.
  • You need keyboard controls, pagination, or user-driven carousel navigation.
  • Your project does not use Tailwind and you do not want to translate utility classes.

Install

Installation record for ruixen-auto-scrolling-client-carousel
Declared dependenciesnone declared
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 Tailwind with the foreground and muted-foreground theme tokens, create a cn class-merging helper, and either configure the @ alias to resolve lib/utils or change that import to your local path. Keep it in a client-capable 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.

Author repository

github.com/ruixenui/ruixen.com
License
MIT
Record published
2026-08-14

Alternatives

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