riivault_

next

npm package · declared by 292 of 2,343 sampled repositories · graph computed 2026-08-24

Counted from the runtime dependencies public repositories declare — not the resolved tree. A transitive dependency is a consequence; a declared one is a choice. Development dependencies are excluded because they repeat across every project in a language regardless of what is being built.

Declared with

ranked by association, not by count
Declared withRepositoriesvs chance
react-dom187 of 2,3430.74
react188 of 2,3430.73
tailwind-merge82 of 2,3430.64
next-themes52 of 2,3430.64
class-variance-authority71 of 2,3430.62
clsx88 of 2,3430.61
@radix-ui/react-slot50 of 2,3430.58
lucide-react82 of 2,3430.57
@vercel/analytics34 of 2,3430.55
@radix-ui/react-dialog36 of 2,3430.53
tailwindcss-animate33 of 2,3430.53
@radix-ui/react-dropdown-menu30 of 2,3430.52
react-icons30 of 2,3430.49
@radix-ui/react-label25 of 2,3430.49
next-auth13 of 2,3430.48
next-intl13 of 2,3430.48
react-hot-toast17 of 2,3430.47
@radix-ui/react-accordion13 of 2,3430.47
@vercel/speed-insights11 of 2,3430.47
@next/bundle-analyzer11 of 2,3430.47

Every pair above is counted from the same evidence: repo manifest.

Used instead

candidates · shares a neighbourhood and refuses to co-occur

No alternative measured. A pair qualifies only if it shares a neighbourhood and then fails to appear together against an expectation that it would — and almost everything that shares a neighbourhood does appear together. That is the test working, not a gap in the data: similarity alone would list this tool’s closest neighbours as alternatives, and most of them are things it is used with.