ocaml/dune

Simplify/Clarify Web site building

Offen

#663 geöffnet am 29.03.2018

 (9 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)OCaml (478 Forks)github user discovery
good first issuehelp wantedjsoo

Repository-Metriken

Stars
 (1.882 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 1T 20h) (345 gemergte PRs in 30 T)

Beschreibung

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 ?

Contributor Guide