@types/node
npm package · declared by 44 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/react | 15 of 2,343 | 0.77 |
| @types/react-dom | 15 of 2,343 | 0.77 |
| typescript | 25 of 2,343 | 0.76 |
| eslint | 9 of 2,343 | 0.59 |
| autoprefixer | 8 of 2,343 | 0.56 |
| postcss | 10 of 2,343 | 0.54 |
| tailwindcss | 9 of 2,343 | 0.46 |
| next | 14 of 2,343 | 0.33 |
| tailwind-merge | 8 of 2,343 | 0.28 |
| clsx | 9 of 2,343 | 0.28 |
| react-dom | 17 of 2,343 | 0.26 |
| react | 17 of 2,343 | 0.25 |
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.