updated fable-library-js to ^2.0.0-beta.3

[laurentpayot]

Fixes #37 (and thoth-org/Thoth.Json#223)

Used Bun to remove the old version and add the latest beta version of fable-library-js

[nojaf]

This is only relevant if you also bump the Fable.Compiler nuget package. Those need to be in sync.

[laurentpayot]

My last commit updated Fable.Compiler to version 5.0.0-alpha.13 in Directory.Packages.props.

Is that all that’s needed?

[nojaf]

I'm not sure, did you test any of this against your own project?
Would have expected https://www.nuget.org/packages/Fable.AST/5.0.0-beta.1 to also need a bump.

[laurentpayot]

I will try tomorrow tonight and let you know.

[laurentpayot]

Last commit updated Fable.AST to 5.0.0-beta.1

I built vite-plugin-fable with bun install, then linked it to my project with pnpm link.
Everything seems to be working, both in dev and prod modes 🎉

[nojaf]

Alright, works for me.
Thank you!

PS: never use your main branch to send PRs. I was going to bump the version as well in your PR and that isn't allowed if you use your default branch.

[laurentpayot]

PS: never use your main branch to send PRs.

Will do. In the future, do you want me to do Fable version updates like this regularly?

[nojaf]

Do those you need for yourself, I'd say. It might be interesting to document this process somewhere.

[laurentpayot]

Well I will at least when the plugin is broken. I remember using paket for updates is out of the question for you, right?
When Fable 5 is out of alpha/beta, I will probably submit a PR and try to find the time to write some documentation.

[nojaf]

Why would want to use paket? It is unmaintained and can break every dotnet SDK?
What advantages would this have over NuGet?

[laurentpayot]

Because of paket update, amongst other reasons.
The last paket commit is from six months ago. I have seen worse in the .Net ecosystem.
Anyway don’t worry, I will stick to NuGet because I do not want to fix something that is not broken.