Measured entry

kokonut-attract-button

buttondark-futuristicmotion on file

A client-side React call-to-action that pulls a scattered particle field into a violet button on hover or touch and swaps its label during the interaction. It ships as a shadcn registry component and depends on React, Motion, Lucide, the shadcn Button primitive, Tailwind utility classes, and the local cn helper.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of kokonut-attract-button at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of kokonut-attract-button at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of kokonut-attract-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 kokonut-attract-button
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal70.5 KB (135.9 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 2m 16s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/components/kokonutui/attract-button.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A focused novelty button that builds, mounts, and stays within the tested viewports, with no detected accessibility violations. The interaction is legible on pointer and touch, but its dependency cost and wide particle field limit it to occasional hero use. It needs a shadcn-style setup rather than working in a bare React project.

Use it if

  • You want one playful focal action in a landing page or product reveal.
  • Your app already uses shadcn conventions, Tailwind utilities, Motion, and Lucide.
  • You can give the surrounding layout enough visual space for particles to spread around the control.

Skip it if

  • You need a restrained button for dense forms, tables, or repeated actions.
  • Your motion policy requires an explicit reduced-motion fallback.
  • You want to avoid the substantial dependency cost of Motion for a single control.
  • Your design cannot accommodate particles drawing outside the button bounds.

Install

Installation record for kokonut-attract-button
Declared dependencieslucide-react, motion, radix-ui
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 Motion and Lucide, provide a compatible Button component, create the cn class-merging helper, configure the at-sign path alias, and ensure Tailwind processes the supplied utility classes. Preserve the client-component boundary in frameworks that render on the server.

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