Always worried that the bindings I find on someone’s github has partial coverage and may be missing something we need. Without the ability to extend, you end up with like
Express2.resfiles that have one function in them
I always thought yarn’s patch protocol was a super useful feature for avoiding this problem: yarn patch | Yarn
There’s a bit of friction with finding, installing the library, installing the rescript version of it, and adding it again to
rescript.jsonthat makes just feel easier to copy paste into a new file
That’s definitely easier, and what I’d been doing until pretty recently. Our compilation times had started to creep up a bit, and breaking these vendored bindings into separate packages in our monorepo yielded a pretty significant reduction in incremental and “warm” (bs-dependencies already compiled) compilation times.
That said, it’d be pretty convenient if the compiler could pick up some metadata from package.json of installed packages instead of relying on manually syncing these