redux-ecosystem-links VS Recoil

Yeah, from 2016-2018 I spent a lot of time cataloguing Redux-related libraries in the ecosystem, and I definitely saw several addons that were meant to record Redux actions and send them to a server for devs to use in debugging. Totally feasible! (and tbh that's the kind of thing Redux was meant to enable in the first place.)

FWIW, there are some various other third-party replacements for combineReducers that might be useful (see https://github.com/markerikson/redux-ecosystem-links/blob/master/reducers.md ), but you'd have to specifically choose to use them yourself, and on top of that createSlice wouldn't be expecting a third arg or pass it through to its case reducers.

Atom-based: splits states into tiny pieces of data called atoms, which can be written to and read from using React hooks. In this group, we have Recoil and Jotai.

recoil -> Designed to solve a specific problem. Not good for all use cases. Understand it first! You can learn more about it here.

Recoil Official Website

Recoil 🌀

Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.

However you may find better luck with Recoil which is developed by Meta, and is designed to work with Async data, and is a much simpler project to get started with.

Recoil introduced a new pattern for storing state and propagating updates. This atomic model has proven to scale up better than the singleton model at the cost of some hefty learning curves.

recoil is extremely similar to Riverpod but for React (both are backed by a data flow graph).

Before we proceed you can check the project on github. This implementation is for learning purposes, for production use check Jotai or Recoil.