\r\n \u003C/Suspense>\r\n`\r\nAm I using it the wrong way?\n\n### Reproduction\n\nnull\n\n### Steps to reproduce\n\n_No response_\n\n### System Info\n\n_No response_\n\n### Used Package Manager\n\nnpm\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.",[],667,"The click event does not work on GLTFModel","2024-04-30T04:40:39Z","https://github.com/Tresjs/tres/issues/667",0.76420444,{"description":2959,"labels":2960,"number":2961,"owner":2875,"repository":2876,"state":2934,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Describe the bug\n\nCurrent type definitions don't allow for a function to be passed to the `ref` prop of a component, so any time you use a [functional ref](https://vuejs.org/guide/essentials/template-refs.html#function-refs) you'll run into a type error.\r\n\r\nApologies for not including a reproduction or sample but this should be quick to recreate in any dev environment with the reproduction steps.\n\n### Reproduction\n\n/\n\n### Steps to reproduce\n\n1. Install tresjs in any project\r\n2. Add TresCanvas\r\n3. Add new ref, and function to populate ref \r\n`const sphereRefs = ref\u003CObject3D[]>([]);`\r\n`const setSphereRefs = (el: any) => {\r\n if (el && !sphereRefs.value.includes(el)) {\r\n sphereRefs.value.push(el);\r\n }\r\n};`\r\n4. Add TresGroup, TresMesh, etc...\r\n5. Pass a function to the `ref` property `:ref=\"(el) => \"setSphereRef(el)\"`\r\n6. Type error pops up indicating this isn't a valid value for the `ref` prop despite this being a common use for the `ref` prop.\n\n### System Info\n\n_No response_\n\n### Used Package Manager\n\nyarn\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.",[],427,"ref prop missing type for functional ref","2023-10-30T10:34:55Z","https://github.com/Tresjs/tres/issues/427",0.7763686,{"description":2967,"labels":2968,"number":2970,"owner":2875,"repository":2876,"state":2934,"title":2971,"updated_at":2972,"url":2973,"score":2974},"**Describe the bug**\r\nSeems like the state of useTres keep alive between pages, even when the routes are lazy\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to https://serene-mousse-562782.netlify.app/MouseShaderEffect\r\n2. Move the mouse, observe no controls is on the scene\r\n3. Go to home using the navbar (here you can see we have the pam-camera-control)\r\n4. Return to the mouseShaderEffect using the navbar (observe now the state of pam-camera-controls remains)\r\n\r\nThis behavior also happens with orbicControls\r\n\r\n**Expected behavior**\r\nA new route should be a complete new canvas which also means that the old canvas should die entirely and every other effect\r\n\r\n**Additional context**\r\nThis could affect other states/effect throug the library\r\n",[2969],{"name":2897,"color":2898},173,"Problem with state using router navigation","2023-04-05T13:41:50Z","https://github.com/Tresjs/tres/issues/173",0.7777984,{"description":2976,"labels":2977,"number":2980,"owner":2875,"repository":2876,"state":2934,"title":2981,"updated_at":2982,"url":2983,"score":2984},"**Describe the bug**\r\nCould not resolve \"@vueuse/core\" on installation, since it's a peerDependency set as external, the user would need to add it separately\r\n\r\n**Reproduction**\r\n[Stackblitz](https://stackblitz.com/edit/tresjs-basic?file=README.md)\r\n\r\n\r\n**System Info**\r\nOutput of `npx envinfo --system --npmPackages '{vite,@tresjs/*, three, vue}' --binaries --browsers` \r\n\r\n```\r\n System:\r\n OS: Linux 5.0 undefined\r\n CPU: (3) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 0 Bytes / 0 Bytes\r\n Shell: 1.0 - /bin/jsh\r\n Binaries:\r\n Node: 16.14.2 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 7.17.0 - /usr/local/bin/npm\r\n npmPackages:\r\n @tresjs/core: ^1.6.0 => 1.6.0 \r\n vite: ^4.1.0 => 4.1.1 \r\n```\r\n",[2978,2979],{"name":2897,"color":2898},{"name":2866,"color":2867},96,"Could not resolve \"@vueuse/core\" on Installation","2023-02-06T18:17:07Z","https://github.com/Tresjs/tres/issues/96",0.784684,["Reactive",2986],{},["Set"],["ShallowReactive",2989],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHQea9rt3VTLk1wHqLc9XYTedVcCovGiXZYikejV185w":-1},"/Tresjs/tres/995"]