Andrey Popp

Thanks for clarification and for suggestion to use `R.open_error_msg`!

Can be done via destructuring and [ES object rest/spread](https://github.com/sebmarkbage/ecmascript-rest-spread): ``` const point3d = {x: 1, y: 2, z: 17} const {z, ...point2d} = point3d; ```

@omefire that's the place where local vs non-local builds take different build paths — https://github.com/reasonml/esy/blob/esy/src/esy/buildEjectCommand/runtime.sh#L98-L105

@omefire there's JS builder in `refactor/build-repr` branch. I think it is possible we could add such feature only in JS build but now it is too early to decide as...

@omefire right, I agree

Should we move issues over to reasonml/esy?

That could help: https://github.com/discoteq/flock The question is how do we introduce `flock` to an esy's environment? It is **not desirable** we require it installed as external dep. One option is...

> to protect concurrent builds for the same package under different projects (for example, building ReasonReactProject and ReasonProject at the same time)? This one. The first case is covered with...

I'd expect it to work... probably it reuses `shrinkwrap`'ed resolution? Did you try to remove `shrinkwrap.yaml` before trying to run `esy install`?

Agree, this is needed. Right now I use ``` % esy make build ``` for that where `make build` just runs package's build system. This is not idea as env...