Cody Bennett

R3F only raycasts against interactable objects that have handlers registered, so I'm not sure much more can be done there as far as optimizing events' filtering. Three's also intelligent enough...

We're only as fast as threejs here with actual raycasting overhead, but a faster solution could use something like [three-mesh-bvh](https://github.com/gkjohnson/three-mesh-bvh).

Currently, we can't support this due to the performance ramifications of three's built-in raycaster. I'd consider this as a feature request if we do use https://github.com/gkjohnson/three-mesh-bvh to partition the scene...

I implemented this in #2148 but ended up reverting since the migration for point lights was rather non-trivial. Are we able to give this the same treatment as color management?...

> It could be argued that the devDependency should not matter in most cases, but it broke the cdn development distribution of @react-three/fiber at esm.sh and there is problably no...

This looks to be resolved upstream at https://github.com/ije/esm.sh/issues/296, but do update if this is not the case.

Looking into it. Strange that this will pass locally.

I think this will have to point this to v8 so we have a bit more freedom -- v7 is frozen rn except for critical fixes. From what I understand,...

FWIW, events are completely modular, so you can plug in your own events system into v7 or v8 instead of forking the whole thing. ```jsx render(, canvas, { events: myEvents...

As to answer your comment above, we don't want users to install an internal dependency, so this should be bundled into the final build as a dependency.