You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to use ecctrl within a next.js project I get a bunch of errors from within node_modules. They look like this:
Type error: Type 'CylinderGeometry' is missing the following properties from type'BufferGeometry': drawcalls, offsets, addIndex, addDrawCall, and 5 more.
129 |<Suspense fallback="null">
130 |<animated.group position-x={springs.basePositionX} position-y={springs.basePositionY}>> 131 |<mesh geometry={joystickBaseGeo} material={joystickBaseMaterial} rotation={[-Math.PI / 2, 0, 0]} {...props.joystickBaseProps} />| ^
132 |</animated.group>
133 |<animated.group rotation-x={springs.topRotationX} rotation-y={springs.topRotationY}>
134 |<mesh geometry={joystickStickGeo} material={joystickStickMaterial} rotation={[-Math.PI / 2, 0, 0]} position={[0, 0, 1.5]} {...props.joystickStickProps} />
Now the thing that makes me curious is that these happen even though I have skipLibCheck set to true within my tsconfig... Still I get errors from node_modules? My tsconfig for reference:
However, after some digging, I saw that the file those errors are from is not a .d.ts file => it's a .tsx file... and hence not covered by skipLibCheck.
Looking at the ecctrl/dist/Ecctrl.d.ts I think I might have found the culprit for this:
not sure where/how these are generated, but it importing from ../src makes type definitions break because it doesn't use the type definitions and instead the "real" .tsx file. Which leads to the inclusion of it into typechecking + the resulting errors. (most likely because of some version/type mismatch between ecctrl three types vs. locally installed three.js version?)
not sure if changing this will have any other effects, but I think it should just fix the /dist/ because it should then know to use the .d.ts file correctly then.
When trying to use ecctrl within a next.js project I get a bunch of errors from within node_modules. They look like this:
Now the thing that makes me curious is that these happen even though I have skipLibCheck set to true within my tsconfig... Still I get errors from node_modules? My tsconfig for reference:
However, after some digging, I saw that the file those errors are from is not a .d.ts file => it's a .tsx file... and hence not covered by skipLibCheck.
Looking at the ecctrl/dist/Ecctrl.d.ts I think I might have found the culprit for this:
specifically this line:
should be
not sure where/how these are generated, but it importing from ../src makes type definitions break because it doesn't use the type definitions and instead the "real" .tsx file. Which leads to the inclusion of it into typechecking + the resulting errors. (most likely because of some version/type mismatch between ecctrl three types vs. locally installed three.js version?)
my package.json versions:
Related to:
#12
#96
#82
#25
The text was updated successfully, but these errors were encountered: