Measured entry
shadcn-context-menu
A copy-in React context menu built on Radix UI primitives. It ships as a client-side TypeScript source component with items, groups, checkboxes, radio choices, submenus, separators, labels, and shortcuts. Its presentation relies on lucide-react icons, a cn helper, Tailwind utilities, theme tokens, and animation classes.



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 | flagged at 375 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 58.7 KB (124.1 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 27.53s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/components/ui/context-menu.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A capable, accessible foundation for desktop context actions, with useful variants and submenu support. It mounts cleanly in the prepared harness, but the bare build fails on the missing cn utility import, so it needs a shadcn-style setup before it can be dropped into another project. Review narrow layouts before adopting it.
Use it if
- You need a desktop right-click menu with keyboard navigation and focus handling supplied by Radix UI.
- Your product needs nested actions, checked options, radio selections, or destructive menu items in one consistent API.
- Your app already follows shadcn conventions and you want source code that can be edited locally.
Skip it if
- Your interface is primarily touch-driven and cannot provide an obvious alternate way to reach the same actions.
- You need a dependency-light menu and do not want Radix UI or the supporting icon and styling setup.
- Your narrow layout cannot tolerate the horizontal overflow observed in the compact viewport.
- You want a packaged component with isolated styles instead of source tied to app-level Tailwind tokens.
Install
| Declared dependencies | radix-ui |
|---|---|
| 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 |
For a non-shadcn project, add Radix UI and lucide-react, provide a compatible cn class-merging helper, replace or configure the alias import, and supply the Tailwind theme tokens and animation utilities used by the component. Keep it in a client-rendered boundary where the framework requires one.
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/shadcn-ui/uiAlternatives
Other published entries for the dropdown pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- tripled-context-menu-shadcnuiminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 61.1KB
- Bare
- pass
- Prov
- NO
- shadcn-dropdown-menuunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 44.4KB
- Bare
- fail
- Prov
- NO
- originui-comp-131minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 58.1KB
- Bare
- fail
- Prov
- NO
- neobrutalism-dropdown-menubrutalism
- Renders
- YES
- A11y
- 0
- Gzip
- 58.5KB
- Bare
- fail
- Prov
- NO
- neobrutalism-context-menubrutalism
- Renders
- YES
- A11y
- 0
- Gzip
- 58.8KB
- Bare
- fail
- Prov
- NO
- ruixen-account-menuunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 60.6KB
- Bare
- fail
- Prov
- NO