vibecodng.com

Free MCP betaIndex and tools live

Measured entry

magicui-dock

navbarspatialmotion on file

A client-side React recreation of a desktop application dock, shipped as Dock and DockIcon source through a shadcn registry item. It uses Tailwind utility classes, Motion springs and transforms for pointer-driven magnification, class-variance-authority for variants, and a shadcn-style cn utility backed by class merging helpers.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of magicui-dock at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of magicui-dock at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of magicui-dock 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-dock
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal71.2 KB (136.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 4m 43s
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 fit for desktop-oriented launchers when the magnification effect earns its Motion dependency. It builds and mounts cleanly in the prepared harness, but the bare failure shows that it needs a shadcn-style setup, especially the cn utility and path alias. Add real interactive elements and accessible names yourself.

Use it if

  • You need a compact launcher or navigation strip whose icons magnify around a desktop pointer.
  • Your React app already uses Tailwind, Motion, and shadcn-style source components.
  • You want control over icon sizing, magnification range, alignment, and custom children.

Skip it if

  • Your navigation must arrive with keyboard behavior, link semantics, labels, and focus treatment already defined.
  • Most users are on touch devices, where its pointer-distance interaction offers little benefit.
  • You want to avoid adding Motion and its associated client-side weight for a small navigation element.
  • Your design system does not use Tailwind utilities or shadcn-style path aliases.

Install

Installation record for magicui-dock
Declared dependenciesmotion, 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 Motion, class-variance-authority, Tailwind CSS, clsx, and tailwind-merge. Provide a cn helper at the expected utility alias or replace that import with your local equivalent, configure the alias, and ensure the file is compiled as a client component. Supply buttons or links, accessible names, and focus styles for each dock item.

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

Alternatives

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