Florian Verdonck

One idea I originally considered was to download the Fable daemon binaries (or a single file) from a GitHub release artifact. This way, the post-install process could run a simple...

I just took a look at how the big players are solving this problem. Having the daemon as a single file is a reasonable approach when it comes to installing...

Shameless self-promotion but you could consider something more like https://youtu.be/t3R-GnW-r9g?si=ltRVzBC7yy_Ip7Xf Let the changelog be the driver, use `gh` cli to make release (and thus git tag)

Would be interesting short-term, long-term you want to get rid of postinstall all together.

It is quite the turnoff that the PR description mentions code that doesn't compile: The goal is to wrap Jsx.element type identifiers in braces?

@cknitt, there's no need for me to hold up the release for this. We can revisit and possibly merge it later.

I recently used this helper in my code: ```res let forOf: (array unit, unit => bool) => unit = %raw(` function (items, callback, shouldBreak) { for (let i = 0;...

Maybe this should more autocomplete `JsError.throwWithMessage("Hello!")` and ` JsExn.throw("some non-error value!")` instead. ([docs](https://rescript-lang.org/docs/manual/v12.0.0/exception)) I cannot ever remember those things and I basically want to have something show up when I...

## Split bsc module system flags for stdout compilation ### Problem When `bsc` compiles to stdout (no `-bs-package-output` specified), it hardcoded the Commonjs module system: ```ocaml (* compiler/core/lam_compile_main.ml:295 - old...

Hi @cristianoc , the splitting of the bsc arg turned out quite ugly. To satisfy bsb, a lot of code was generated while it seems a lot more straightforward in...