Jesse Koldewijn

Hey @anvesh-vanam for me reinstalling the the extension when noticing this behavior did the join. Had the same issue on Chrome a couple of times.

Can confirm that the before mentioned issue doesn't occur on the latest firefox dev-ed on win11. Personally haven't experienced this issue on any browser in linux yet.

> Shouldn't matter all that much. Could you try the firefox developer edition to see if that one does work?

> Hey man, it seems to be a running issue that the dev tools sometimes break on older browser revisions. Experienced this with multiple releases over the past 2 years...

> Also having this problem on 118.0.2 - did you ever find a fix? > > > > !!window.React is false for me also Have you tried reinstalling the extension?

> > Have you tried reinstalling the extension? > > > > Yes, no change. > > > > Edit: it works on the react test site, just not on...

not going to lie, I think you might enjoy Solid.js Signals more than React.js useState behaviors.

I do have to agree, that signals are kinda a need2implement for react. I mean, even angular has them. (not that I like angular, but usually they are the out-of-date...

Hey man, were you able to fix the issue at hand? @0ui0

Also something completely besides the point. Is there any specific reason for client-side rendering your fairly complex looking data intensive platform that you're building right now? Reason for asking is...