How to handle missing deps?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
If there are missing runtime library deps, npm install on my module, node-pre-gyp will download a binary version and then proceed to try and build from source when the sanity test fails. How can I catch the missings deps issue and avoid doing a local build? I'd rather display an error instead.
Contributor guide
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 by tracing the npm install flow in node-pre-gyp, especially where the downloaded binary's sanity test fails and the source build begins. Determine how missing runtime library dependencies can be detected before that fallback, and consider the work complete when installation reports an error instead of attempting a local build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100