Consider unifying cache verification for modern Yarn
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, node.js, rust
Research direction
Start by reading the package manager cache and integrity verification code, then inspect the existing Yarn 2+ handling and the tests added for #2227. Define how a shared verification record would interact with Corepack-style pins and network access, while preserving verification of the extracted bin/yarn.js. Done means missing or mismatched records trigger download, verification, and replacement, with tests covering existing valid Yarn pins.
Written by the indexing model from the issue text.
Description
Vite+ no longer depends on Corepack, but it still supports integrity pins that Corepack writes to the packageManager field.
For Yarn 2 and later, these pins cover bin/yarn.js, not the npm tarball. Changing the hash target would break existing valid pins, as previously reported in #2209 and fixed in #2227.
Could we use a common cache verification policy for all package managers? When the verification record is missing or differs from the requested pin, Vite+ would download, verify, and replace the installation instead of rehashing the cached Yarn CLI.
Modern Yarn would still verify the extracted bin/yarn.js to preserve existing pin compatibility. This would require network access in cases where local verification currently works.
- Dominant language
- Rust
- Stars
- 6.3k
- Forks
- 283
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 230
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from voidzero-dev/vite-plus
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voidzero-dev/vite-plus#2882 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
voidzero-dev/vite-plus#2097 · 10 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
Support external `vp-<command>` executables, as Git and Cargo doPossibly taken @cpojer claimed this 1 day ago. Openenhancement pending triage
voidzero-dev/vite-plus#3195 · 1 assignee ·
Maintainers usually reply within 1 day
-
vp migrate doesn't flag esbuild-specific config (minify: "esbuild") — migrated project fails to build on Vite 8Possibly taken @john-okeefe claimed this 1 day ago. Opencontribution welcome
voidzero-dev/vite-plus#3176 · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
-
`vp run`: scripts get a non-blocking stdin (EAGAIN) when `run` tasks in vite.config.ts use constantsPossibly taken @wan9chi claimed this 1 day ago. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
voidzero-dev/vite-plus#3155 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in voidzero-dev/vite-plus
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
foxglove/mcap#1907 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
good first issue help wanted r-feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
servo/rust-smallvec#792 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day