Measured entry

ruixen-motion-file-tree

transition-effectunclassifiedmotion on file

A client-side React file tree that recursively renders files and folders, keeps expansion and selection state internally, and animates nested groups with Motion. It ships as a shadcn registry component and depends on Motion, Lucide icons, Tailwind theme classes, and a local cn utility backed by clsx and tailwind-merge.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of ruixen-motion-file-tree at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-motion-file-tree at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-motion-file-tree 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 ruixen-motion-file-tree
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal72.2 KB (137.7 KB build, 65.5 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 1m 22s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/components/ruixen/motion-file-tree.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A sound choice for a small animated file browser when its intentionally narrow API is enough. It builds and mounts in the prepared harness, but the bare failure confirms that it needs a shadcn-style setup, including the expected utility alias and theme classes.

Use it if

  • You need a compact, read-only project or document navigator with animated folder disclosure.
  • Your app already uses shadcn conventions, Tailwind theme tokens, and the local cn helper.
  • Uncontrolled expansion state and a simple node-selection callback fit your interaction model.

Skip it if

  • You need controlled expansion, lazy loading, editing, drag and drop, or virtualization for a large tree.
  • You require full keyboard tree navigation and keyboard selection behavior beyond folder toggling.
  • You want to avoid adding Motion and an icon package for a small navigation widget.

Install

Installation record for ruixen-motion-file-tree
Declared dependenciesmotion, lucide-react, clsx, tailwind-merge
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, install Motion, Lucide React, clsx, and tailwind-merge; add a cn helper at the expected utility alias or rewrite that import; and provide Tailwind styles plus the accent, muted, primary, and foreground theme tokens used by the component.

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