I've been thinking about this a bit, as a JS developer who is experimenting
with OCaml (in my non-existant free time). I don't use the CommonJS flow in
my day job although we do have many projects which our internal
build/dependency system combines with similar results.


On Wed, Feb 25, 2015 at 6:26 AM, Jordan W <jordojw@gmail.com> wrote:

>
> I created a proof of concept called CommonML, which lets developers use
> their familiar CommonJS workflow with OCaml:
> https://github.com/jordwalke/CommonML


My initial thoughts were to stick with the OPAM repositories; even if I
have to make a local OPAM repo server it seems like leveraging the existing
ecosystem is a good idea. My experiments use a dedicated `opam switch` for
the project, enforced by the Makefile (which might not scale to multiple
projects, but I haven't tried that yet).

I can think of one good reason to share OCaml and JS dependencies on the
same server though, and that's including a JS library in a js_of_ocaml
project. Certainly using a single package.json file to specify both JS and
OCaml dependencies is an interesting idea (even if under the hood we
eventually find a way to use OPAM for the OCaml projects).

Cheers,
Andy