DefinitelyMaybe

hey sorry types aren't working for you. Could you give us a snippet of your code, did you add the `.from` to your code?

Hmm interesting 🤔 thank you for doing that quick double check with me. The team's looking into it further 👍

@idle-z we've transitioned on the `next` branch to using `type.ts`, has this resolved the type issues for you?

I agree with @boytchev's comments above. Adding a [tutorialkit](https://tutorialkit.dev/guides/about/) tutorial to my demo docs would be a good fit. To note, the current documentation issue #24984 would likely need to...

an option for the `texture` vs `uniformTexture` would be to leave the name as is but reflect the type from the import i.e. `import { texture } from "three/tsl/uniforms"`

+1 for it going into extras

Well I did get it to build on me machine 😅 however this could also be a similar issue to what I experienced in my own deployment earlier - literally...

Will redo from current main instead of trying to work through all the merge conflicts

sorted in `next`, docs link [here](https://next.threlte.xyz/docs/reference/rapier/framerate#fixed-framerate)

Hey, sounds like these errors have been giving you a heck of a time. Some clean up is definitely in order 😅