react-easy-state VS use-context-selector

I've really enjoyed react-easy-state

For state, I love to use React Easy State.

react-easy-state was very easy.

If you want to try something a bit different with regards to state management, you can try: https://github.com/RisingStack/react-easy-state

Nope, react-easy-state is much easier: https://github.com/RisingStack/react-easy-state

I personally prefer to work with react-easy-state instead of using Redux or even the built-in state management in React.

Just started using react-easy-state in a project, and I have to say I love it. In the past, I used Redux/RTK for global state management, along with Redux Thunk or Redux Saga for side effects. In contrast, react-easy-state is easy and requires so much less boilerplate to setup and worry about. I’m fully comfortable using Redux in apps and have done it plenty of times, but I love how react-easy-state just works. It’s amazing being able to mutate the state from anywhere, inside and outside of components, and have it immediately reflected by components, without installing any plugins and having complex config files.

I am a big fan of react-easy-state, which uses proxies to automatically trigger re-renders when you mutate any state that the component depends on. It's a bit of a different way of using state management compared to typical immutable state examples, but it allows for some very straightforward code without much boilerplate around it.

The app for people to submit orders (drinks-user) is just a form and to manage state, I'm using React-easy-state

Use jotai, or as someone else mentioned, zustand. React Context out of the box requires a very deliberate mental model due to a lack of tooling around selecting slices of state. This is why packages like react-context-selector exist: https://github.com/dai-shi/use-context-selector

Unless I've missed it, context doesn't have selector IIRC. You'd have to use a third party solution useContextSelector

How does this differ from https://github.com/dai-shi/use-context-selector?

you can always split out context state or use a library to help with rerender issues like https://github.com/dai-shi/use-context-selector, or just switch to jotai or something else if you want something more ergonomic or better design patterns.

If you don't want to swap out useContext, you could always use useContextSelector, which helps you limit what props in the context should rerender the component.

I wouldn't call this easy

It wouldn't be clear to anyone learning Context API either. At least, not using official docs. Because Context API is not supposed for state management, and if you for some unknown reasons try to roll your own state management on top of it, you have to use tricky libraries to work around the issues resulting from such abuse.

Any time anything in the context changes, any component that is consuming it will re-render. If you use it for frequently changed values, this library is needed to reduce unnecessary re-renders.

Use of this implementation of useContextSelector

Another technology I use regularly is Redux. But this time I wanted to manage the global state in a simpler and clearer way just using React hooks. I decided to go with a simple useReducer combined with theuseContextSelector hook which will avoid the whole application’s re-render caused by the native useContext hook.