cache builds locally.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
@springmeyer and I discussed this at some length on freenode #mapbox last Friday.
Here are my notes: https://github.com/bukzor/node-pre-gyp/commit/c6481ae384a86bc9f3799fb666076b4d08584f6b
The general idea is that if you build something with node-pre-cache twice, the second build should be cached and very quick, even if the upstream manager has not published a build for your platform.
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 linked commit c6481ae384a86bc9f3799fb666076b4d08584f6b and the issue notes. Then trace how node-pre-cache builds are handled locally. Done means a second build is cached and very quick, including when no upstream build exists for the platform.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100