reactn VS unstated-next

Have a look at ReactN

If you want to move to hooks for state management I suggest ReactN.

ReactN because it demonstrated engaging with and supporting customers to balance priorities and deliver results.

My open source React state management library ReactN helped me get a job at AWS, because it showed customer obsession.

I love ReactN.

Look into ReactN which uses hooks, has lower overhead, no boilerplate, and is much easier to use and learn than Redux.

I myself started a few years ago using ReactN which intends to implement global state management in a similar way like the local state in react works. But since this is a monolithic store too I recently switched to (the very unknown) React Capsule which is from the same dev, extremely lightweight, similar to recoil and intends to use encapsulated state which can be used either in plain JS, in class components, as well as in function components.

I'm still using unstated-next, its another straightforward one that extends useContext

Of cource, we can mix Hook result values with a local state or something in the place among and , so we can adjust values a bit easily. (In easy case, Unstated Next is helpful.)