tl;dr: you got a package that may have bundled its own react, or is using another version of react

I believe this happens when a module/package uses a different version of react than what next.js is using... i don't know if react-three (or react-three/drei) itself bundles react but it should be fixed if all react-dependent package uses the same version of react