Running esy with an out of date esy pesy, should fail to build.

[jordwalke]

If you forgot to run esy pesy after changing the package.json in a way that affects the output generated files, then running esy or esy build should fail. This is lower priority, but would be nice. The way it's done is that there would be two commands.

build: "pesy refmterr dune build -p package-name",
buildDev: "dune build -p package-name"

Where pesy knows it's running in the esy build environment instead of as an esy pesy command. We discussed this and it wasn't so easy to detect which of the modes we're in, but thought I'd make a task to track this feature.

[ManasJayanth]

Another issue was that we wanted pesy to be build dependency. build: "pesy refmterr dune build -p package-name unfortunately requires it to be a regular one.

This reason we wanted pesy to be dev only dependency was because of dependency conflicts. If pesy can run in build env (during a regular non dev build), then even scoped package names handled well

[ulrikstrid]

Shouldn't pesy and refmterr be used in buildDev and not build?

[ManasJayanth]

Closed by #116