Measured entry
motion-primitives-dock
hover-effect3dmotion on file
A client-side React dock composed from Dock, DockItem, DockIcon, and DockLabel exports. It ships as a shadcn registry TSX file, uses Motion for cursor-driven magnification and tooltip transitions, and expects Tailwind utility classes plus a cn helper resolved through the usual project alias.



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.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 69.6 KB (135.0 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 26.84s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/dock.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A polished, configurable dock for pointer-heavy React interfaces, with clean mounting and responsive behavior in the prepared harness. It does not work bare and needs a shadcn-style setup, including the expected utility helper and import alias.
Use it if
- You need a desktop-style application launcher whose items enlarge as the pointer approaches.
- You want composable dock items, icons, and hover or focus labels rather than a fixed menu schema.
- Your React interface already uses Tailwind and Motion, so the component fits the existing stack.
Skip it if
- You want to avoid adding Motion for a single navigation effect.
- Your interface is primarily touch-driven, where cursor-distance magnification adds little value.
- You require native button elements and their default semantics without adapting the dock item markup.
- Your project does not use Tailwind and you do not want to translate the utility classes.
Install
| Declared dependencies | motion |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, install Motion, provide Tailwind with the referenced utility classes, add a class-name merging helper compatible with cn, and either configure the source alias for that helper or change the import. Render it in a client-capable React boundary.
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/ibelick/motion-primitivesAlternatives
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.
- eldora-card-flip-hover3d
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- uilayouts-btn-hover-left-flip3d
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- uilayouts-btn-hover-down3d
- Renders
- YES
- A11y
- 0
- Gzip
- 17.6KB
- Bare
- pass
- Prov
- NO
- uilayouts-btn-hover-multiplegradient-glow
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- magicui-cool-modespatial
- Renders
- YES
- A11y
- 0
- Gzip
- 21.8KB
- Bare
- pass
- Prov
- NO
- uilayouts-hovercard2gradient-glow
- Renders
- YES
- A11y
- 0
- Gzip
- 24.0KB
- Bare
- pass
- Prov
- NO