vibecodng.com

Free MCP betaIndex and tools live

Measured entry

magicui-interactive-hover-button

buttondark-futuristicmotion on file

A pill-shaped React button whose dot expands on hover while the label slides into an arrow-led replacement. It ships as a shadcn registry component and relies on Tailwind theme utilities, a local cn helper, and the ArrowRight icon from lucide-react.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of magicui-interactive-hover-button at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of magicui-interactive-hover-button at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of magicui-interactive-hover-button 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 magicui-interactive-hover-button
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical1
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 34.82s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/interactive-hover-button.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A focused effect with clean responsive behavior, but the demo exposes a critical accessible-name failure when no children are supplied. The bare mount also fails, so it needs a shadcn-style setup before it is usable.

Use it if

  • You want a compact call-to-action with a conspicuous hover transition.
  • Your app already uses shadcn conventions, Tailwind theme tokens, and lucide-react.
  • You can always provide meaningful button text and test the motion against your interaction states.

Skip it if

  • You need a self-contained button that drops into plain React without aliases or utility styling.
  • Your interface avoids hover-led effects because its primary use is touch or keyboard interaction.
  • You cannot guarantee meaningful children, since an empty instance produces an unnamed button.

Install

Installation record for magicui-interactive-hover-button
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 matching background, primary, and foreground tokens; provide the aliased cn utility or replace that import; install lucide-react; and require meaningful button children.

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/magicuidesign/magicui
License
MIT
Record published
2026-08-14

Alternatives

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