\r\n\r\n \u003Cdiv class=\"wrapper\">\r\n \u003CHelloWorld msg=\"You did it!\" />\r\n\r\n \u003Cnav>\r\n \u003CRouterLink to=\"/\">Home\u003C/RouterLink>\r\n \u003CRouterLink to=\"/about\">About\u003C/RouterLink>\r\n \u003C/nav>\r\n \u003C/div>\r\n \u003C/header>\r\n\r\n \u003CRouterView />\r\n\u003C/template>\r\n\r\n\u003Cstyle scoped>\r\n\r\n\u003C/style>\r\n```\r\n\r\nAboutView\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"about\">\r\n \u003Ch1>This is an about page\u003C/h1>\r\n \u003Cdiv class=\"canvas\">\r\n \u003CTresCanvas>\r\n \u003C!-- Your scene here -->\r\n \u003C/TresCanvas>\r\n \u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nimport { TresCanvas } from '@tresjs/core'\r\n\u003C/script>\r\n\u003Cstyle>\r\n@media (min-width: 1024px) {\r\n .about {\r\n min-height: 100vh;\r\n display: flex;\r\n align-items: center;\r\n }\r\n}\r\n.canvas {\r\n width: 100px;\r\n height: 100px;\r\n}\r\n\u003C/style>\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/tresjs-minimal-reproduction\r\n\r\n### Steps to reproduce\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)\r\n CPU: (8) x64 13th Gen Intel(R) Core(TM) i7-1355U\r\n Memory: 1.70 GB / 7.76 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 20.18.0 - ~/.nvm/versions/node/v20.18.0/bin/node\r\n npm: 11.0.0 - ~/.nvm/versions/node/v20.18.0/bin/npm\r\n npmPackages:\r\n @tresjs/cientos: ^4.0.3 => 4.0.3 \r\n @tresjs/core: ^4.3.2 => 4.3.2 \r\n vite: ~6.0.6 => 6.0.6\r\n```\r\n\r\n\r\n### Used Package Manager\r\n\r\nnpm\r\n\r\n### Code of Conduct\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\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.\r\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[2867],{"name":2868,"color":2869},"bug","d73a4a",905,"Tresjs","tres","open","I get an error when using TresCanvas. Like this .. ( onUnmounted is called when there is no active component instance to be associated with. Lifecycle injection APIs can... )","2025-02-08T10:41:31Z","https://github.com/Tresjs/tres/issues/905",0.7239598,{"description":2879,"labels":2880,"number":2881,"owner":2871,"repository":2872,"state":2873,"title":2882,"updated_at":2883,"url":2884,"score":2885},"### Description\r\n\r\nHey there,\r\nTres looks amazing. Great work!\r\n\r\nI'd love to switch to Tres, but my application uses multiple canvas elements, each rendering a different camera perspectives to the same scene. Of what I read in the docs & source code, TresCanvas creates its own scene and doesn't share it with other TresCanvas instances. I'd love to see TresCanvas taking scene as an optional prop, but I can also imagine that there might be a lot of side effects coming with such a change.\r\n\r\nWhat do you think of it? Edge case that's hard to implement or easy and viable for the ecosystem?\r\n\r\nHave a great day!\r\nMarc\r\n\r\n\r\n### Suggested solution\r\n\r\n`/src/components/TresCanvas.vue`\r\n```ts\r\nconst props = withDefaults(defineProps\u003CTresCanvasProps>(), {\r\n ...,\r\n scene: new Scene() // TresScene | Scene\r\n})\r\n```\r\nI already know, I'm missing out on component lifecycle handling. I just wanted to point in the direction this is going.\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\nI think this is somehow the reverse request to [Portal](https://github.com/Tresjs/tres/issues/789)\r\n\r\n### Validations\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\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.",[],842,"Decouple scene from canvas","2024-10-17T14:16:20Z","https://github.com/Tresjs/tres/issues/842",0.72983676,{"description":2887,"labels":2888,"number":2895,"owner":2871,"repository":2872,"state":2873,"title":2896,"updated_at":2897,"url":2898,"score":2899},"### Description\r\n\r\nAs a developer using TresJS, I want to have a `\u003CPortal>` component that can contain a separate `Scene` and `context`.\r\n\r\n### Suggested solution\r\n\r\nProvide a `\u003CPortal>` component similar to R3F.\r\n\r\n### Requirements\r\n\r\n- [ ] Add override-able pointer to `TresContext` (Also add as prop to TresCanvas: see #581 ); use vanilla `THREE.Vector2`, accept `Vector2` and `UsePointerOptions` as TresCanvas prop\r\n- [ ] Make these fields on `TresContext` swappable and (in some case injectable by the user): scene, camera, cameras, controls, raycaster, eventManager, sizes\r\n\r\n### Validations\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\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.",[2889,2892],{"name":2890,"color":2891},"p3-significant","2C78E3",{"name":2893,"color":2894},"v5","EFC959",789,"Portal","2025-02-06T09:59:01Z","https://github.com/Tresjs/tres/issues/789",0.7308941,{"description":2901,"labels":2902,"number":2913,"owner":2871,"repository":2872,"state":2873,"title":2914,"updated_at":2915,"url":2916,"score":2917},"### Description\n\nHow to use vue-cli\n\n### Suggested solution\n\nHow to use vue-cli\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.",[2903,2904,2907,2910],{"name":2868,"color":2869},{"name":2905,"color":2906},"help wanted","008672",{"name":2908,"color":2909},"PR welcome","2D76B0",{"name":2911,"color":2912},"p2-edge-case","ABCC40",754,"How to use vue-cli","2024-08-21T09:51:50Z","https://github.com/Tresjs/tres/issues/754",0.7310789,{"description":2919,"labels":2920,"number":2921,"owner":2871,"repository":2922,"state":2873,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### Describe the bug\n\nI am using `\u003CHtml>` to wrap elements containing template refs, but these refs are not correctly initialized. As a result, the references to the slotted elements are inaccessible within the component's lifecycle.\n\nPerhaps related to issues: [464](https://github.com/Tresjs/tres/issues/464) — [312](https://github.com/Tresjs/tres/issues/312)\n\n### Reproduction\n\nhttps://play.tresjs.org/#eNqdVW1v2zYQ/iucgiEuJkuykxSb5xSZ3XbtsKxBG2Afqn5gpIvFhCIJkvLLAv/3HSnLlpLWdWoLhnkvzz13vDs9BNcazB9KRfMKglEwNplmyhIDtlKEUzE7TwNr0uBVKlippLbkgWi4DYkUl7ISFvKQLKjNCrImt1qW5BiBjn9vWbsAUyrm1GxNLizK7kycSd21/aBvmJ1KYbXkJiTvbMmfOjEQVhrnl4pMCmOJoprONFUf4ZacO3o9UXH+whlsafZ6L8j5K/KQCkKcl+QQcTnrHZe1/jhsw0RzyitAhLVH8Rn2WvqQfAvOm+4BG8d1ibGgeLBQKk4t4ImQcatUCyZyuegb9h+QjAPV/UxyqfE2jn4dvp5Mz/yVEPx4ryvQRkFm2RymtARNyUhJwyyTAl0+/xYS93xJAxI3bp1a78QO7RJM0QXoD0OCT+IQRlpa2iiSkFxSW0RX72vtBqZJRgr4E2QJVq/IiOqZcT6DkAyis5CctPm0Ql9LvDUsimaUY3Efpb2jGjcO+7kjRfe4YBk1tm8KiqXthp3I5Vd4OpLNz7O4nr513x/gijV2pX5ayU+qAL2r5cFM3k4mycmkwx19/GBlOEegW2JUKDc96NfqXmTyDjiX5F+pef7TOFZtpNhB7U3yNdOuMaWg/G82K+yTy8F8T31fMeQjULVCxSAadu9rk0Adox4SFIzj1gTh0dgVd38LZBWm4kbmq3pGS7xUJkYkwbVBcDjznIlZcyzAERuRQZL87AULlttie16n4ogqVQN9x5aQG5rdzzQulbwe2RE5ShIXB2Fw+D3BIAzqndcvqYrujBS4ez18ulHgyh3VAZ2svTCdIg0Ka5UZxXGWC/TPgbO5jgTYWKgybptfnEbDaBjnzNjYidE6DbA0j4Drpfoc7NoD4ZMo6QtY2miwi7LRdoPZBdB7RcUhKWxtfYAGuRFGJXM+bexCw0G4zu4CEV8i7fgXMGW7GvjuqgwcXOaW+cUgic4QEdc2LKOyW+SNHTayhvwZwLXDPmg07OdQsgNAG1OX/Gn0Mubspg3pELFD19ia1uAb7ZbNHjVmJkvFOOgPyg1vt0EpLojFX15mdQVbflkB2f1X5HdmWVO+wmYBPcdy764SRxVsrX7z6R/srJaylHnFN5fzDeVHwLdx5TjWZhMcRaTdsvNs3/s5wy1wbd4s/eLZJNUhalcKvPRzs/S2vVYLvvjCeXt/HdM9VdpldhKdbAu+/h+NgxeG\n\n### Steps to reproduce\n\n1. Use the `\u003CHtml>` component to wrap elements containing template refs.\n2. Observe that these refs are not initialized (console.log inside onMounted shows them as undefined).\n3. Any logic relying on these refs does not work as expected.\n\n```vue\n\u003Ctemplate>\n \u003CHtml>\n \u003Cdiv ref=\"container\">Some Content\u003C/div>\n \u003C/Html>\n\u003C/template>\n\n\u003Cscript setup>\nimport { Html } from '@tresjs/cientos'\nimport { ref, onMounted, watch } from 'vue';\n\nconst container = ref(null);\n\nonMounted(() => {\n console.log(container.value); // Expected: DOM Element | Actual: null\n});\n\nwatch(container, () => {\n console.log('watch', container.value); // Expected: DOM Element | Actual: The log never appears\n})\n\u003C/script>\n```\n\n### Summary of Solutions\n\nParent refs don't get assigned when using `createVNode()` and `render()` because the content ends up outside the parent's render tree. Here's a quick breakdown:\n\n#### What Doesn't Work\n- **Direct `\u003CTeleport>`** \n The custom TresJS renderer can't find the target in the standard DOM.\n\n- **Manual `createVNode()` + `render()`** \n This creates a new root outside the parent's render tree, so refs declared in the template aren't assigned.\n\n#### What Might Work ?\n- **Global Store (Pinia/Vuex)** \n You could set up a tunnel to share content via a global store, but that adds an external dependency we’d rather avoid.\n\n- **Tunnel via Provide/Inject (In/Out)** \n Use provide/inject to share a reactive state (like an array of VNodes) between an \"In\" component (capturing the content) and an \"Out\" component (rendering it in the standard DOM). This should preserve reactivity and proper ref assignment without extra dependencies. This [message](https://github.com/Tresjs/tres/issues/312#issuecomment-2302950778) in [issue 312](https://github.com/Tresjs/tres/issues/312) talked about this method. \n\n\n### System Info\n\n```shell\nSystem:\n OS: macOS 15.1.1\n CPU: (14) arm64 Apple M4 Pro\n Memory: 116.89 MB / 24.00 GB\n Shell: 5.9 - /bin/zsh\n Binaries:\n Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node\n npm: 11.0.0 - ~/.nvm/versions/node/v22.11.0/bin/npm\n pnpm: 9.14.4 - ~/.nvm/versions/node/v22.11.0/bin/pnpm\n Browsers:\n Chrome: 133.0.6943.55\n Safari: 18.1.1\n```\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/cientos/blob/main/CODE_OF_CONDUCT.md)\n- [x] Read the [Contributing Guidelines](https://github.com/Tresjs/cientos/blob/main/CONTRIBUTING.md).\n- [x] Read the [docs](https://cientos.tresjs.org/guide).\n- [x] Check that there isn't [already an issue](https://github.com/Tresjs/cientos/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.",[],596,"cientos","Template refs inside `\u003CHtml>` component are not working","2025-02-17T20:39:49Z","https://github.com/Tresjs/cientos/issues/596",0.7319218,{"description":2928,"labels":2929,"number":2936,"owner":2871,"repository":2872,"state":2937,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Description\r\n\r\nIdea from @userquin, the idea would be to use [Vue named scoped slots ](https://vuejs.org/guide/components/slots.html#named-scoped-slots) to be able to get the canvas context on the parent like this:\r\n\r\n```html\r\n\u003CTresCanvas shadows alpha v-slot=\"state\">\r\n \u003CTresPerspectiveCamera :position=\"[5, 5, 5]\" />\r\n \u003CTresOrbitControls\r\n v-if=\"state?.renderer\"\r\n :args=\"[state?.camera, state?.renderer?.domElement]\"\r\n />\r\n\u003C/TresCanvas>\r\n```\r\n\r\nOr even deconstruct it\r\n\r\n```html\r\n\u003CTresCanvas shadows alpha v-slot=\"{ camera, renderer }\">\r\n \u003CTresPerspectiveCamera :position=\"[5, 5, 5]\" />\r\n \u003CTresOrbitControls\r\n v-if=\"renderer\"\r\n :args=\"[camera, renderer.domElement]\"\r\n />\r\n\u003C/TresCanvas>\r\n```\r\n\r\n### Suggested solution\r\n\r\nAdd this to `TresCanvas.vue`\r\n\r\n```html\r\n\u003Ccanvas\r\n ref=\"canvas\"\r\n :data-scene=\"scene.uuid\"\r\n :class=\"$attrs.class\"\r\n :data-tres=\"`tresjs ${pkg.version}`\"\r\n :style=\"{\r\n display: 'block',\r\n width: '100%',\r\n height: '100%',\r\n position: windowSize ? 'fixed' : 'relative',\r\n top: 0,\r\n left: 0,\r\n pointerEvents: 'auto',\r\n touchAction: 'none',\r\n ...$attrs.style as Object,\r\n }\"\r\n >\r\n \u003Cslot v-bind=\"context\" />\r\n\u003C/canvas>\r\n```\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\nrelated #565\r\n\r\n### Validations\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\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.",[2930,2933],{"name":2931,"color":2932},"wontfix","ffffff",{"name":2934,"color":2935},"has-workaround","AEA9C4",572,"closed","Use default slot props to get Canvas context","2024-06-01T07:39:43Z","https://github.com/Tresjs/tres/issues/572",0.6854411,{"description":2943,"labels":2944,"number":2951,"owner":2871,"repository":2872,"state":2937,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Describe the bug\n\nIt seems like Tres.js is no longer working in Firefox. Even on your official documentation all examles render just a black canvas.\r\nI would really like to use Tres.js in projects of my company, but I am unable to do this if Firefox is not supported or working :(\n\n### Reproduction\n\nhttps://tresjs.org/guide/\n\n### Steps to reproduce\n\nThe first and all other examples of this page.\n\n### System Info\n\n```shell\nWindows 10\r\nFirerfiox version 114.0.1 (64-Bit)\n```\n\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.",[2945,2948],{"name":2946,"color":2947},"question","d876e3",{"name":2949,"color":2950},"waiting for author","B145BC",310,"Black Canvas in Firefox","2023-06-20T07:13:04Z","https://github.com/Tresjs/tres/issues/310",0.69177026,{"description":2957,"labels":2958,"number":2959,"owner":2871,"repository":2872,"state":2937,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Describe the bug\n\nAs shown in the StackBlitz URL example, `onPointerLeave` was activating in version 3.9 and earlier. However, in version 4.0 and later, it is difficult to activate. How can I use `onPointerLeave`?\r\n\r\n```html\r\n \u003CTresMesh\r\n @pointer-enter=\"onPointerEnter\"\r\n @pointer-leave=\"onPointerLeave\"\r\n name=\"box\"\r\n >\r\n \u003CTresBoxGeometry />\r\n \u003CTresMeshBasicMaterial color=\"#006060\" />\r\n \u003C/TresMesh>\r\n```\r\nThis way of using it is not a good practice.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/tresjs-minimal-reproduction-kentgx?file=src%2Fcomponents%2FTheExperience.vue,src%2FApp.vue\n\n### Steps to reproduce\n\n_No response_\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.",[],713,"v4.0.1 The `onPointerLeave` function is not activating.","2024-06-06T14:33:34Z","https://github.com/Tresjs/tres/issues/713",0.6952563,{"description":2965,"labels":2966,"number":2973,"owner":2871,"repository":2872,"state":2937,"title":2974,"updated_at":2975,"url":2976,"score":2977},"Since vue compiler doesn't recognize the TresJS as native, users need to add this code to the `vite.config.ts` \n\n isCustomElement: tag => tag.startsWith('Tres') && tag !== 'TresCanvas',",[2967,2970],{"name":2968,"color":2969},"docs","0075ca",{"name":2971,"color":2972},"v2","FEE22E",169,"Add customElement vue compiler code to docs","2023-03-30T06:19:00Z","https://github.com/Tresjs/tres/issues/169",0.70184696,{"description":2979,"labels":2980,"number":2981,"owner":2871,"repository":2872,"state":2937,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Description\r\n\r\nBased on https://github.com/orgs/Tresjs/discussions/321\r\n\r\nAs a plugin author, I will like to have a reactive state with the following characteristics:\r\n\r\n- Performant, (use of `shallowRef` where needed)\r\n- read-only\r\n- Strictly Typed\r\n- Reduce side effects on watchers\r\n- Needs to work on cientos and the rest of ecosystem via `provide/inject` \r\n\r\n### Suggested solution\r\n\r\n| Name | Type | Requirement | Details |\r\n| ---------------------------------- | -------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\r\n| scene | readonly, shallowRef | essential | |\r\n| cameras | readonly, shallowRef | essential | userData.TRES_IS_ACTIVE_CAMERA = true\u003Cbr>const cameras = shallowRef([]) return { cameras: readonly(cameras)} |\r\n| camera | computed, readonly | essential | |\r\n| pushCamera(newCamera: Camera, setActive: boolean) | function | essential | cameras should be watched and removed from the cameras array if they got removed from the scene |\r\n| removeCamera(camera: Camera) | function | essential ||\r\n| setCamera(cameraId string) | function | essential ||\r\n| renderer | readonly, shallowRef | essential | setRenderer(renderer: Renderer)\u003Cbr>maybe only callable once? |\r\n| setRenderer(renderer: Renderer) | function | essential ||\r\n| sizes (height, width, aspectRatio) | readonly | handy | sizes: {\u003Cbr> height: Ref\u003Cnumber>\u003Cbr> width: Ref\u003Cnumber>\u003Cbr> aspectRatio: Computed\u003Cnumber>\u003Cbr>} |\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\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.",[],331,"New and better state context provider","2023-07-29T08:58:56Z","https://github.com/Tresjs/tres/issues/331",0.70948964,["Reactive",2987],{},["Set"],["ShallowReactive",2990],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fvJeS_-FaCC207cWnK1aX2kmGysqGJyeVmYZWHMqWMSc":-1},"/Tresjs/cientos/329"]