`npm download` fails silently
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 36
- Forks
- 14
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 1
Description
Normal download logs are like this:
os.type() is: Linux
os.arch() is: arm64
Downloading Libzim from: https://download.openzim.org/release/libzim/libzim_linux-aarch64-manylinux-9.7.0.tar.gz
Running Extract: [tar --strip-components 1 -xf ./download/libzim_linux-aarch64-manylinux-9.7.0.tar.gz -C ./download]
Successfully downloaded and extracted file
gyp info it worked if it ends with ok
(last line is not from download but indicates we have move to next command)
But on some occasion (probably because download fails because we have a server issue ATM, see https://github.com/openzim/node-libzim/actions/runs/26953039465/job/79522881032 for such an occurence):
os.type() is: Linux
os.arch() is: arm64
Downloading Libzim from: https://download.openzim.org/release/libzim/libzim_linux-aarch64-manylinux-9.7.0.tar.gz
gyp info it worked if it ends with ok
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the npm download entry point that emits the download and extraction logs, and compare the successful and failing output shown in the issue. Trace how a failed server download is handled before the next command runs. Done means download failures are surfaced clearly and do not silently continue to the next command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100