TypeScript Error: Movement is not part of state

[do-kevin]

Information:

• Use Gesture version: ^10.2.4
• TypeScript

Bug
I am getting an error complaining about state's movement. I've tried removing my node_modules and upgrading the package, but it still shows up. movement is still part of state on my console.log.

On hover, it says

Property 'movement' does not exist on type 'Omit<SharedGestureState & CommonGestureState & { axis: "x" | "y" | undefined; xy: Vector2; } & { _pointerId?: number | undefined; ... 7 more ...; swipe: Vector2; } & { ...; }, "event"> & { ...; }'.

Screenshots

[dbismut]

can't reproduce https://codesandbox.io/s/issue-501-35zbto?file=/src/App.tsx

[linonetwo]

Simillar issue here.

And when passed to animated.mesh:

ClipboardEventHandler<EventTarget> | undefined; ... 156 more ...; position: Vector3; }' is not assignable to type 'AnimatedProps<Omit<ExtendedColors<Overwrite<Partial<Mesh<BufferGeometry, Material | Material[]>>, NodeProps<Mesh<BufferGeometry, Material | Material[]>, typeof Mesh>>>, NonFunctionKeys<...>> & { ...; } & EventHandlers>'.
  Types of property 'onClick' are incompatible.
    Type 'MouseEventHandler<EventTarget> | undefined' is not assignable to type '((event: ThreeEvent<MouseEvent>) => void) | undefined'.
      Type 'MouseEventHandler<EventTarget>' is not assignable to type '(event: ThreeEvent<MouseEvent>) => void'.
        Types of parameters 'event' and 'event' are incompatible.
          Type 'IntersectionEvent<MouseEvent>' is missing the following properties from type 'MouseEvent<EventTarget, MouseEvent>': altKey, button, buttons, clientX, and 27 more.ts(2322)

[dbismut]

I won't reopen without a sandbox.

[cuppachino]

I was able to recreate the issue by selecting "Use VS Code's Version 4.8.0-dev.20220714" over the workspace version, which in my case was 4.7.4

in the status bar, left of your selected language mode, click the curly braces.

The fix is to your workspace version.

[dbismut]

@cuppachino seems like TS 4.8 does introduce this bug. I'm not sure why tbh.

[dbismut]

Here's a minimal repro on TS Playground.

It seems to be linked to the NonNullable type / making drag and pinch optional in state.
Deactivating strictNullChecks fixes it for TS 4.8.

[dbismut]

Ok after some investigation, this is because of the simplification of the NonNullable mapped type.

// Native NonNullable Utility Type

// definition on 4.7 and lower
type NonNullable<T> = T extends null | undefined ? never : T

// definition from 4.8 
type NonNullable<T> = T & {}

Fix is incoming (at least I hope).

[dbismut]

Should be now fixed in 10.2.19.