React state management is usually a trade-off. You either deal with "Provider Hell" using the Context API, or you have to learn a completely new syntax (and rewrite your logic) for libraries like Redux or Zustand.
I built react-state-custom to bridge this gap. It lets you turn standard Custom Hooks into performant Global Stores with zero boilerplate.
Why I built it:
I love the simplicity of React Hooks (useState, useEffect), but I hate prop-drilling. I wanted a way to write a normal hook and just... "make it global" without wrapping my app in 50 different providers.
The 3 Killer Features:
- No More Provider Hell Instead of manually wrapping components in , , etc., react-state-custom uses a single dynamic root (). It creates stores on demand when components ask for them.
- Built-in Lifecycle Management (The "Grace Period") This is where it beats standard global state libraries. You can define a "grace period" (e.g., 2000ms). If a user navigates away from a page and comes back within 2 seconds, the state is preserved. If not, it auto-cleans up. No more stale data bugs or manual useEffect cleanup.
- Performance via Subscriptions It uses an event-driven subscription model. If your hook returns 10 values but a component only uses 1, that component only re-renders when that specific value changes. How it works:
Top comments (0)