thanks for your explanations. > - with opam every time you create switch you need to compile everything from scratch, with esy we try to reuse as much as possi

thanks for your explanations. > - with opam every time you create switch you need to compile everything from scratch, with esy we try to reuse as much as possible from the build cache Yes, that's definitely useful. > [...] for now you can use package.json for npm/yarn for bucklescript dependencies and esy.json (esy looks for esy.json before package.json) for native dependencies. So by acting like we use esy on Bucklescript, when we actually use npm, we get a very similar result?