Maxime Mangel
Maxime Mangel
@Freymaurer Did you see a similar issue when working on Feliz plugins ?
Hello @ThisFunctionalTom, Are you trying to consume the packages via NuGet or using `ProjectReference`. If this is the former, you need to make sure to release a Fable compatible package....
Could try compiling using `--test:MSBuildCracker` flag ? This is using MSBuild to resolve the dependencies instead of Buildanlyzer. Resolution of the project is done by https://github.com/fable-compiler/Fable/blob/main/src/Fable.Cli/BuildalyzerCrackerResolver.fs Or the new when...
I think it makes sense, because in the fsproj we can use `Fable.Core` or `fable.core` for the name of the dependency and it resolve to the same package. At least,...
Hello, This is by design. `nullness` in F# is checked at compile type, so we don't generate additional type information at runtime. You can see a discussion about it here:...
We don't have an option for generating a native equivalent here. The closest is to use Fable option type. When F# get support for anonymous DUs, we will probably be...
@ncave I though I had it released. I just made a new release for Fable 5