Closed s8mathur closed 5 months ago
It doesn't look a problem with the package. Try npm cache verify
or npm cache clean --force
and repeat npm ci
Thanks Massimo, will try the verification step and open a separate issue if any changes are needed. Thanks!
@s8mathur, I was able to trigger this on one of my VMs. I am going to update the package-lock file.
Since Feb 02, my ARM64 builder has been reporting the following error when compiling the binary using `npm ci --silent`` as seen in the build.sh script. Any pointers are appreciated; thanks!