and with teleport controls mainly used in VR applications as opposed to AR applications, it would seem most beneficial to create a component called \u003CTeleportVR />\r\n\r\nThis component will allow users to teleport using a single motion controller, defaulting to the right handed controller with the joystick being used to trigger the aiming interface. Most application 3D or VR use the right joystick for movement, and if using teleport controls it makes the most sense to use this as the default trigger under the expectancy developers are more likely to use the other buttons on the controller for purposes differing from movement.",[2920,2923],{"name":2921,"color":2922},"enhancement","a2eeef",{"name":2924,"color":2925},"help wanted","008672","XR","Teleport VR controls component","2024-05-12T17:53:16Z","https://github.com/Tresjs/XR/issues/16",0.8068691,{"description":2932,"labels":2933,"number":2943,"owner":2863,"repository":2864,"state":2944,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### Describe the bug\n\nI am importing useSeek in my project:\r\n```typescript\r\nimport { useSeek } from \"@tresjs/core\";\r\n```\r\n\r\nSince the upgrade to Tres 3.8.0, I get the error `Module \"\"@tresjs/core\"\" has no exported member \"useSeek\". Did you mean to use \"import useSeek from \"@tresjs/core\"\" instead?`\r\n\r\nIndeed, useSeek, useRaycaster and useLoader which are exported in src/composables/index.d.ts don't seem to be present in the package anymore.\n\n### Reproduction\n\nhttps://www.runpkg.com/?@tresjs/core@3.8.0/dist/src/composables/index.d.ts\n\n### Steps to reproduce\n\nUnfortunately I didn't manage to reproduce the issue on Stackblitz, but the link above shows that the 3 files are missing from the directory where it's supposed to be imported from.\n\n### System Info\n\n_No response_\n\n### Used Package Manager\n\npnpm\n\n### Code of Conduct\n\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/tres/issues) that reports the same bug to avoid creating a duplicate.\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[2934,2937,2940],{"name":2935,"color":2936},"bug","d73a4a",{"name":2938,"color":2939},"p2-edge-case","ABCC40",{"name":2941,"color":2942},"regression","167F7A",619,"closed","useSeek, useRaycaster and useLoader are missing from TresJS 3.8.0","2024-04-08T10:24:47Z","https://github.com/Tresjs/tres/issues/619",0.7629266,{"description":2950,"labels":2951,"number":2958,"owner":2863,"repository":2864,"state":2944,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Description\n\nAs a TresJS developer, I would like to have better type support and IntelliSense. The idea would be to replace the current approach of generating the types on the build.\n\n### Suggested solution\n\nCody from Pmndrs gave me a hint on how R3F is tackling the typing. https://github.com/pmndrs/react-three-fiber/blob/v9/packages/fiber/src/three-types.ts\r\n\r\n```ts\r\ntype ThreeExports = typeof THREE\r\ntype ThreeElementsImpl = {\r\n [K in keyof ThreeExports as Uncapitalize\u003CK>]: ThreeExports[K] extends ConstructorRepresentation\r\n ? ThreeElement\u003CThreeExports[K]>\r\n : never\r\n}\r\n```\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/tres/issues) that reports the same bug to avoid creating a duplicate.",[2952,2955],{"name":2953,"color":2954},"dx","1576AD",{"name":2956,"color":2957},"types","5C076E",268,"Refactor typescript support from build to runtime","2023-05-21T09:05:02Z","https://github.com/Tresjs/tres/issues/268",0.7797351,{"description":2964,"labels":2965,"number":2967,"owner":2863,"repository":2864,"state":2944,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Description\n\nAs a developer using TresJS, I would like to change reactively the constructor params via args prop, which is not possible at the moment.\r\n\r\n```ts\r\n\u003Cscript lang=\"ts\" setup>\r\n// renderer.domElement is undefined at the beginning. \r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CTresOrbitControls :args=\"[activeCamera || camera, renderer?.domElement || domElement]\" />\r\n \u003C/template>\r\n ```\n\n### Suggested solution\n\nAdd logic to `nodeOps` to re-instance the THREE object when `args` change\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/tres/issues) that reports the same bug to avoid creating a duplicate.",[2966],{"name":2935,"color":2936},366,"Re-instance THREE instances via args prop reactivity","2023-08-17T13:53:39Z","https://github.com/Tresjs/tres/issues/366",0.7854631,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHseZ5hlV0fxDa__p3iFeJS_RuU57edAZbyn6HITodhg":-1},"/Tresjs/cientos/606"]