i tracked this down to https://github.com/ZJONSSON/node-unzipper/issues/271

the original issue report talks about upgrading from node 18 to node 19, however there is also this comment in the thread: > Can either of you confirm what I say in my previous comment? In my case using Node 18.15.0 no error occurs. However, the files are corrupted if Node 18.16.0 is used.

and looking at the image we use

docker run --rm -it node:18-alpine@sha256:1ccc70acda680aa4ba47f53e7c40b2d4d6892de74817128e0662d32647dd7f4d --version   
v18.16.0

ah, looks like a fix has been merged recently https://github.com/ZJONSSON/node-unzipper/pull/274 on May 10th

sadly, upgrading to

0.10.14

does not appear to fix the issue

filed a tracking issue for this https://github.com/garden-io/garden/issues/4467

see also https://github.com/go-task/go-npm/issues/7#issuecomment-1568567117

there's no good immediate replacement for

unzipper

for our usecase, as we need streaming support and not a lot of the libraries provide that. additionally, most of the unzipping libraries in the ecosystem are even less maintained than

unzipper

- they might suffer from the same issues on Node

>=18.16.0