popcodeorg / popcodeorg/popcode
Cache bower packages during deploy
Open
Nobody has claimed this yet.
deployment
- Dominant language
- JavaScript
- Stars
- 191
- Forks
- 143
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 5
Description
We cache npm packages, but from watching a deploy just now, it looks like it downloads a fresh copy of the bower packages every time. Should be able to speed up deploy a bit by caching them.
Contributor guide
No contributing guide indexed for this repository
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 locating the deploy configuration that caches npm packages and the step that downloads Bower packages. Trace how the existing npm cache is configured and identify where Bower dependencies are installed. Done means deploys reuse cached Bower packages instead of downloading a fresh copy each time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100