Measured entry

uilayouts-mesh-gradient-background

background-effectaurora-meshmotion on file

A full-viewport, client-side React hero built around a custom animated Three.js shader. It ships as a shadcn registry component and includes its own heading, canvas, camera controls, lighting, environment, and noise pass. It depends on Three.js, React Three Fiber, Drei, React Three Postprocessing, and Three type declarations.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of uilayouts-mesh-gradient-background at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of uilayouts-mesh-gradient-background at 768 pixels wide
Harness screenshot at 768 pixels wide. This viewport scrolled sideways.
Harness screenshot of uilayouts-mesh-gradient-background at 1440 pixels wide
Harness screenshot at 1440 pixels wide. This viewport scrolled sideways.

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 uilayouts-mesh-gradient-background
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowflagged at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal300.6 KB (366.1 KB build, 65.5 KB baseline)
Bare modeOK
Provider requiredNO
Demo usedwritten from the component source API

Verdict

It builds and mounts cleanly, but it is closer to a complete WebGL hero than a drop-in background. The hard-coded copy and viewport sizing need refactoring, and the observed overflow makes it a poor choice when responsive containment must work out of the box.

Use it if

  • You want an immersive WebGL hero whose copy and green shader treatment will be customized in source.
  • Your app already accepts the runtime and delivery cost of a Three.js scene for a prominent landing-page moment.
  • You need pointer-responsive motion and are prepared to define reduced-motion behavior yourself.

Skip it if

  • You need a reusable background that simply renders behind existing children; this component owns the page and hard-codes its heading.
  • Horizontal overflow at responsive widths is unacceptable without additional layout work.
  • Your bundle budget cannot justify a full Three.js, Fiber, Drei, and postprocessing stack for decoration.
  • You need a CSS-only fallback, server-rendered output, or motion preferences handled out of the box.

Install

Installation record for uilayouts-mesh-gradient-background
Declared dependenciesthree, @types/three, @react-three/fiber, @react-three/drei, @react-three/postprocessing
Missing on installnone
Bare installbuilds and mounts without the shadcn-style helpers
Providerno provider required in the harness

Add Three.js, React Three Fiber, Drei, React Three Postprocessing, and the Three type declarations. Keep the component behind a client boundary and support its Tailwind utility classes or replace them with local CSS. Refactor the full-viewport wrapper and hard-coded heading before embedding it.

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.

License
MIT
Record published
2026-08-18

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.