Fable.React version 8 depends on React.Dom gte 18 lt 19 according to femto
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react
- Domain
- frontend
Research direction
Start by comparing the Fable.React v8 dependency metadata with the femto output and the Feliz 1.68 React constraints described in the issue. Confirm the intended React and react-dom version ranges for Fable.React v8; done means femto can resolve its dependencies together with Feliz 1.68.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- F#
- Stars
- 277
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fable-compiler/fable-react
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
fable-compiler/fable-react#243 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fable-compiler/fable-react#241 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
fable-compiler/fable-react#240 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
fable-compiler/fable-react#239 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
fable-compiler/fable-react#232 · 7 comments · 3 reactions ·
All issues in fable-compiler/fable-react
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
speaches-ai/speaches#678 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jellyfin/jellyfin-web#8540 ·