You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I'm understanding correctly, Fable.React v9 targets React 18, while older versions target 17. However, when I use femto --resolve I get the following result:
[12:56:43 INF] Fable.React requires npm package react
[12:56:43 INF] | -- Required range >= 18.0.0 < 19.0.0
[12:56:43 INF] | -- Resolution strategy 'Max'
[12:56:43 INF] | -- ✔ Found version 18.2.0 that satisfies the required range
[12:56:43 INF] Fable.React requires npm package react-dom
[12:56:43 INF] | -- Required range >= 18.0.0 < 19.0.0
[12:56:43 INF] | -- Resolution strategy 'Max'
[12:56:43 INF] | -- ✔ Found version 18.2.0 that satisfies the required range
However, I'm sticking with Fable.React v8 specifically to not jump into Fable the 4 ecosystem until it is more stable. This presents a problem, since Feliz 1.68 depends on react gte 17 lt 18:
[12:56:43 INF] Feliz requires npm package react
[12:56:43 INF] | -- Required range >= 17.0.1 < 18.0.0
[12:56:43 INF] | -- Resolution strategy 'Max'
[12:56:43 INF] | -- ✔ Found version 17.0.2 that satisfies the required range
[12:56:43 INF] Feliz requires npm package react-dom
[12:56:43 INF] | -- Required range >= 17.0.1 < 18.0.0
[12:56:43 INF] | -- Resolution strategy 'Max'
[12:56:43 INF] | -- ✔ Found version 17.0.2 that satisfies the required range
Because of this, my dependencies will never resolve properly.
The text was updated successfully, but these errors were encountered:
If I'm understanding correctly, Fable.React v9 targets React 18, while older versions target 17. However, when I use
femto --resolve
I get the following result:However, I'm sticking with Fable.React v8 specifically to not jump into Fable the 4 ecosystem until it is more stable. This presents a problem, since Feliz 1.68 depends on react gte 17 lt 18:
Because of this, my dependencies will never resolve properly.
The text was updated successfully, but these errors were encountered: