This is something we discussed in the past, I tried to do it in #285, but we didn't merge at the end because moving interfaces to another .dll broke .NET builds. If you're planning to release Feliz 2 @Zaid-Ajaj, maybe this can be a good opportunity to try it again. The idea is:
Extract Fable.React types (at a minimum ReactElement) to another library, say Fable.React.Types, and publish it independently.
Publish a new Fable.React version that depends on this library, but probably after that we can deprecate it.
Make Feliz 2 depend on Fable.React.Types but no Fable.React. This will still make Feliz elements compatible with Fable.React, but it will avoid the dependency when not needed.
Other libraries that basically only need ReactElement can do the same, like elmish-react and the upcoming Feliz.JSX.React.
If this is OK with you I can make the Fable.React split and send a new PR 👍
This is something we discussed in the past, I tried to do it in #285, but we didn't merge at the end because moving interfaces to another .dll broke .NET builds. If you're planning to release Feliz 2 @Zaid-Ajaj, maybe this can be a good opportunity to try it again. The idea is:
ReactElement
) to another library, say Fable.React.Types, and publish it independently.If this is OK with you I can make the Fable.React split and send a new PR 👍