weswigham on v4.3.4
elibarzilay on main
DanielRosenwasser on main
feat(28491): add QF to declare … (compare)
amcasey on main
Make export-module and referenc… (compare)
The page looks the same at 2020 June 28
redux is not a good solution in general, its built framework agnostic so you end up with many layers of heavy abstractions just to change state.
"redux" for the store,
then to consume redux in react "react-redux"
then because you need logging so redux-logger
then you can't run async actions or debounce so you need redux-thunk or redux-sagas.
then because you get stuck in boilerplate hell you need redux toolkit
and then redux-toolkit imports immer
And then you haven't even reached the code-level abstractions. Then you need to implement actions/reducers/rootReducer to change your state from the top-down this strategy can't be codesplit on a route-level (in the sense that your rootReducer is always imported into the root of your application), The result is the promise of "scaleable" state management is really undermined from the get-go.
Try recoil instead, only uses the React library to achieve everything so feels free fluid to use and its bottom-up state management so codesplits easy.
useReducerbut it's a pain, esp. having to avoid accidentally mutating objects.