cache pnpm and runtime when `cache` is enabled
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 140
- Forks
- 19
- Avg merge
- 13h 19m
- Merged PRs (30d)
- 3
Description
the following installs node & pnpm every time it's ran, as they do not get cached (they get downloaded & installed before cache is recovered)
uses: pnpm/setup@v2.1.0
with:
runtime: node@26
cache: true
Run pnpm/setup@v2
# no cache here
Installing pnpm...
Installation Completed!
Installing runtime node@26...
Restoring cache...
# there is cache now
ref: https://github.com/SuperchupuDev/tinyglobby/actions/runs/33325776540/job/99295515418
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 GitHub Action setup flow that installs pnpm and the Node.js runtime, then locate where cache restoration occurs relative to those steps. Reproduce the referenced workflow to confirm the current order; done means the cache is restored before pnpm and the runtime are installed, avoiding repeated downloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, typescript
- Domain
- ci-cd, devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100