We used React Three Fiber at my job 2-3 years ago (when it was "early") and it was already amazing then, we could do really cool stuff easily. We wrote our own wrappers to easily do <Cube /> and similar things and published it as OSS[1], but TBH documentation was scarce since it was an internal project and there were virtually no resources dedicated to publish it, just a couple of devs pushing for it. We even published one of the first bridges[2]. We didn't want to totally opt out of the React render loop so we had to do a lot of hacks and optimizations, but it was a great experience overall.

Nowadays React Three Fiber is very mature and you have the "drei" collection[3], which have all the things I mentioned and a lot more. Though now looking at the source and timing (we published a blog [4] with our solution and their commit few weeks later with almost the same code[5]) it seems they might've copied our solution as part of their package, would've loved a heads up or ack but well happy to make open source better.

[1] https://www.npmjs.com/package/@standard/view

[2] https://github.com/facebook/react/issues/13332#issuecomment-...

[3] https://github.com/pmndrs/drei

[4] https://standard.ai/blog/introducing-standard-view-and-react...

[5] https://github.com/pmndrs/drei/pull/137/files

Polygonjs [1] (disclaimer, I develop it) is for vanilla js, but also has components for vuejs [2], react [3] and react-three-fiber [4]. The goals are to provide a higher level api than threejs, and also to not be restricted to a single framework.

[1] https://github.com/polygonjs/polygonjs

[2] https://polygonjs.com/docs/integrations/vue

[3] https://polygonjs.com/docs/integrations/react

[4] https://polygonjs.com/docs/integrations/react_three_fiber

Yeah these declarative wrappers on top of threejs really help it become more approachable, especially since the skills you've learned with React, Vue, or Svelte translate so directly.