Wojtek Czekalski
Wojtek Czekalski
the build artefacts inside `lib/es6/src/` are your friend.
@threepointone I'm on this one . I did this and rewritten all but one bs.raw js functions to Reason. Since you seem to be on fire maybe we could get...
yes, indeed. I'll push to show you what I have at the moment.
>will push all the opam packages to npm (and related things) What are `related things`? What about naming? Should everything be scoped? If yes how, `@esyopam`? If not, how do...
Also unrelated but exciting - maybe simple, as in pure OCaml packages could include `.bsconfig` for simple `js` interop.
@jordwalke and I talked about creating a repository for the converted opam modules which would also contain corresponding `bsconfig`s. Although it's not clear if it's a good (i.e. workable) solution...
I might be too positive about `bsconfigs`. @dorafmon informed me that he had to fork containers because apparently BuckleScript doesn't support most of the ppx attributes. If it's the case...
Description thanks to @andreypopp : How it works now — there's a bunch of Python scripts which convert opam metadata into npm metadata. Such npm metadata is distributed along with...
Since #98 was resolved the next smaller task is implementing a converter from `opam` to `npm` file using `opam-file-format`. The minimum self contained part of this task would be just...
Description thanks to @andreypopp: yarn/npm use a super naive dependency solver. This is somewhat acceptable for JS code but doesn't scale with OCaml ecosystem. The problem is that with OCaml...