Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

I am running fnm on Alpine, meaning no glibc thus official node.js build can't be used. I set the appropriate mirror env variable to the unofficial one, but it still fails to install because my arch is x64 but the unofficial build has -musl appended onto that. Hopefully a flag to override that can be added

This might be a good way to reconcile Dream, Piaf, and the rest of the "ecosystem" for esy users.

The branch can probably be maintained by constantly cherry-picking a single commit that adds esy.json and subtracts src/vendor. This could even be done in CI in the long term, but probably we'd rather get rid of src/vendor by actually upstreaming or releasing the protocol projects, instead.

As marked in https://github.com/briskml/brisk/blob/master/examples/hacker-news/app/Story.re#L82, we'll need to transform incoming html.

<p> tags are not rendered with proper margin/padding by Cocoa in NSTextView by default, and instead of manually changing document attributes on ObjC bindings side, simply pre-processing html text and replacing paragraphs by newline characters seems more prefe

So Docusaurus is amazing for building sites and documentation and I really want to use it. It would be awesome to also port over the current homepage to a custom React component that can be used on the homepage too.

Relevant issue: jsdelivr/jsdelivr#18166

Update

So apparently jsdelivr will minify the main entry file and add .min. in its name. Since we check for the name. And the minified file could saves a lot of bytes and improve parsing speed for the bundler.

So we would save this default file provided by jsdelivr, check with what's provided in main field

Similar to OCaml documentation - lets do https://realworldocaml.org/ automatically so that learning Reason is painless.