James Pearce

OK I like this. In the middle of a few other things but let's see...

OK, this API is going to land soon: There will also be hooks and support so this state can be tracked in a UI. Hoping this works for you!

OK, this is shipped in 5.3.0-beta.3. [Take a look](https://beta.tinybase.org/guides/releases/#v5-3) at the new methods, listeners and hooks, and see if it does what you need!

Yes... I've hit this in the past too. You currently need both the ui-react and ui-react-dom libraries to be the debug version (on the assumption they will be compiled away...

Apart from the presence of the inspector it's just that the debug version is not minified. If I can't fix it to be more intuitive, I will do a better...

Check out the new v5.0.0-beta.21 release: in it, the StoreInspector (now called Inspector) is in its own module that can run in either debug or non-debug mode. Hoping we can...

I just started getting this in my tests after upgrading from 0.2.7 to 0.2.10, using Jest. Looks like 0.2.8 is where it starts failing. I can try to isolate more...

> I'm keen to reproduce this so we can sure it's prevented. Do you have a rough idea of the sequence that triggers it? I'm tempted to say I'm in...

Ah... this seems like a good old-fashioned bug.

Yeah, this was also affecting schema-based typing too. Unless everything was using the same import, the global context wasn't a singleton. This is fixed in 5.2.2 and sorry it took...