Fable 5.22 is out. Since 5.16:
- Opt-in Temporal dates and times for JS
- Implicit conversion to U2..U9
- Cold builds: project cracking 7.7s to 2.3s ποΈ
- Compilation up to 2.9x faster (server GC + JIT tuning) π
- Faster watch: incremental inline exprs
- Many BEAM and Rust fixes
Introducing Fable.Ripple: fine-grained reactivity for F# and Fable.
A write updates the exact DOM nodes reading the signal. No virtual tree, no diff.
Four focused packages for signals, DOM, forms, and routing.
Try the beta: https://t.co/QVVIYZBpj4
#fsharp
Nacara is back, featuring in-browser interactive snippets powered by Fable. You can now expose your own library code live in your docs so readers can experiment with your API immediately.
See the Thoth.Json docs for a live example!
Nacara is back! π₯
A complete ground-up rewrite running natively on .NET. It's now fully pluggable and lets you turn F# code snippets into interactive playgrounds.
π See it live on Thoth.Json docs: https://t.co/boKyJSzM8n
π Check out Nacara: https://t.co/dDfHciVC4J
#fsharp
Fable 5.14.0, 5.15.0, and 5.16.0 have been released over the past few days! π
These updates feature:
- Improved support for Python, Rust, and Beam.
- Added support for precompiled libraries in fable-standalone (stay tuned for a surprise coming in the next few days!).
#fsharp
Fable 5.6 is officially here! π
π Expanded https://t.co/5NF6gynyUf API support (Path and Directory) for JS & Python.
π€ 100% automated release process achieved for the first time!
#fsharp
Fable 5.5 is out π
This release have a strong focus on fixing bug for JavaScript/TypeScript targets.
It is also trying to make the writing cross-target code easier. Thanks to `https://t.co/iF4u9BDQUb*` target detection as an alternative to compiler directives.
#fsharp
@threepointone We're building a binding for the #fsharp and @FableCompiler communities to implement the full SDK. Every bit helps! οΏ½οΏ½οΏ½ https://t.co/g0mX4EIvOJ
What's better than Fable 5?
Fable 5.1 and 5.2! π (And yes, I totally forgot to announce 5.1).
Both releases bring plenty of fixes across various targets. Check out the release notes for details:
https://t.co/vCVdivdo81
#fsharp
There is a new test framework joining the F# ecosystem: Scriptorium.
It is designed from the ground up as a cross-target testing framework, seamlessly supporting both F# .NET and Fable compilation targets (JavaScript only at the time of writing)
https://t.co/dJEq2BJjmr
#fsharp
Fable 5 has been released π
This is the result of almost 1 year and a half of work from the community and the maintainers.
Huge thank you to everyone involved. β€οΈ
#fsharp
π¨ BREAKING: ππ§π€¨βΊοΈWe just pushed the latest version of Cloudflare bindings for #fsharp. We've generated bindings for a fairly significant cross-section of the supported SDK and API surface for management. #dotnet@FableCompiler https://t.co/qxVKW37D3Q
The wait is over! Fable 5 Release Candidate is officially here. π
After a year of hard work from the community, we're bringing you:
β¨ .NET 10 & F# 10 support
π A massive Python update (now powered by a Rust core & PyPI!)
π Cleaner JS/TS Pojo bindings
https://t.co/NVvA5TxzrV
@vyrotek@raimeyuu Yes, everything in the blog post should still be working. And some improvement where made since then.
However, for type safety people use Feliz DSL in general so they don't escape F# type safety. It depends on the preference.
Fable 5.0.0-alpha.15 has been released.
Lot of improvements have been made for TS and Python target.
It also include fixes for Nullable Reference Types hopefully making us closer to an official stable release. Fable 5 is already used in production by some.
#fsharp