[Feature request] Add option to use local pre-compiled node addon module
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
Hi,
We have a library that uses different versions of node addon module based on user's platform. Looks like it is not supported to implement this customized experience with current node-pre-gyp workflow through (package.json).binary.host and (package.json).binary.module_name.
One solution is for our library to download the pre-compiled node addon module based on user's platform during installation, and then have node-pre-gyp use this local tarball to build.
Thanks
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 reading the node-pre-gyp workflow around package.json binary.host and binary.module_name, then trace how installation selects and builds addon archives. Define how a library can provide a platform-specific local pre-compiled tarball and how node-pre-gyp should consume it. Done means the workflow supports that local tarball without requiring the existing host or module-name behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100