prometheansacrifice

I think I can. Assigning it to myself.

@wesleybits Could you try to install it in a different prefix (something like `~/.npm`) with `npm i -g esy --prefix ~/.npm` (assumming you have permissions at `~/.npm`)

Thanks! We'll working on improving the error message.

@varnerac Would you be able to provide us with a small repro? It would help to know what $PATH looks like on the shell too

Thanks everyone for taking the time on this PR. I missed reviewing it in the weekend and will try reviewing during the week. Shallow review: looking good. On Sun, Sep...

Thanks for the report and the relevant links. Will try my best to get to this asap.

@EduardoRFS Let's override `conf-jq` at esy-opam-overrides like we have been doing for `conf-gmp`

Thanks. This is definitely something we would like to have in esy itself so that other editors benefit too.

@tatchi The CI failure is because of `esyNativeInstallNpmRelease` not being install via yarn/npm in the Alpine build. Can you see what's going on there? Thankfully, the issue can be repro'ed...

@kyleshevlin Are you running multiple esy processes?