The main difficulty for Three.js binding with Glutinum is that Glutinum only support one file at a time for now.

But in theory, you can do the transformation and adapt the code where needed.

You can also start porting only the API you need and not everything at once.

I don't know how good it is but there seems to be a old binding version for Three.js here.

github.com/w0lya/fable-...

The goal of this alpha is for people to be able to experiment with Nullness in Fable and see how it plays out both in term of usage and for creating bindings.

2/2

Something to note, is because of how Fable works you need the libraries to have been upgraded to use nullness to.

This is something we are still experimenting about and we will write a blog/documentation about it later.

F# nullable should works for JavaScript at least.

We are looking into how to support it for TypeScript, as we originally wanted to emit native null check for TypeScript, but we will probably do it in a similar way as for JavaScript.

1/

🦾 Major hat tip to @compositional-it.com for advancing it and for all of the contributors like @mangelmaxime.bsky.social and many others for Fable. We love @dzoukr.cz 's SAFEr stack and are lifting its opinions for our static site generator (and are building an Oxpecker back-end option for it). 💙

Hello,

In theory this is possible but I am not well verse into the status of the Rust target. I think it is usable but we need more users to find bugs or share their experiences.

You should open a discussion on the Github repo to ask feedback from Ncave

github.com/fable-compil...

Adding a new target like done for Python, Rust, etc. is indeed the way to go.

If someone want to invest time on it, we welcome new contributions but this is a big task to tackle as even if Fable make it easier mapping one language to another is not an easy task.