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

Error: invalid code -- missing end-of-block while executing npm i --save-dev deno-bin #26

Open
vazexqi opened this issue Mar 13, 2024 · 2 comments

Comments

@vazexqi
Copy link

vazexqi commented Mar 13, 2024

Just started happening a few hours ago

npm i --save-dev deno-bin

171 error path /Users/vazexqi/Desktop/cli/node_modules/deno-bin
172 error command failed
173 error command sh -c node install.js
174 error node:internal/process/promises:288
174 error             triggerUncaughtException(err, true /* fromPromise */);
174 error             ^
174 error
174 error Error: invalid code -- missing end-of-block
174 error     at __node_internal_genericNodeError (node:internal/errors:865:15)
174 error     at Zlib.zlibOnError [as onerror] (node:zlib:189:17)
174 error     at processChunkSync (node:zlib:457:12)
174 error     at zlibBufferSync (node:zlib:178:12)
174 error     at Object.syncBufferWrapper [as inflateRawSync] (node:zlib:792:14)
174 error     at Object.inflate (/Users/vazexqi/Desktop/cli/node_modules/adm-zip/methods/inflater.js:6:25)
174 error     at decompress (/Users/vazexqi/Desktop/cli/node_modules/adm-zip/zipEntry.js:80:45)
174 error     at Object.getData (/Users/vazexqi/Desktop/cli/node_modules/adm-zip/zipEntry.js:268:24)
174 error     at Object.extractEntryTo (/Users/vazexqi/Desktop/cli/node_modules/adm-zip/adm-zip.js:552:32)
174 error     at main (/Users/vazexqi/Desktop/cli/node_modules/deno-bin/install.js:54:21) {
174 error   errno: -3,
174 error   code: 'Z_DATA_ERROR'
174 error }
174 error
174 error Node.js v18.18.2
@vazexqi
Copy link
Author

vazexqi commented Mar 13, 2024

I believe the issue is due to https://github.com/cthackers/adm-zip/releases (version 0.5.11) that was just released.
Once I lock it to 0.5.10 it works fine.

@kt3k
Copy link
Owner

kt3k commented Mar 21, 2024

Sorry for the late response, but it seems to be fixed in 0.5.12 already. Can you confirm it?

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

Successfully merging a pull request may close this issue.

2 participants