#fablecompiler — Public Fediverse posts

FYI: Fable Compiler: Revitalizing F# with JavaScript & OCaml #shorts: Discover how OCaml's influence, along with the Fable compiler, has revitalized F#. Async's role and its spread through different programming language tiers are also explored. Check the 'History of Programming Languages' paper for more. #OCaml #FSharp #FableCompiler #Async #ProgrammingLanguages https://www.youtube.com/shorts/J_qm9CRUwN8

ICYMI: Fable Compiler: Revitalizing F# with JavaScript & OCaml #shorts: Discover how OCaml's influence, along with the Fable compiler, has revitalized F#. Async's role and its spread through different programming language tiers are also explored. Check the 'History of Programming Languages' paper for more. #OCaml #FSharp #FableCompiler #Async #ProgrammingLanguages https://www.youtube.com/shorts/J_qm9CRUwN8

Fable Compiler: Revitalizing F# with JavaScript & OCaml #shorts: Discover how OCaml's influence, along with the Fable compiler, has revitalized F#. Async's role and its spread through different programming language tiers are also explored. Check the 'History of Programming Languages' paper for more. #OCaml #FSharp #FableCompiler #Async #ProgrammingLanguages https://www.youtube.com/shorts/J_qm9CRUwN8

I was sniped into writing some rudimental bindings for @vuejs for the #FableCompiler
I'm amazed on how well Fable integrates with the ecosystem, you can use F# defined components in .vue files and .vue files in F# defined components

I don't plan to fully implement it (or a DSL like Feliz) as it is a responsibility I don't plan to bear with me right now, but it should be good enough for others to pick up and offer real Vue apps in F#
https://github.com/AngelMunoz/Vuoso

#fsharp #dotnet #webdev

Glutinum 0.11.0 is out, this is another huge release.

If you want the detailed changelog with examples, you can view it from Github:

https://github.com/glutinum-org/cli/blob/f0fafecf06ec129b5d06571eca9a12036d645bd3/CHANGELOG.md#0110

#fsharp #fablecompiler

Fable 4.23.0 is here 🎉

Rust users can enjoy more features and benefits from fixes.

TypeScript, code generation got severals fixes and JavaScript got a regression compared to Fable 2 fixed 😱.

We also welcome a new contributor ✨

#fsharp #fablecompiler

Fable.Form 5 is out 🎉

It is now easily extensible, UI agnostics, support more common HTML5 fields properties out of the box and improve the developer experience overall.

Check out this blog post for details

https://www.patreon.com/posts/fable-form-v5-of-114579171?utm_medium=clipboard_copy&utm_source=copyLink&utm_campaign=postshare_creator&utm_content=join_link

#fsharp #fablecompiler

Join the core team at Amplifying F#

Contribute to F# and it's community through this wonderful initiative by Florian, Edgar, David and Jimmy, a model for Open Source community engagement! https://amplifyingfsharp.io/join-the-core/

#fsharp #fablecompiler

When using Fable.Form myself, I was always annoyed with the need to set information that I don't use, this will be improved in the next version. 🎉

Thanks to the new pipeline builder API for the attributes, you will only have to set the fields that you need.

#fsharp #fablecompiler

I always found it confusing to use `string * string list` to represent options of Select/Radio in Fable.Form.

It is not clear which string is the key or value. Next version will instead use an interface to make it more expressive.

#fsharp #fablecompiler

You can write beautiful, safe, functional code with #fsharp even running in the browser using the awesome #fablecompiler but you have to remember, underneath it all, is still #javascript

Fable.Package.SDK 1.1.0 just got released.

From now on, it will automatically NOT BE included in the dependencies of your NuGet package.

https://github.com/fable-compiler/Fable.Package.SDK

If you don't know Fable.Package.SDK, it is the easiest way to author a Fable library.

#fsharp #fablecompiler

Fable 4.22.0 is out 🎉

Come get the latest improvements for Rust target, and some more for Python and JavaScript.

#fsharp #fablecompiler

Fable developers, I am looking for feedbacks regarding how to supports F# code that target multiples runtimes.

There is a discussion happening on Thoth.Json repo and I would love to hear your thoughs and feedbacks.

https://github.com/thoth-org/Thoth.Json/issues/206

#fsharp #fablecompiler

Do you use Sutil ?

No worries, Fable.Form will also supports it. ✨

