vibecodng.com

Free MCP betaIndex and tools live

Measured entry

fancy-drag-elements

hover-effectspatialmotion on file

A client-side React wrapper that turns each child into an absolutely positioned, freely draggable Motion element inside a constrained container. It ships as a shadcn registry TypeScript file, depends on Motion for gestures and inertia, and assumes utility classes for sizing and positioning.

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

Verdict

A focused free-drag primitive with sensible containment and stacking controls. It builds and mounts cleanly without framework scaffolding, but it leaves positioning, persistence, keyboard interaction, and semantic reordering to the host application.

Use it if

  • You are building a moodboard, playful canvas, or spatial cluster where items can be moved freely.
  • You want optional momentum, elastic dragging, containment, and bring-to-front behavior behind a small API.
  • Your parent layout can provide explicit space for absolutely positioned children.

Skip it if

  • You need a sortable list that updates order, persists positions, or emits drag results.
  • Keyboard users must be able to perform the same rearrangement without a pointer.
  • Children need to remain in normal document flow or must not begin from the same origin.
  • Adding Motion is too much dependency weight for a minor decorative interaction.

Install

Installation record for fancy-drag-elements
Declared dependenciesmotion
Missing on installnone
Bare installbuilds and mounts without the shadcn-style helpers
Providerno provider required in the harness

Install Motion, copy the client component into the project, and provide equivalents for its relative, full-size, and absolute utility classes if Tailwind is unavailable. Give the container a defined size, set initial child placement as needed, and add keyboard controls plus state persistence when dragging changes meaningful data.

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/danielpetho/fancy
License
MIT
Record published
2026-08-13

Alternatives

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