React 17.0-rc.0 required for RTF 5.0?

[stephent]

Just bumped from 4.2.21 to 5.0.0 and on running npm i, I get some new warnings:

npm WARN [email protected] requires a peer of react@>=17.0-rc.0 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of react-dom@>=17.0-rc.0 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of [email protected] but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of react-three-fiber@^4.2.20 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of three@^0.119.1 but none is installed. You must install peer dependencies yourself.

My app is running on react 16.13.1 and there are other dependencies which prevent a move to 17.0-rc.0 at this time.

Any hints on how best to handle these warnings?

(Thanks for RTF - it's fantastic, as is drei!)

[drcmda]

i think ncu just updated the peerdeps, i honestly dont know why it touches them in the first place. it should absolutely run with stable react. i'll rectify this next patch version.

[stephent]

Ok - thanks! Yes, seems to run just fine.

[axelboc]

I'm still seeing the warning in v5.1.4. Well, the warning is now about react@>=17.0 and react-dom@>=17.0.

[axelboc]

react-reconciler should probably also be downgraded since the latest version doesn't support React v16 any more. Managing dependencies is the worst 😓 😄

[drcmda]

this is a bit of a mess, the reconciler situation. but given that i released v5 with react 17 in mind i think it should stay or else i can't move with the updates they release for this major - im especially interested in the changes regarding concurrent mode . for normal react apps r17 doesn't really change anything, but they do have some surprises for custom renderers.

what is possible though is that you alias react and the reconciler to something that suits you.

[axelboc]

Oh right, I remember seeing a whole bunch of Concurrent mode-related stuff in the v17 release notes. Oh well, React 17 it is! 😄