Feedback after reading 'No-boilerplate global state management in React' about reactn HOT 2 CLOSED

The Provider is currently the highest priority feature, as it's needed for concurrent server-side rendering. Whenever concurrent SSR is supported, I'll cut 1.0.0 of the package.

useGlobal as a hook works as you have it now, except I'm still very on the fence about nested values. I love them in concept, but it's about the performance ramifications of implementing them. Currently, you'd have to use useGlobal('y').

useGlobal() does return the entire global state and a setter for it.

I will separate component logic and hook logic when React's main package does the same (presumably deprecated components).

The day React deprecates components, I'll cut a release of ReactN that is hooks-only.

If I missed any requests, let me know. Otherwise, this can be closed. Provider is an open issue, and so is deep-nested subscriptions (y.x). I'm positive I won't drop component support any sooner than the aforementioned time.

from reactn.

Oh, and feel free to close this issue.

from reactn.