Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken v0.7.3 npx packages #1389

Closed
dcroote opened this issue Aug 22, 2022 · 2 comments
Closed

Broken v0.7.3 npx packages #1389

dcroote opened this issue Aug 22, 2022 · 2 comments

Comments

@dcroote
Copy link
Contributor

dcroote commented Aug 22, 2022

Originally reported on Discord, v0.7.3 of airnode-validator, airnode-admin, and airnode-deployer are broken due to a missing airnode-validator file (see error below).

This is reminiscent of #1246 and #1247, however the v0.7.3 release includes the fix from #1268, which corrected the validator binary path. Given the missing file is the correct validator binary path (which we know works in v0.7.2) this might have resulted from not running yarn build prior to release? Further evidence for this is from socket.dev, which shows the file missing from the package for v0.7.3, but present for v0.7.2.

Error:

> npx @api3/[email protected]
npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /home/derek/.npm/_npx/23478/lib/node_modules/@api3/airnode-validator/dist/cjs/bin/validator.js
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/home/derek/.npm/_npx/23478/lib/node_modules/@api3/airnode-validator/dist/cjs/bin/validator.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/derek/.npm/_logs/2022-08-22T01_37_58_062Z-debug.log
Install for [ '@api3/[email protected]' ] failed with code 254
@martinkolenic
Copy link
Contributor

martinkolenic commented Aug 22, 2022

When I was testing this on Friday, I pulled the release from the repo, which might explain why it did work for me (and for some reason I did not use the docker image provided in the cloud).

UPDATE: I don't seem to have the same problem when testing the Docker image I get from the release commit or the api3/airnode-deployer:0.7.3 image. This must be a npx-specific problem; sorry this flew by without me noticing.

@bbenligiray
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants