rt-rapier breaks with StrictMode enabled about react-three-rapier HOT 3 CLOSED

Looking into this, why not eagerly create World here in state?

I also see this in other places, although this is initialized immediately in createWorldApi before passing in context.

from react-three-rapier.

Good call! I'll wrap the Demos in StrictMode from now on.

There is some work to be done on RigidBody lifecycles.
React 18 Strict Mode has some annoying but necessary behaviors in order to catch potential problems, especially in Development Mode where it runs all components twice, invoking effects and state-setters both times.

The safe way to ensure a single eagerly created instance is to use the refGetter pattern like above ☝️ @CodyJasonBennett -- I really dislike it, but what can you do.

It would be nice to create the world in a useState, but then we'd have a non-symmetrical side-effect where we have to destroy it in an unrelated useEffect.

I should be passing the refGetter to the update hooks in the RigidBody instead of the refs. Strict Mode is causing the component to mount multiple times, breaking the rigid body reference in the "newest" world...

Do you have suggestions on cleaner ways of handling this?

from react-three-rapier.

In this case, you would nullify worldRef.current on unmount to unsatisfy the null check, but I wanted to understand why internals were designed that way and if they work around existing problems. Do you need access to these bodies at render? Can we remove render-effects entirely?

from react-three-rapier.