Nick Matantsev

@iggyZiggy your error message is related to #50 instead (will post more there), I think that Jesse is describing a different issue here.

Hey, this is a good question! I just recently finished a rewrite that decouples a lot of this code from React, so it is conceivable to expose completely a non-React...

Thanks everyone, I can see a lot of interest in this and I think there is a way to expose the necessary internals so that anyone can use them without...

Hey, thanks a lot for looking into this and reporting the specific issues. I will try to fix this in the next few days.

I upgraded to latest React/r3f was able to repro the `sceneRef.current` issue, still figuring out a fix.

Hi Slava and others, I appreciate the long wait - a bit of a crunch at work but I should have some cycles this week to wrap this up.

Thanks for checking in again! Yeah the last month has been really busy at work, I am hoping that time management improves in the coming week. Really appreciating the wait...

Ok, so I did some cleanup work and upgraded to React 18. As is, the `main` branch now works with the latest React *but* I had to take out the...

> The update is not yet published to npm right? I did not push a new version to NPM yet, this is in a temporary state until I fix suspense...

Hi Leonardo, yes please update with results if you find something. I am slowly working through my open source issues backlog currently (had a bit of an overloaded summer!), and...