casswoo
I finally had the chance to look into this.
I tested all our examples with the latest Three.js version (0.184.0), and they all work correctly.
I noticed that the only issue is that the Three.js version in the peer dependencies is pinned, which might cause issues with package managers. However, that's because Three.js uses the 0.y.z versioning scheme, which does not work well with ^. Each Three.js version can potentially introduce breaking changes, so the most I can do is accept a wider version range up to the latest release: >=0.162.0 <0.185.0.
I'll also try to test and update the latest version more frequently.
I was also able to create an R3F web app using spine-threejs, and everything worked correctly. So, I don't see anything specific we should change regarding that, since it's already working. I added the example to our examples, but we won't create a dedicated runtime for it.
If there are specific issues you've identified with R3F, please share a repro with us and point them out.
I released a new version: 4.2.116 👍️