vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-tree-node-tooltip

tooltipunclassifiedmotion on file

A recursive client-side file tree whose folder rows expand with Motion and whose labels open Radix-based tooltips. It ships as shadcn registry source, not a standalone package, and depends on React, Motion, Lucide icons, Tailwind theme classes, the cn utility, and the registry tooltip component.

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

Verdict

A reasonable starting point for small, decorative file trees, with clean recursive data handling and working animation. It needs a shadcn-style setup, lacks full accessible tree behavior, and the blank wide-view capture deserves investigation before production use.

Use it if

  • You need a compact file or category tree with per-node explanatory tooltips.
  • Your app already uses shadcn conventions, Tailwind theme tokens, and the cn helper.
  • Animated expansion and simple click-to-toggle folders match your interaction model.

Skip it if

  • You need full tree semantics, arrow-key navigation, selection state, or focus management.
  • You are rendering a large or deeply nested dataset that needs virtualization or centralized expansion state.
  • You want to avoid Motion, Lucide, and Radix tooltip dependencies for a small navigation widget.
  • You need a component that drops into a plain React project without project aliases or design-system utilities.

Install

Installation record for ruixen-tree-node-tooltip
Declared dependenciesmotion, lucide-react, radix-ui, 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, add Tailwind with the expected theme tokens, configure the at-sign source alias, provide a cn helper using clsx and tailwind-merge, install Motion and Lucide, and add compatible Radix tooltip primitives. The file must run as a client 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.

Author repository

github.com/ruixenui/ruixen.com
License
MIT
Record published
2026-08-18

Alternatives

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