pnpm cache could prune store before caching
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
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
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 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.
Assessment
- Tech stack
- node.js, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100