prometheansacrifice

Since the project is using both NPM and esy, could you, perhaps, use esy.json instead?

Are you looking for `self.root`? https://esy.sh/docs/environment/#variable-substitution-syntax

Is `protoc` present at `#{self.root / 'usr' / 'protoc' }` ? Then, it should be ``` "exportedEnv": { "PATH": { "val": "#{self.root / 'usr' : $PATH}", "scope": "global" } ```

`self.root` wont help here because it would be evaluated in the context of `@opam/conf-protoc`. Unfortunately, I dont have a nice solution to offer, other than making `protoc` the dependency of...

How can I reproduce this?

This fails ``` "dependencies": { "ocaml": ">= 4.12.0", }, "devDependencies": { "@opam/ocamlformat": "0.26.1", }, ``` But the following works ``` "dependencies": { "ocaml": ">= 4.12.0 < 5.0.0", }, "devDependencies": {...

Error message was, ``` error: No solution found: Conflicting constraints: @grain/libbinaryen -> @opam/ocamlformat -> ocaml@>=4.8.0 && ocaml@ ocaml@=5.2.0 ```

> I wonder if the proper fix is to ask user to specify a concrete OCaml version. Maybe not through the package.json but interactively on the first project install? I...

> users would want to work with a specific OCaml compiler version, not picked "arbitrary" based on other constraints Informed users: yes. But there's always someone who forgets, didn't read...

Are you suggesting that this interactive selector is triggered when the user hasn't specified the exact compiler version *instead* of trying to club `ocaml` together with other packages and solve?