pnpm cache could prune store before caching
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- ci-cd
Research direction
Start by tracing the setup-node implementation for workflows using cache: 'pnpm' and identify where the pnpm store is saved. Evaluate adding pnpm store prune immediately before caching, then verify that the resulting cache excludes unused packages and still restores correctly.
Written by the indexing model from the issue text.
Description
Description:
To avoid the pnpm store growing with each update of packages, the action could guarantee that the cached store is as narrow as possible by running pnpm store prune before storing the cache.
This should result in cache not ballooning over time, and avoiding caching unused packages.
Justification:
Could result in quicker cache save/restore for long running workflows using cache: 'pnpm'
Are you willing to submit a PR?
Yeah I could look at it, if it's something people agree would be useful
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 3
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.
More from actions/setup-node
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
actions/setup-node#1531 · 1 comment · 4 reactions ·
-
feature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 30/100
actions/setup-node#1634 ·
-
actions/setup-node#1628 · 3 comments · 1 assignee ·
-
`npm config get cache` fails with `EBADDEVENGINES` when requiring newer npm versions in `devEngines` Openfeature request
Difficulty 4/5 3-5 days Newbie friendliness 52/100
actions/setup-node#1553 · 12 comments · 2 reactions ·
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 35/100
actions/setup-node#1422 · 4 comments ·
All issues in actions/setup-node
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·