You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fffa2f4
Browse filesBrowse the repository at this point in the historyBrowse files
committed
fix(pm): verify and content-key managed package-manager installs
Verify a downloaded managed package manager (pnpm, Yarn 2+, bun, and native
pnpm 12+) against the integrity the project declares in its `packageManager`
field -- or, for the pnpm global setup bootstraps, against the hash the CLI
carries -- rather than the integrity the registry reports. Cache a verified
install in a content-addressed directory keyed by that pin (and, for a
platform-binary manager, the registry origin), under a hidden `.verified-v1`
namespace that only a verified download writes to; an unpinned install stays at
the version-directory root. A different pin resolves to a different, verified
directory.
- Reuse a complete keyed directory without re-reading the pin; a different pin
triggers a fresh, verified download. A complete install is never replaced.
- Skip link entries when extracting package-manager archives, as npm does, so a
tarball writes only regular files into its own install directory.
- Keep the Windows `.cmd` fallback on the shim's cached fast path.
- `vp env which`/`current`/`doctor`/`list`/`clean`/`uninstall` understand both
the unpinned version-directory root and the verified namespace.
Co-Authored-By: arkmarta <arkadiuszmarta@proton.me>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/command_self_setup_external/snapshots/command_self_setup_homebrew_user_dependencies.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Cached Node, package managers, and global tools run without CLI dependency repai
14
14
CLI aliases, explicit installers, and unconfigured shims still prepare CLI dependencies.
15
15
User installations and cleanup stay independent.
16
16
Relative, tilde, and environment-variable selectors reach pnpm as the same absolute user config.
17
-
Registry overrides and basic authentication work with the shared downloader.
17
+
Registry overrides and basic authentication reach the shared downloader.
18
18
After authentication failure, diagnostics, upgrade guidance, and cleanup remain available.
19
19
Missing authentication and corrupted pnpm tarballs stop setup.
Copy file name to clipboardExpand all lines: crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/download_progress/snapshots/installation_progress_failure.md
-10Lines changed: 0 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,6 @@
2
2
3
3
## `node install.mjs interactive failure`
4
4
5
-
**→ expect-milestone:**`install:download:ready`
6
-
7
-
```
8
-
Before installation: preserve this output.
9
-
info: installing vite-plus@<version>...
10
-
⠿ Downloading pnpm <version>... <size> B (<size> B/s)
Copy file name to clipboardExpand all lines: crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/download_progress/snapshots/installation_progress_interactive.md
-10Lines changed: 0 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,6 @@
2
2
3
3
## `node install.mjs interactive`
4
4
5
-
**→ expect-milestone:**`install:download:ready`
6
-
7
-
```
8
-
Before installation: preserve this output.
9
-
info: installing vite-plus@<version>...
10
-
⠿ Downloading pnpm <version>... <size> B (<size> B/s)
0 commit comments