melange-re.github.io

melange-re.github.io copied to clipboard

Should we mention in the [data representation table](https://melange.re/v2.2.0/communicate-with-javascript/#data-types-and-runtime-representation) that OCaml objects translate into JS objects? Ref: https://github.com/melange-re/melange-for-react-devs/pull/21#discussion_r1466592210 cc @feihong

jchavarri

https://github.com/melange-re/melange/pull/1034#discussion_r1465803409

jchavarri

[discuss.ocaml.org/t/whats-possible-with-melange/13806/2?u=davesnx](https://discuss.ocaml.org/t/whats-possible-with-melange/13806/2?u=davesnx) [discuss.ocaml.org/t/what-are-the-limits-and-prerequisites-of-using-dependencies-with-melange/13688](https://discuss.ocaml.org/t/what-are-the-limits-and-prerequisites-of-using-dependencies-with-melange/13688)

davesnx

Guide: Integrate melange with vite and vitest

4

- Explain _build folder artifacts - Explain node_resolve's rollup plugin

davesnx

https://github.com/melange-re/melange/pull/985

jchavarri

anmonteiro

I don't think the docs mention the `{. "foo": string}` syntax for types, looking at https://melange.re/v2.1.0/communicate-with-javascript/#using-jst-objects. Also should include some explanation for the Reason syntax feature, where `{. "box": string}`...

jchavarri

Externals should list all the params of the function, and type aliases should be avoided: ```ml external foo : int -> unit = "foo" let () = foo 2 (*...

jchavarri

Explain how OCaml modules compare to Js modules

1

- let default export trick - What gets exported, how to create a mli to hide stuff - mel.as on exports - The field for commonjs/es6 from dune

davesnx

Update communicate-with-javascript.md

1

I managed to fix some of the feedback I found while revisiting the documentation with JS. I tried to suggest stuff and annotate some of my feedback as comments. We...

davesnx