zustand

npm package · declared by 114 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
@tauri-apps/api	12 of 2,343	0.55
lucide-react	32 of 2,343	0.53
react-i18next	9 of 2,343	0.48
react	50 of 2,343	0.48
react-dom	48 of 2,343	0.48
i18next	9 of 2,343	0.47
remark-gfm	13 of 2,343	0.45
@radix-ui/react-select	8 of 2,343	0.42
react-markdown	11 of 2,343	0.40
tailwind-merge	17 of 2,343	0.39
framer-motion	9 of 2,343	0.37
class-variance-authority	14 of 2,343	0.37
clsx	18 of 2,343	0.36
react-router-dom	8 of 2,343	0.34
next	20 of 2,343	0.33
@radix-ui/react-slot	8 of 2,343	0.31
axios	9 of 2,343	0.27
zod	15 of 2,343	0.22

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.