React19 compatibility

[connectplatform]

Describe the feature you'd like:

Please modify package compatibility to React v19. Right now I get this:
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error react@"^19.0.0" from the root project
npm error peer react@">=18.0" from @react-three/[email protected]
npm error node_modules/@react-three/fiber
npm error @react-three/fiber@"^8.17.10" from the root project
npm error peer @react-three/fiber@"^8" from @react-three/[email protected]
npm error node_modules/@react-three/drei
npm error @react-three/drei@"^9.119.0" from the root project
npm error 6 more (expo, @expo/dom-webview, react-native-webview, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18" from @react-three/[email protected]
npm error node_modules/@react-three/drei
npm error @react-three/drei@"^9.119.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

Suggested implementation:

please add "^18.0.0 || ^19.0.0"

[abernier]

i think this is intended, from what i know, r3f is not (yet) React 19 compatible

r3f v9 will be, but not yet released

[viktaur]

What can we do to fix this in the meantime?

[abernier]

What can we do to fix this in the meantime?

you can keep r3f v8 and react 18 (until v9 + updated drei are here)

[raulrpearson]

@viktaur, they recently added this comment to the r3f readme:

Warning

R3F v8 is not compatible with React 19 or Next 15, which uses React 19. Use the R3F v9 RC instead which can be installed with @react-three/fiber@rc.

Note

While we work on R3F v9 you can track compatibility of different libraries and common workarounds here.

[sxxov]

related: #2213

i've found that forcing drei to work with r3f's v9 rc doesn't work out-of-the-box, due to the shape of the internal .__r3f object structure changing in v9. manually patching them seemed to get me 90% of the way there though, with most utilities just working post-patch.