Cody Nova

@jwrubel You technically have access to more of the Cannon API with that example hook than you do within `use-cannon`. Because `use-cannon` wraps the physics simulation in a web worker,...

The `ref` in the hook from the example code you posted is a reference to a ThreeJS mesh that will receive values from the Cannon physics body - it's not...

Wouldn't most of the rollup plugins for ESM and CJS also need to be used in the AMD build?

I think jest is probably the way to go, but I wouldn't complain about either option 😄

Try providing a RaycastResult when calling `intersectBody`: ```js body.addEventListener('collide', ({ contact: { bi } }) => { if (!grounded) { const vTo = new CANNON.Vec3(0, -1, 0) const ray =...

The problem I see is that we don't want to call `updateDirection` in any intersection method unless it's truly necessary (it is not insignificant to performance) - and the way...

> This does not work: Your destructuring isn't correct: ```js body.addEventListener("collide", ({ contact: bi }) => { ``` should be ```js body.addEventListener("collide", ({ contact: { bi } }) => {...

After doing more digging I will need to consider this further. Updating the intersect methods API as I suggested above would cause undesirable behavior when initializing the Ray with a...