Indicate compatible Three version in r3f doc

[fnick851]

Maybe I'm too new to this but it seems like ThreeJS often introduce breaking changes.

For example recent 0.124 to 0.125, and 0.125 to 0.126 will break a few things for r3f.

I think it would be helpful if r3f indicate somewhere obvious in the doc which Three.js it is currently/fully compatible with.
For example, it can be npm install [email protected] react-three-fiber instead of just plain three.

[joshuaellis]

react-three-fiber is a renderer for three, what do you think it is breaking, we haven't had anything else reported yet.

[fnick851]

Oh, it must be I don't really understand how it works internally then.

For example with r3f 5.3.19, three 0.126, next.js 10.0.5, I have:

./node_modules/three/build/three.module.js
Module not found: Can't resolve '/project/node_modules/next/node_modules/@babel/runtime/helpers/esm/assertThisInitialized' in '/project/node_modules/three/build'

[joshuaellis]

Can you replicate this error in a sandbox so we can look?

[fnick851]

@joshuaellis Thanks. By attempting to replicate the error, I found it is an issue with a library I used called react-three-gui.

[drcmda]

yes, i think drei or three-gui are far more likely to be affected. r3f is relatively resilient. when they moved from webgl to gl2 that was too much even for r3f but everything else should be fine.