[v9] fix: Euler types and ReactProps

[krispya]

This does three things to fix types.

1. Adds an export to ReactProps to fix error TS4023: Exported variable {ComponentName} has or is using name 'ReactProps' from external module "C:/dev/nt--drei/node_modules/@react-three/fiber/dist/declarations/src/three-types" but cannot be named.
   Is this a bug with lerna multi package project with TS4053 error? microsoft/TypeScript#40718
   XXX has or is using name 'Foo' from external module "../bar" but cannot be named microsoft/TypeScript#9944

2. Makes MathRepresenation a union with THREE.Euler since it's optional order string parameter throws a wrench in any algorithmic detection as far as I can see.

3. Adds a MathType Euler export so ReactThreeFiber.Euler works.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 56a11a9:

Sandbox	Source
example	Configuration

[CodyJasonBennett]

Would it be error prone to loosen MathRepresentation to { set(...args: any[]): any } ? I can only think of TypedArrays.

[CodyJasonBennett]

BTW how were you getting error TS4023: Exported variable {ComponentName} has or is using name 'ReactProps' from external module "C:/dev/nt--drei/node_modules/@react-three/fiber/dist/declarations/src/three-types" but cannot be named.? Is this with PNPM and symlinks?

[krispya]

It is with the Drei repo in the base src folder using yarn and no symlinks (afaik). There must be a better solution than this, but this worked. :)

[krispya]

Would it be error prone to loosen MathRepresentation to { set(...args: any[]): any } ? I can only think of TypedArrays.

Wouldn't this mean any instance with a set method passes the math representation test now? There are a few floating around three, such as the Raycaster.

[CodyJasonBennett]

I'm happy to merge this. I do suspect a similar issue with #2668 (comment).

[krispya]

I think so too. Okay, let's merge and make adjustments going forward. I'll see if we can rollback exporting ReactProps once all the type systems are working as we expect.