effector vs @hookstate/core
effector and @hookstate/core have comparable adoption (406,673 vs 452,718 downloads per month). @hookstate/core ships 51% less gzipped JavaScript (6.0 kB vs 12.3 kB), which matters if bundle size is a priority. effector has been updated more recently, a sign of more active maintenance.
| Metric | effector | @hookstate/core |
|---|---|---|
| Weekly downloads | 108,584✓ | 84,848 |
| Monthly downloads | 406,673 | 452,718✓ |
| GitHub stars | 4,837✓ | 1,656 |
| Minified size | 28.9 kB | 23.4 kB✓ |
| Minified + gzipped | 12.3 kB | 6.0 kB✓ |
| Dependencies | 0 | 0 |
| Open issues | 156 | 32✓ |
| Last commit | 2026-05-13✓ | 2025-03-20 |
| Latest version | 23.4.4 | 4.0.2 |
| License | MIT | MIT |
When to choose which
effector
Reactive logic from events, stores and effects.
Choose it when: Complex reactive business logic you want strongly typed and framework-agnostic, decoupled from the view.
- + Powerful reactive primitives
- + Excellent TypeScript
- + Framework-agnostic
- - Smaller community
- - New vocabulary to learn
@hookstate/core
Nested state via proxies with a plugin system.
Choose it when: You manage deeply nested state and want fine-grained updates plus plugins (persistence, validation).
- + Fine-grained nested updates
- + Plugin system
- - Small community
- - Less momentum than peers
Feature comparison
| Feature | effector | @hookstate/core |
|---|---|---|
| Paradigm | Events / effects | Proxy store |
| First-class TypeScript | ✓ Yes | ✓ Yes |
| Works outside React | ✓ Yes | Partial |
| Dedicated devtools | ✓ Yes | ✓ Yes |
| Built-in async / server state | ✓ Yes | Manual |
| Boilerplate | Medium | Low |
Related comparisons
Embed this comparison
A live badge for your README — it updates as the numbers change.
[](https://devcompare.dev/compare/effector-vs-hookstate-core)Data from npm, Bundlephobia and GitHub. Last updated 2026-06-02.