Measured entry

ruixen-gooey-pagination

navbarliquid-glassmotion on file

A client-side React pagination control shipped as a shadcn registry item. It renders inline-styled glass dots with an SVG goo filter, animates the active marker through motion/react, keeps page state internally, and can emit an optional Web Audio tick.

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

Verdict

Visually distinctive and easy to drop into React, but not production-ready as navigation. The harness mounted it, yet wider captures were blank, and the source leaves arrow buttons unnamed and page dots outside keyboard semantics. Use it only after accessibility work and responsive investigation.

Use it if

  • You need a compact, decorative paginator for a small set of pages.
  • Your integration can consume a zero-based change callback while the component owns the active page state.
  • You want styling that is contained in the component and does not require a theme provider or shared utility layer.

Skip it if

  • You need production-ready accessible navigation without modification, since the arrow buttons lack names and the dot targets are not keyboard controls.
  • You need controlled pagination tied directly to routing or external state, since there is no current-page prop.
  • You cannot investigate viewport-specific rendering, since the harness produced blank wider captures despite a successful mount.
  • Your dependency policy excludes Motion or optional browser-generated interaction sounds.

Install

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

In a non-shadcn app, copy the TSX component into a client-rendered React module, install Motion, and ensure the bundler supports motion/react. No provider or shared utility layer is required. Add accessible names, keyboard-capable page controls, visible focus treatment, and suitable contrast before release.

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.

Alternatives

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