Blaine Bublitz

I still haven't found a suitable solution to this (though my attention was pulled in another direction). @EduardoRFS I wonder if my solution will end up building upon your #1348...

@ManasJayanth Do you have any ideas on how to solve my issue above? It'd be cool to have something that I could implement.

This is a blocker on both https://github.com/grain-lang/binaryen.ml/issues/42 and Grain's usage of libwasmtime (because it uses the same mechanism described in that issue).

That makes sense as a workaround, but should esy be updated to handle the `{= version}` constraint when a resolution is being applied? It is handled when there is no...

> It's important because you can do conditionals on it. I thought that was when you used `{= dev}` or do you mean another way?

Ran into this problem on Fedora. They have `sha1sum`, `sha256sum` and `sha512sum` commands though.

`EsyBash.currentEnvWithMingwInPath` is also referenced in https://github.com/esy/esy/blob/70d42838fb3f50b44ed8443dc42be30002a08536/esy-lib/RewritePrefix.re#L19 and https://github.com/esy/esy/blob/master/esy-solve/Solver.re#L627

This seems great! I was having an issue yesterday in that I had outdated submodules which caused esy to build incorrectly and fail when I ran it.

@ManasJayanth Do you know why `runScript` uses `ChildProcess.runToStatus` instead of `Bos.OS.Cmd.run` here: https://github.com/esy/esy/blob/70d42838fb3f50b44ed8443dc42be30002a08536/bin/esy.re#L720-L728 This seems different than the rest of the script running, which may be the cause of this...

@jonschlinkert if I were updating a 0.10 or 0.12 service, it'd be to node 4 so maybe keep that around longer than EOL? Remember that product owners can't move as...