Import OrbitControls seems to pull in all of three-stdlib

[stephent]

For example, per VS Code:

When I build (vite project using rollup), all of three-stdlib is included in the build output.

Are there any workarounds for this, or known issues with tree-shaking? Thanks!

Versions:

    "@react-three/drei": "9.84.2",
    "@react-three/fiber": "8.14.2",
    "three": "0.156.0"

[EvenTopland]

Hi, I'm having the same issue. Did you find a solution?

[stephent]

I didn't, unfortunately. I haven't dug into it too far, but I recall reading various threads and posts on the three.js forum that suggest the issue may lie there. I get the impression there's an assumption that any web app using three.js is likely to be "heavy" anyway, and that tree shaking is not a high priority.

[EvenTopland]

That’s unfortunate, package size really makes a difference.
I made an issue here after encountering the same problem, and it seems like they solved the issue once in three-stdlib, but the issue has since come back