typescript
npm package · declared by 80 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 |
|---|---|---|
| @types/node | 25 of 2,343 | 0.76 |
| @types/react-dom | 19 of 2,343 | 0.73 |
| @types/react | 19 of 2,343 | 0.73 |
| autoprefixer | 11 of 2,343 | 0.53 |
| postcss | 14 of 2,343 | 0.52 |
| eslint | 10 of 2,343 | 0.51 |
| tailwindcss | 15 of 2,343 | 0.49 |
| react | 29 of 2,343 | 0.26 |
| react-dom | 27 of 2,343 | 0.25 |
| next | 16 of 2,343 | 0.24 |
| class-variance-authority | 8 of 2,343 | 0.21 |
| lucide-react | 11 of 2,343 | 0.20 |
| tailwind-merge | 9 of 2,343 | 0.20 |
| clsx | 10 of 2,343 | 0.19 |
| zod | 14 of 2,343 | 0.18 |
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.