Allow workspace-local switch cache location
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 225
- Forks
- 19
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 3
Description
Similar to the yarnPath config option in older versions of yarn, the idea is to allow loading the cache (and ideally populating it) from a local folder within the workspace rather than the user folder.
This allows a yarn binary to be checked into the repo, which is helpful for network isolated CI instances. With the current state, the switch cache must be populated at image build time. This adds complexity when updating yarn versions, as the image must contain all possible yarn versions that a PR/release might run against (both new and old, possibly more in some cases).
Having the binary be in the repo allows it to always be consistent, using the git worktree as a source of truth.
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
The issue names no files or tests; start by locating the current switch-cache handling and reviewing the older yarnPath behavior it references. Done would mean the cache can be loaded and ideally populated from a workspace-local folder, allowing a repository-managed Yarn binary to work in network-isolated CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100