Prevent PlaneBufferGeometry rename warning

[wmcmurray]

My suggestion to fix #192 (comment)
(unwanted warning in console : THREE.PlaneBufferGeometry has been renamed to THREE.PlaneGeometry.)

I only tested it with r145, but according to your package.json, troika-three-text supports three.js from r103, so I used this CDN link as a reference to help determine what checks to perform.

Feel free to use this approach or not 🙂

Thanks !

[Console-buche]

Well done !
Oh man I was about to publish my own PR for this as I stumbled on the issue myself, then just saw yours.
I like the compat function, nice touch. 👍

Btw : there's a varity of other files that reference PlaneBufferGeometry. I think we could safely extend your proposal to them.

[CodyJasonBennett]

Following this up with #225. Three deprecation policy means that PlaneBufferGeometry will be removed in r154, or 10 releases after deprecation, so there's not an effective way to shim compatibility here.

[wmcmurray]

Nice catch @CodyJasonBennett !
import * as THREE from 'three' would make it possible (but it would be terrrrrible for three-shaking).
I hope Troika is willing to bump the min Threejs revision ! 🤞🏼

[CodyJasonBennett]

Attempting to import a non-existent module through named imports or namespaces will break bundlers (deprecated is effectively removed since three intends to delete in 10 releases). You'd need a dynamic expression that cannot be statically analyzed that is both safe at run-time (despite tree shaking) and not effectful. We employ a similar workaround in @react-three/fiber for progressive support of THREE.ColorManagement, but can't do the same here despite singleton callbacks.

[lojjic]

Thanks @wmcmurray for this, and apologies for the silence on my part. I do think bumping the minimum three version is appropriate at this point, so I'm going to close this PR in favor of #225.