react-router-dom
npm package · declared by 75 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 |
|---|---|---|
| react-scripts | 8 of 2,343 | 0.61 |
| react-markdown | 15 of 2,343 | 0.49 |
| framer-motion | 14 of 2,343 | 0.48 |
| react-dom | 49 of 2,343 | 0.48 |
| lucide-react | 27 of 2,343 | 0.47 |
| react | 49 of 2,343 | 0.47 |
| remark-gfm | 12 of 2,343 | 0.43 |
| react-icons | 9 of 2,343 | 0.40 |
| tailwindcss | 9 of 2,343 | 0.38 |
| zustand | 8 of 2,343 | 0.34 |
| clsx | 14 of 2,343 | 0.29 |
| axios | 10 of 2,343 | 0.29 |
| tailwind-merge | 11 of 2,343 | 0.27 |
| class-variance-authority | 8 of 2,343 | 0.23 |
| zod | 8 of 2,343 | 0.08 |
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.