Commit Graph
12 Commits
Author SHA1 Message Date
Neko Ayaka 3e741d57ec chore(deps): bump dependencies 2025-11-16 02:21:38 +08:00
Neko Ayaka 5b9bf180e9 Revert "chore(deps): bump dependencies"
This reverts commit 38401084e1.
2025-11-16 01:28:29 +08:00
Neko Ayaka 38401084e1 chore(deps): bump dependencies 2025-11-15 23:45:01 +08:00
Neko Ayaka a7a1302b99 chore(deps): bump dependencies 2025-11-01 16:03:45 +08:00
Neko Ayaka 0b85ab78fc chore(deps): bump dependencies 2025-10-12 00:36:21 +08:00
Neko Ayaka 0de306f668 chore(deps): bump dependencies 2025-10-09 02:35:44 +08:00
Neko Ayaka 75321a4cd9 chore(deps): bump dependencies 2025-10-03 16:54:50 +08:00
Neko Ayaka 372125fb89 chore(deps): bump dependencies
Notice: after bumping up to three 0.180.0 with @types/three 0.180.0,
  Argument of type 'Group<Object3DEventMap>' is not assignable to parameter of type 'Object3D<Object3DEventMap>'.
    Type 'Group<Object3DEventMap>' is missing the following properties from type 'Object3D<Object3DEventMap>': setPointerCapture, releasePointerCapture, hasPointerCapture

Currently, AFAIK, clearly, three, and @types/three doesn't have the setPointerCapture, releasePointerCapture, hasPointerCapture method / getters
The only place I found on GitHub, points out that https://github.com/pmndrs/xr/blob/456aa380206e93888cd3a5741a1534e672ae3106/packages/pointer-events/src/pointer.ts#L69-L100 declares

```js
declare module 'three' {
  interface Object3D {
    setPointerCapture(pointerId: number): void
    releasePointerCapture(pointerId: number): void
    hasPointerCapture(pointerId: number): boolean

    intersectChildren?: boolean
    interactableDescendants?: Array<Object3D>
    /**
     * @deprecated
     */
    ancestorsHaveListeners?: boolean
    ancestorsHavePointerListeners?: boolean
    ancestorsHaveWheelListeners?: boolean
  }
}
```

And in @tresjs/core v5, it uses the @pmndrs/pointer-events internally.
Somehow the Object3D from @types/three and the one augmented by @pmndrs/pointer-events are not compatible.

`new Object3D() as unknown as Object3D` works as workaround here but there should be no need to do such a thing since these two Object3D should be the same.
With no updates from `typescript`, I assume there is no breaking change or regression from `typescript` side.
2025-09-26 17:07:07 +08:00
Neko Ayaka ab10782c65 chore(deps): bump dependencies 2025-09-03 13:25:12 +08:00
Neko Ayaka dc6dff5a6d chore(deps): bump dependencies 2025-08-29 01:38:04 +08:00
Neko Ayaka a095ee62f1 chore(deps): bump dependencies 2025-08-02 01:06:54 +08:00
Neko Ayaka 7f178b130f feat(component-calling): or component use, init 2025-07-29 02:37:29 +08:00