Invalid "esy" version with MacOs about esy

[ulrikstrid]

In the example of luv I think npm install esy generates a package.json or adds esy to the already existing one.

[dannywillems]

Same here with lubuv CI

[ulrikstrid]

I see what happens here. It looks like esy is trying to install itself and fails. We should probably special-case esy and just make sure the current version of esy matches the constraint.

[ManasJayanth]

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

[James-McGeough]

Seeing this on Debian as well

[aantron]

Do we know what is actually causing this issue? It appears that something has changed in esy, since all the builds worked previously.

[lubegasimon]

Could someone have found a workaround for this issue?

simon@MacBook-Pro expenditure_tracker % npx esy start     
error: invalid "esy" version: ^0.6.12 must be one of: 1.0.0
  reading package metadata from link-dev:./package.json
  loading root package metadata
esy: exiting due to errors above