Conversation
|
@MangelMaxime I was waiting for .NET 9.0 to be released officially before we do that, but if you prefer, we can start a bit earlier. Let me know. |
|
@ncave I am fine with waiting. Only reason, I thought about updating the REPL metadata was because someone reported a bug for Fable.Browser.Event using the REPL when it was already fixed. The reason, why the REPL code and his code were wrong was because both are using an old version of the package. We can keep this PR open, and wait for .NET 9 to be released before updating the metadata 👍 |
|
@MangelMaxime Technically you can just drop in the package replacement for |
Hello @ncave,
I was trying to update the metadata dependency and encounter some breaking changes along the way. I was able to fix the change of path for calling the different tools and move to
Ionide.ProjInfoinstead ofDotNet. ProjInfobecause the list of DLLs returned was empty andDotNet. ProjInfois not maintained anymore.However, when running the script and running
fcs-export.fsprojsuccessfully, I only get the .NET standard DLLs exported.Browser.XXX.dllandFable.Repl.Lib.dllis missing from the output.Could you please check if something has changed in your fork that we need to update ?
In order, to run
./src/Export/build.shyou need to have your F# compiler fork folder alongside the REPL folder in a folder namedfsharp_fable.