vibecodng.com

Free MCP betaIndex and tools live

Measured entry

magicui-animated-beam

background-effectspatialmotion on file

A client-side React SVG overlay that draws an animated gradient path between two referenced elements. It ships as a shadcn registry TypeScript component, measures its container and endpoints with ResizeObserver, animates through Motion, and imports the usual shadcn cn utility alongside Tailwind utility classes.

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

Verdict

A focused connector effect with a sensible prop surface, but it is integration code rather than a standalone demo. The generic harness could not mount it because its required refs were absent, and a bare project needs a shadcn-style setup before it will build.

Use it if

  • You need to visualize a connection between two elements in an integration map or workflow diagram.
  • Your layout can provide stable refs for the container, source, and destination elements.
  • Your app already uses shadcn conventions, Tailwind utilities, and Motion.

Skip it if

  • You need a drop-in component that can render without wiring element refs.
  • Your interface must avoid continuous decorative motion or does not provide a reduced-motion treatment.
  • You want to avoid adding Motion for a single decorative connector.
  • The connected elements move independently without causing the observed container to resize.

Install

Installation record for magicui-animated-beam
Declared dependenciesmotion
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 React project, install Motion, provide a client-rendered environment and a ResizeObserver-capable browser, add a cn class-merging helper at the expected alias or change that import, and supply equivalent Tailwind utilities or replace the utility classes with your own CSS. Render it with valid container, source, and destination refs.

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-13

Alternatives

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