ocaml/dune

Simplify/Clarify Web site building

Aperta

#663 aperta il 29 mar 2018

 (9 commenti) (0 reazioni) (0 assegnatari)OCaml (478 fork)github user discovery
good first issuehelp wantedjsoo

Metriche repository

Star
 (1882 stelle)
Metriche merge PR
 (Merge medio 1g 20h) (345 PR mergiate in 30 g)

Descrizione

I think this use case deserves to be better explained, maybe in the "quickstart" section. Currently there are many things that are not very clear:

  • An executable with (js_of_ocaml (..)) and a public name will build/install the .exe, not the .js. This is not intuitive.
  • If I have an HTML file that uses the generated js, it's not clear how to put the website together in order to visit it without either pointing inside _build or moving the files around.
  • What's the right way to handle static data and/or bundle additional js files?

I feel like the basic supports is there (and I ended up successfully building my .bc.js) but it feel fairly unfinished. I'm not sure what the idiomatic dune way is, but a little bit of polish would be sufficient to make the situation much better. Maybe with a new target that would put the files together and launch the website, or something like that ?

Guida contributor