corepack up vs corepack use pnpm
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
I want to update pnpm in a dir by using corepack up but it creates an extra dir ~/.cache/node/corepack/v1/corepack-* which is 20MB and ~/.cache/node/corepack/v1/pnpm/10.6.5. corepack use pnpm only creates ~/.cache/node/corepack/v1/pnpm/10.6.5. Extra dir should be removed.
corepack cache clean
cd dir
corepack up
corepack cache clean
cd dir
corepack use pnpm
Contributor guide
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
Reproduce the behavior in a directory using the two command sequences, comparing the cache after corepack up with the cache after corepack use pnpm. Trace the corepack up command entry point and cache handling; done means updating pnpm without creating the extra corepack-* directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100