Installing from a repo pointer in package.json downloads a binary
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.8k
- Forks
- 704
- PR merge metrics
- No merged PRs in 30d
Description
The gist of it is that when you're set up pointed at a git repo. it should do a build of everything. If it's coming from the NPM registry it assumes the code is already generated, and tries to download a binary. It's instead successfuly downloading a binary, but that code isn't there (and isn't being generated cause it thinks it's coming from the npm registry).
See here: https://github.com/nodegit/nodegit/issues/561#issuecomment-101769115
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 with package.json installation handling and compare a git repository pointer with an NPM registry install; read the linked issue comment for the related behavior. Done means repository installs build the code instead of downloading a binary as though generated code were already available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, node.js
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100