Do not error when publishing, existing binary exists, and it is identical
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
At the moment, `node-pre-gyp package publish` errors when there is already an existing version. It would be great if it could download the existing version and only error if the new version is not the same as the existing version.
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 `node-pre-gyp package publish` command and how it handles an existing version. Check how the existing binary is downloaded and compared with the new one; done means an identical binary publishes without error while a different binary still errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100