react-three-fiber · Issues· 76 open

[v10 alpha.5] /legacy import and browser build fail on WebGPU-only exports from plain three

`useLocalNodes`: inline creator rebuilds the graph every render, and any uniform registration invalidates every consumer

[v10] Track useLocalNodes resource reads to narrow registry subscriptions

[v10] Add explicit dependency-array semantics to useLocalNodes

React 19.3: useTransition() inside the R3F tree throws "Cannot read properties of undefined (reading 'length')"

Types: the ScopedStore surface (`useLocalNodes`, `uniforms.scope`, `nodes.scope`) — uniforms need a double cast, nodes are `any`

events.connect throws TypeError on null target during DOM-reparenting animations

React safe way to mutate memoized resources

Remove `onUpdate`

Clarify `useRenderPipeline` names

TypeScript: React.ElementType becomes incompatible after importing @react-three/fiber

RFC: named dirty signals for event-driven frame jobs

v10: expose newly loaded textures to later creator hooks in the same render

Add a reuse prop for named material instances

Support effect-only useNodes/useLocalNodes callbacks without synthetic returns