Is it possible to use the binary generated by node-pre-gyp to run npm install?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
I am building a nodejs library that has some binary dependencies. Now, I would like to distribute the library internally as a compiled binary, but without using an npm registry. To do that, I am trying to generated a compiled version of the library with node-pre-gyp, but I am not sure what to do with the generated tar.gz file. npm install on the tar file does not work, as it does not have a package.json file. I assume the expected next step is to use node-pre-gyp to publish it to aws-s3 and then have some registry pointing to it, but I want to be able to run npm install https://myserver.com/mylib/mylib-linux-x64.tar.gz. Is that possible?
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
No files or tests are named. Start by tracing how node-pre-gyp creates the generated tar.gz and how npm install handles a remote archive, then compare that with the proposed AWS S3 distribution flow. Done would be a clearly supported installation path from the direct URL, or a documented explanation of why it is not possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100