Results 92 comments of Eduardo Rafael
trafficstars

The problem is on version constraints ```sh ## will add ^3.6.1 esy add @esy-ocaml/[email protected] ## is ignored esy add @esy-ocaml/reason@^3.6.1 ```

@bentxt did you tried to remove the `.esy`? This is not the solution of course but it may be a problem of stale files with wrong permissions or something like...

@bentxt are you on ARM64 / M1? This is a well tested path on esy which makes it weird.

@ulrikstrid your error is different, yours is related to esy not finding cp because esy has a default folder to search on Linux, is known that nixOS sadly doesn't work

@bentxt that's probably the problem then, your somehow got a stale esy-subst and didn't delete. This also happens on Windows but are kind of hard to reproduce, I should try...

@syaiful6 A good start would be to have it available in the CI, I don't expect it to be a any maintenance burden, publishing it is another problem, but if...

@ManasJayanth can you give a look on this? I think it's really important, we could also automatically do a cleanup when running `esy install`

Didn't test it, but I believe the behavior to be right, if @ManasJayanth can confirm it to me we can merge

It's probably not a bug, just that no one made a patch to dune above 2.8 at https://github.com/esy-ocaml/esy-opam-override/tree/6/packages

You can do a local override, something as ```json { "resolutions": { "@opam/js_of_ocaml-ppx": { "source": "phated/js_of_ocaml:js_of_ocaml-ppx.opam#82dd36e72e74d0b141b08aeaf443020bee5da10b", "override": { "dependencies": { "@opam/js_of_ocaml": "*" } } } } } ```