RFC: v9 goals

[krispya]

Let's discuss some v9 goals here. These are all tentative right now.

Completed

• Add stage-based lifecycle, deprecate useFrame for useUpdate [v9] feat: implement update lifecycle with useUpdate #2279
• Remove onUpdate prop [v9] refactor!: remove onUpdate prop #2480
• Remove updateStyle from Size [v9] refactor!: remove updateStyle from Size #2489
• act types for testing [v9] fix(types): don't declare unstable_act #2492
• Instance descriptors, refactor JSX types & extend [v9] refactor!: instance descriptors, dynamically map ThreeElements #2465
• prefer named functions, for loops in hot paths [v9] fix: prefer named functions, for loops in hot paths #2540 (backported in v8.8.7)
• upgrade Zustand to v4 [v9] refactor(types)!: upgrade Zustand to v4 #2558
• export all public types [v9] refactor(types): export public types #2559, [v9] refactor: streamline core, harden exports #2583
• respect React.StrictMode across renderers [v9] fix: forward StrictMode #2547
• anonymous extend overload for libraries [v9] experiment: extend factory overload #2785
• Suspense causes attach to be called multiple times #2250

TODO

• New caching model, update useLoader for React.use: [v9] feat(cache): promise based caching with workers #3245
• Primitive with children mounting / unmounting + documentation #3204
• scene from useThree is not always a THREE.Scene within portal #2725
• Breaking changes in React experimental branch #3222
• RFC: workflow canvas prop  #2299

Pending

• New scheduler
• Refactor internal state

[krispya]

I'd also like to discuss making renderer.physicallyCorrectLights = true by default. See: #2127

[CodyJasonBennett]

I don't think we can change defaults for lighting OOTB, problems are detailed in the linked issue. That might be a consideration for #2299 but the issue of decay not respecting physicallyCorrectLights remains. I think this is something to be considered in threejs itself.

[krispya]

I don't think we can change defaults for lighting OOTB, problems are detailed in the linked issue. That might be a consideration for #2299 but the issue of decay not respecting physicallyCorrectLights remains. I think this is something to be considered in threejs itself.

Agreed.

After a conversation with Paul, I'm making sure a pass on the frameloop modes is also on the to-do list. In particular demand needs to be updated so that it skips the render loop but still tracks delta so starting and stopping render doesn't destroy delta based animations.

[saitonakamura]

What are your thoughts on updating to zustand v4?

[krispya]

I'm in favor, the typing is hugely improved and so is compatibility with context. But it isn't a trivial update. Is it something you would be interested in spearheading? I can contribute.

[saitonakamura]

Yeah, I think so. When upgrading to r3f v8 I erroneously update zustand to v4. I had to revert back of course but not until I had some fair share of migration experience (we use it too)

[krispya]

That would be great. If you start a branch, I can do review and assist.

[CodyJasonBennett]

Just did this with react-ogl in pmndrs/react-ogl#75, giving it a try here in #2558.

[krispya]

Thanks so much for all your hard work Cody. I wanted to add here some type exports for the different r3f props which were previously exported as Vector3, Color, etc.

[aspheris]

Hello! Whats the status of V9? I'm looking to use the lifecycle stages in useUpdate but it looks like its not officially ready yet.

[krispya]

Hello! Whats the status of V9? I'm looking to use the lifecycle stages in useUpdate but it looks like its not officially ready yet.

Hey! So we have been working on projects in parallel to this one and trying out some of the v9 updates internally as we go along. For example, I am exploring alternatives to useUpdate that are more robust for video game style apps right now. It may be a little bit longer before there is a stable version available.