// the find
jherr/nextjs-state-management
nextjs-state-management video code
A collection of near-identical Next.js pages apps, each wired to a different state management library (Context, Jotai, MobX, React Query, Redux, RxJS, Zustand, plain useState) as companion code for a YouTube video. It's for someone trying to decide which state library to reach for and wants to see the same toy problem solved eight different ways side by side.
Directly comparable implementations — same feature built eight times means you can diff `store.tsx`/`store.ts` across folders and see exactly what each library's API costs you in boilerplate. Good spread of approaches, from no-library (useState, Context) to heavier tools (Redux, MobX, RxJS), plus the increasingly popular lightweight options (Zustand, Jotai). Each variant is a self-contained Next.js app with its own package.json and lockfile, so you can clone one folder and run it without pulling in the rest.
Dead since October 2022 — Next.js has moved through several major versions since (App Router wasn't even default yet), so the pages-router patterns here don't reflect how you'd actually structure a modern Next.js app. No README at the repo root explaining the shared example or what each subfolder is demonstrating beyond library name; you have to watch the referenced video to get the pitch. It's demo code, not a library: no tests, no CI, and the state logic in each example is trivial enough that it doesn't surface the real tradeoffs (async handling, derived state, devtools) that actually differentiate these libraries at scale.