react-day-picker

npm package · declared by 50 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

Tools declared alongside this one, ranked by association strength
Declared with	Repositories	vs chance
date-fns	8 of 2,343	0.70
class-variance-authority	9 of 2,343	0.57
tailwind-merge	9 of 2,343	0.54
clsx	9 of 2,343	0.50
lucide-react	9 of 2,343	0.50
next	8 of 2,343	0.42
react-dom	9 of 2,343	0.34
react	9 of 2,343	0.33

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.