fix error with hot module replacement

[PatrykWalach]

When hot module replacement happens the parentCache doesn't change but useEffect is rerun (don't know what the exact cause of this is), when useEffect is rerun it crashes, because it can't access cacheItem anymore.

The extra check makes sure effect is run once per parentCache (maybe we are compatible with StrictMode now?)

[rbalicki2]

I now see this, btw... I'll investigate what is going on.

My suspicion is that the component cache is caching the old component. I haven't looked into this.

I think in terms of strict mode, we're still likely incompatible. Basically, useLazyReference will uncommit, dispose, and re-commit, which does not re-issue the query.

I am philosophically opposed to that — queries aren't always re-issuable! But we can probably warn loudly and reissue queries. Just sucks if you're lazily doing a mutation, which is possible :-P

Once #252 lands, there probably won't be a huge need for lazy loaded queries though

[rbalicki2]

https://isograph.dev/docs/faq/#why-does-isograph-not-support-strict-mode

[PatrykWalach]

Now useLazyDisposableState should work correctly, it will setup cleanup once for every parentCache

[PatrykWalach]

This is not erroring, but the environment cache will indeed produce stale components

PS. so if we fix component cache we will receive fresh components, and it shouldn't cause these errors

PPS. the issue seems to be components get hot reloaded, but somehow iso("entrypoint ...") does not