use-immer VS MobX

The use-immer package additionally provides a useImmerReducer ****function that allows you to make state transitions via direct mutation, but under the hood creates an immutable copy using Proxies in JavaScript.

Apply useImmer to the top component state and the dream is complete.

If you want to use mutating code while ensuring that the final update is immutable, I recommend checking out useImmer (and useImmerReducer) - it uses immer to track mutations and do them immutably for you.

If you find yourself using multiple objects or in your state, it may be worth it to install a library like immer. Immer provides a proxy object, referred to as a draft, so while your code appears similar to a direct mutation of state, a copy is created under the hood when an update when immer is used.

useImmer is also pretty nice too - useReducer is definitely the way if you only want specific ways to manipulate the object though (and useImmerReducer can make writing the logic for that easier too)

Within the component itself, I used a useImmer hook for the state, as it lets me write mutating code while ensuring that the actual update is immutable - but if you're only holding your array in the useState hook, a shallow clone would work fine. js setItems(items => arrayMove([...items], ...params))

React is a lot more strict, and for what we need we cannot leave the state in individual components, we need to pull it up to the App component. Making modifications to deeply nested state is a lot of nasty code, fortunately React world has a solution - immer and its hooks version useImmer.

States can also be organized in some central places (aka. stores). You can use Tini Store (very simple, ~50 lines) or other state management solutions such as MobX, TinyX, ...

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

MobX

Mutable-based: leverages proxy to create mutable data sources which can be directly written to or reactively read from. Candidates in this group are MobX and Valtio.

Looks good! FWIW I always felt the observable pattern much more intuitive than the redux/reducer style. Something like https://mobx.js.org/

Things get hairy in both, but redux pattern feels so ridiculously ceremonially to effectively manage a huge global state object with a false sense of "purity".

Observables otoh say "fuck it, I'm mutating everything, do what you want with it".

MobX Documentation

There's also others libraries like https://github.com/mobxjs/mobx which aren't specific to RN but can be used in any JS environment.

Valtio is like simplified MobX

Link: https://mobx.js.org