reasonml-old / index Goto Github PK

Things like this for example are awesome little examples of using OCaml/Reason/Bucklescript!

So BuckleTypes org is great but the current workflow for creating and consuming typings is hard to scale. If I want to use the binding I have to:

1. Discover it
2. install with npm
3. add to bsconfig

while hoping for version compatibility with whatever I use.

On the other hand of the spectrum a creator has to create a repo, add it to npm (or at least add package.json) and be willing to maintain it over time. Otherwise it gets abandoned and everybody is sad.

Solution: consuming

The most straightforward¹ solution is to create a centralised repo for bindings. @ryyppy² suggested that we could copy the implementation from TypeScript 2.

How I imagine the perfect workflow is that there's a single bucklescript command - let's say install which pulls typings from the central repo/place and adds them to your project. I don't think it needs to do resolve version because it can either use yarn.lock or check module version directly in node_modules. You end up with typings added to your bsconfig and probably to package.json. afterwards you'd probably need to run yarn/npm install to actually pull those in.

Solution: authoring

I'm not sure what's the perfect way to design publishing specs and vendoring specs. I imagine that typings need to be owned by the community. I'm not sure how to model it so that it's both easy to contribute to and maintains good quality.

Let's discuss ideas before discussing the implementation

So before we bikeshed about particular implementation and how to resolve the problems with it, let's think about the workflow. I'll try to write down everything that we mentioned on Discord if I have time. Any contribution below is much appreciated.

1: not really straightforward
2: I don't know their github handle