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?

Lot of packages depend on bs-react-native, such as this. We'll need to work with these package owners to migrate to the next release of reason-react-native.

Preliminary list from npm search:

• [x]

Hi guys!
I love your product.
Do you think you guys could make the Avatar previewer sticky? It'd make the generator a more comfortable mobile experience since users wouldn't have to scroll up all the time too see how the different choices look on their character.

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.

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

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.

It would be great to have a couple of example apps, similar to Redux and co. inside an examples folder in the repo.