state VS constate

If you like to use something even simpler you can check my lib here https://github.com/bit-about/state. It’s production ready and battle tested :)

I’ve used almost all libs you mentioned, and then created my own https://github.com/bit-about/state . I use it on my newest projects and fills all my needs :3

Hey guys! I've released complementary libraries BitAboutState and BitAboutEvent and I'd like to hear your feedback. I wanted to achieve the feeling that these libraries "should be built into React".

Key features:

100% Typescript with state types deduction

Efficient and hook-based

With extra static access to core functionality (without hook)

No centralized providers (decentralized states and events)

Tiny - max 2.5kB

These libraries force, in my opinion, the cleanest way to design code architecture in React projects.

The libraries are production-ready and this week I introduced them to fresh React-Native commercial projects in my company. We will see them on the battlefield :)

BitAboutEvent: https://github.com/bit-about/event

BitAboutState: https://github.com/bit-about/state

BitAboutState: https://github.com/bit-about/state

Another one I like is https://github.com/diegohaz/constate, also <100 lines, but it makes contexts much easier to use. FB also uses mostly contexts for state management.

Github

constate - React Context + State

Constate hook provides lifting local state to React Context Level. So you can access/update state variables anywhere in the application with few lines of code. This is useful when you use the same state in multiple components. For example, you have Themes, Colors, Fonts used in multiple components, Users are allowed to change at one place and it should be reflected in the whole application. Package written in TypeScript and very compact.