Olavo Parno

@sindresorhus thanks for your prompt reply. I took advantage of part of your debug methods and used with unstated-next, I have done a PoC here https://codesandbox.io/s/unstated-store-provider-k4h77. I called it `useLog`...

Hello again, I kinda of rewrote (thanks to [fabiospampinato](fabiospampinato)) part of overstateds debug logic so that I can enjoy it alongside with unstated-next. If anyone's into it too, check my...

Did you provide your app with a [Provider](https://github.com/jamiebuilds/unstated-next#example)? Sorry for the _gioco di parole_ lol. Anyway, could you show us some code or even reproduce it to a codesandbox? e.g.:...

If it does not work, try with hook composition https://codesandbox.io/s/unstated-store-provider-k4h77?file=/src/store/index.js

Can you share a bit of your code or even better reproduce it in a codesandbox of some sort? Would this perhaps help you out? https://github.com/jamiebuilds/unstated-next#tip-1-composing-containers

maybe these would help https://codesandbox.io/s/unstated-store-provider-k4h77?file=/src/store/index.js https://github.com/jamiebuilds/unstated-next#tip-1-composing-containers

> I saw those, but that seems like it conflates the states into one big container, no? yes, and it is left the responsibility to you to destruct what you...

> That would cause a bunch of over-rendering, no? Or is it going to happen anyways? I don't remember for those examples but it might if you don't control it...