sonner
npm package · declared by 116 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 with | Repositories | vs chance |
|---|---|---|
| next-themes | 18 of 2,343 | 0.66 |
| class-variance-authority | 25 of 2,343 | 0.65 |
| cmdk | 10 of 2,343 | 0.64 |
| tailwind-merge | 26 of 2,343 | 0.63 |
| clsx | 26 of 2,343 | 0.58 |
| react-hook-form | 9 of 2,343 | 0.58 |
| @radix-ui/react-select | 10 of 2,343 | 0.57 |
| @radix-ui/react-label | 10 of 2,343 | 0.57 |
| @radix-ui/react-slot | 15 of 2,343 | 0.57 |
| lucide-react | 24 of 2,343 | 0.55 |
| date-fns | 10 of 2,343 | 0.54 |
| @radix-ui/react-dialog | 11 of 2,343 | 0.54 |
| tailwindcss-animate | 10 of 2,343 | 0.53 |
| next | 22 of 2,343 | 0.46 |
| react-dom | 29 of 2,343 | 0.42 |
| react | 29 of 2,343 | 0.41 |
| zod | 16 of 2,343 | 0.34 |
Every pair above is counted from the same evidence: repo manifest.
Used instead
candidates · shares a neighbourhood and refuses to co-occurNo 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.