Kris Baumgarter

@CodyJasonBennett I'm stuck again getting the test to run. Some kind of source map issue.

I think a better solution is to have `scene` always point to the root scene, which I think is expected behavior, and then add another prop to the store called...

- `extensions` removed from `useLoader`. - Testing now works. Requires Node 18 or higher since it is using Node's browser-compliant fetch API.

@CodyJasonBennett How can I check if this PR fixes the issue trying to be solved by https://github.com/pmndrs/react-three-fiber/pull/3243 ?

> At the moment r3f drives react spring when used In the context of three because there are instances where you might run frameloop = demand, and the springs would...

> Maybe due to #3228 instead. I'm thinking we can merge this PR and put the issue aside until react-spring gets an update.

Yes, I think ideally there would be a new section on the right panel when selecting an Object3D that lets you see, edit and add components, list ids and maybe...

I think the above, and the already built in array format, are the only plausible defaults because they are built into R3F. Otherwise, I think you would need UI hints...

I suppose some kind of data format in a comment. ```jsx // @triplex-gizmo-position: { x: posX, y: posY } const Enemy = ({ posX, posY }) => ( // ......

All I would add to this is being able to drop them into specific folders inside the asset panel would be key for complex workflows.