cc @RaananW to follow up
That’s not a bug that needs to be fixed, this is currently the way we have implemented tree shaking and functionality separation in Babylon.
ray.js adds a few new functions to the Scene.prototype object, which in turn changes the function you mentioned. You can read about it here - Babylon.js ES6 support with Tree Shaking | Babylon.js Documentation
This will eventually be modified, but for now - this is the way we deal with tree shaking and you need to make sure you include the classes required for your implementation