#fsharp #fablecompiler

Fable 4.21.0 is out 🎉

Using `jsOptions` via TypeScript target now generate typed code, so you can enjoy your types even when doing some interop.

It also improves FormattableString and Uri supports.

Python also received some love with a fix when reporting errors.

#fsharp #fablecompiler

Fable.Form is one of my most complex piece of software.

After gaining plugin supports, it doesn't require Elmish anymore.

Allowing direct usage in a React component.

Next step, is to look into making it usable from React, SolidJS, FuncUI, Sutil, etc.

#fsharp #fablecompiler

Fable 4.20.0 has been released.

It had new features for Rust and if you use Decimals with JavaScript target you want to upgrade to avoid issues with comparisons.

#fsharp #fablecompiler

Glutinum 0.10.0 is available

The main addition is a new internal memory allowing for a deeper understanding of TypeScript allowing for better translation.

For example, it is now able to support `interface Foo extends Partial<Boo>`.

#fsharp #fablecompiler

Creating Fable library or binding has never been easier.

Glutinum.Template is a new template providing:

- Code formatting
- Automated release based on the Git history
- A demo project to test your library

https://github.com/glutinum-org/Glutinum.Template

#fsharp #fablecompiler

Glutinum 0.9.0 is available.

Glutinum should soon reach feature parity with ts2fable and is already having better understanding of TypeScript in some areas. 🎉

Give it a try using the CLI or via the online tool https://glutinum.net

#fsharp
#fablecompiler

Glutinum 0.7.0 just released.

It improves TSDoc supports and the optimisations done by Glutinum to make the API more F# friendly.

#fsharp #fablecompiler

I would like your opinion on how to map this type from TypeScript to Fable.

There is an open issue on Glutinum repository to discuss it: https://github.com/glutinum-org/cli/issues/98

#fsharp #fablecompiler

🎉 New version of Glutinum is out 🎉

Check it out at glutinum.net

This release is the result of 4 months of work with 38 new entries in the changelog and tripled the number of tests.

This release mark the beginning of the beta.

#fsharp #fablecompiler

Fable 4.17 is out 🎉

Since the last release, we accumulated several fixes and improvements, they are now available to everyone.

Thanks to everyone who reported issues and the different contributors.

#fsharp #fablecompiler

A new Giraffe version, the Web framework for F# 😍😍😍

Superb work from the new team. And kudos to Dustin Morris for bringing in new maintainers!

https://twitter.com/dbrattli/status/1779403695546904854

#fsharp #fablecompiler #web

Fable 4.15.0 is out

No fancy new feature, but several bug fixes which is also important to do :)

#fsharp #fablecompiler

Fable 4.14 is out! Use and contribute to this amazing F# compiler for JavaScript, Typescript and more!

https://hachyderm.io/@MangelMaxime/112019862151001900

#nodejs #fablecompiler #fsharp

To kick March in a bang 💥

Today we released Fable 4.14 which improves signature files support and also implements all possible custom format for DateTime when targeting JS/TS.

You can now go crazy on your DateTime formatting 😏

#fsharp #fablecompiler

Interested in my OSS work?

Read about the work I did in the past months, and what I want to focus on for 2024.

https://www.patreon.com/posts/97581929

#fsharp #opensource #fablecompiler

So here we go: By using the standard Blazor JS interop, we can make a few assumptions about how we can write our Fable code so it can be consumed.
Blazor will be able to consume exported members in a JS file, which can be done easily by having public let bound members in fsharp modules
Once fable outputs the javascript we will have an exported member which then can be called by the Microsoft.JSInterop API surface

#dotnet #fsharp #fablecompiler #blazor #jsinterop

I'm not sure what to do with this #Aurelia 2 beta with #fsharp and #FableCompiler 4
Aurelia has always allowed you to skip the boilerplate when you follow the conventions, but the next version is a little bit more flexible and allows you to customize a ton of stuff, what I'm most interested here is that you can programatically define custom elements
Including containers for DI, Custom Attributes, Value Converters and many other things that exist out there, I think it could be an extensive piece of work but...
With a couple DSLs we could improve part of the DX and hide some of that wiring in a way that matches the F# way
The issue (for many F# devs, not me that's for sure) is that Aurelia ViewModels are based on classes, so all of the component related stuff has to use them (until I find a better way to make it work, I don't think that will change though)