pnpm logs two different content-addressable store paths
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
When pnpm/action-setup installs pnpm, the logs show:
Content-addressable store is at: /home/runner/.pnpm-store/v3
But when pnpm installs the dependencies, it logs another path:
Content-addressable store is at: /home/runner/setup-pnpm/node_modules/.bin/store/v3
The second one is correct. Is it because PNPM_HOME is set after the installation of pnpm instead of before?
I'm not passing anything special to the actions:
- name: Install pnpm ⚙️
uses: pnpm/action-setup@v2
with:
version: 7.x
- name: Install dependencies ⚙️
run: pnpm install --frozen-lockfile
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 with the pnpm/action-setup@v2 workflow step and compare its installation environment with the following pnpm install --frozen-lockfile step. Trace when PNPM_HOME and the content-addressable store path are set; the work is done when both log messages report the same intended store path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100