effector vs @rematch/core

effector is downloaded 2.6× more often than @rematch/core (406,673 vs 154,354 per month), so it has the larger community and more answered questions online. @rematch/core ships 83% less gzipped JavaScript (2.1 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.

Metriceffector@rematch/core
Weekly downloads108,58438,752
Monthly downloads406,673154,354
GitHub stars4,8378,415
Minified size28.9 kB6.1 kB
Minified + gzipped12.3 kB2.1 kB
Dependencies00
Open issues15626
Last commit2026-05-132023-09-27
Latest version23.4.42.2.0
LicenseMITMIT

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

@rematch/core

Redux reimagined around models, no boilerplate.

Choose it when: You like Redux semantics but want models with built-in effects and far less setup.

  • + Model-based, low boilerplate
  • + Redux devtools
  • + Framework-agnostic
  • - Small community
  • - Less active than RTK

Feature comparison

Featureeffector@rematch/core
ParadigmEvents / effectsRedux models
First-class TypeScript✓ Yes✓ Yes
Works outside React✓ Yes✓ Yes
Dedicated devtools✓ Yes✓ Yes
Built-in async / server state✓ Yes✓ Yes
BoilerplateMediumLow

effector

Business logic with ease

@rematch/core

A Redux Framework

Related comparisons

Embed this comparison

A live badge for your README — it updates as the numbers change.

effector vs @rematch/core downloads
[![effector vs @rematch/core](https://devcompare.dev/badge/effector-vs-rematch-core.svg)](https://devcompare.dev/compare/effector-vs-rematch-core)

Data from npm, Bundlephobia and GitHub. Last updated 2026-06-02.