diegohaz

Author here.

This is an opinionated boilerplate that I use to create my own packages [1].

Feedback is appreciated.

[1] https://github.com/diegohaz?tab=repositories

The old context was indeed easier to use, but I think the new API is more explicit. It's easier to infer from where things are coming. It has great value in maintainability.

As I wrote in this article [0], I strongly believe that the new Context API can replace Redux in most apps, not because it's a Redux replacement, but mostly because they didn't need Redux in the first place.

People start their projects with Redux without knowing if they'll actually need it.

[0] https://medium.freecodecamp.org/reacts-new-context-api-how-t...

Feedback is really appreciated.

Repo: https://github.com/diegohaz/constate

Demo: https://codesandbox.io/s/7p2qv6mmq

This is something I needed in another project of mine, so I decided to abstract it into a new package: constate.

The goal was to use it to start building a simple application in the most simplest way: using React local state.

Whenever I feel the need to scale up and use some sort of global state, instead of adding redux, mobx or another complex library, I can just add a context property and everything works.

Feedback is really appreciated.

Repo: https://github.com/diegohaz/constate

Demo: https://codesandbox.io/s/7p2qv6mmq

This is something I needed in another project of mine, so I decided to abstract it into a new package: constate.

The goal was to use it to start building a simple application in the most simplest way: using React local state.

Whenever I feel the need to scale up and use some sort of global state, instead of adding redux, mobx or another complex library, I can just add a context property and everything works.