[BUG] Typescript error when using useTransform to combine 2 useTransforms

2. Describe the bug I have 2 useTransforms (x, y) which I want to combine into a string to use as a CSS transform (not sure of what other way to do this — top/left isn’t performant)

  const progress = useSpring(0, {spring});
  const x = useTransform(progress, [0, 1], [0, 100]);
  const y = useTransform(progress, [0, 1], [0, 100]);
  const t = useTransform([x, y], ([x:, y]) => `translate(${x}px, ${y}px)`);

But when I pass them into a 3rd useTransform to combine, typescript complains

TypeScript error in /Users/tarng/Code/playspace/src/av/Stream.tsx(21,26):
No overload matches this call.
  Overload 1 of 3, '(input: MotionValue<unknown>, transformer: SingleTransformer<unknown, unknown>): MotionValue<unknown>', gave the following error.
    Argument of type 'MotionValue<number>[]' is not assignable to parameter of type 'MotionValue<unknown>'.
      Type 'MotionValue<number>[]' is missing the following properties from type 'MotionValue<unknown>': current, prev, timeDelta, lastUpdated, and 19 more.  TS2769

    19 |   const x = useTransform(progress, [0, 1], [0, 100]);
    20 |   const y = useTransform(progress, [0, 1], [0, 100]);
  > 21 |   const t = useTransform([x, y], ([x, y]) => `translate(${x}px, ${y}px)`);
       |                          ^

if i try this on codepen without strict typescript, it throws this error:

3. IMPORTANT: Provide a CodeSandbox reproduction of the bug https://codesandbox.io/s/framer-motion-2-animatesharedlayout-animate-between-different-components-forked-qmgro?file=/src/App.js

4. Steps to reproduce

Steps to reproduce the behavior: Load the prototype, see typescript or type error

5. Expected behavior

It should run

6. Video or screenshots N/A 7. Environment details Chrome, macos

[tarngerine]

i cry

const x = useTransform([progress, mousePos.x] as MotionValue[], (([progress, start]: number[]) => lerp(start, targetX, progress)));
  const y = useTransform([progress, mousePos.y] as MotionValue[], (([progress, start]: number[]) => lerp(start, targetY, progress)));

[huntercaron]

Ive also run into this, not sure how to fix though. Currently I’ve worked around it with a as any with the properties