rematch VS unstated-next

Link: https://rematchjs.org/

I use Rematch. It’s built on top of redux but without all the ridiculous boiler plate. I looked into Redux Toolkit but found it still requiring too much unneeded code.

Rematch

Rematch is a nice wrapper on redux. I’d also recommend recoil, not sure if they’re stable yet but I’ve used it in production without any issues. Depends on the complexity of your app, may be overkill using these libraries.

Rematch - this is what I used last time after careful evaluation.

I’ve always found Redux too verbose and cumbersome. Luckily I found Rematch. It is Redux best practices without the boilerplate

I'm working on a Grid component which uses react window to render the cells, Each cell uses 5 HOCs where they each subscribe to the store(I use rematch) with connect and some of the HOCs have selectors where they compute some data with a relatively expensive function. I use lodash compose to merge all the HOCs and use it in the Cell component.

Rematch has been created a few years ago by Shawn McKay and Blair Bodnar, a pair of canadian programmers. It's a tiny but super powerful wrapper around Redux that reduces tons of boilerplate that Redux needs to operate.

Checkout Rematch as a redux implementation. It is build on top of redux, but removes all the horrible boilerplate and keeps the good parts.

I'm still using unstated-next, its another straightforward one that extends useContext

Of cource, we can mix Hook result values with a local state or something in the place among and , so we can adjust values a bit easily. (In easy case, Unstated Next is helpful.)