vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-notification

alertglassmorphismmotion on file

A client-side React notification stack shipped as a shadcn registry UI file. It owns default or supplied items, layers them with Motion spring animation, and dismisses the top card by a rightward drag. It depends on motion/react and browser Web Audio for its optional dismissal tick, while its styling is embedded in the component.

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

Verdict

A focused, convincing choice for a gesture-led notification stack, and it runs without shared shadcn utilities or a provider. It is not ready as a general-purpose alert system: contrast needs correction, semantics are absent, and dismissal is pointer-centric. Adopt it when the interaction earns the Motion dependency and you can complete the accessibility work.

Use it if

  • You want a compact stack of recent notifications where the newest item is the primary focus.
  • Your interface benefits from gesture-based dismissal and animated depth rather than conventional toast controls.
  • You can connect supplied items and the dismissal callback to application-owned notification state.

Skip it if

  • You need notifications announced by assistive technology or dismissible from a keyboard without modifying the component.
  • Your accessibility bar cannot accept the current low-contrast secondary text.
  • You need actions, persistence, automatic expiry, or dismiss controls beyond a rightward drag.
  • Adding Motion is not justified for a small notification treatment.

Install

Installation record for ruixen-notification
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 client component into your source tree, install the Motion package, and ensure your React framework supports client components. Wire items and the dismissal callback to your own notification state, and disable sound if Web Audio is unwanted. No provider or shared utility layer is required.

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 alert pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.