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 8ad90d4
Browse filesBrowse the repository at this point in the historyBrowse files
Give pnpm installs pnpm upgrade commands (#1111) (#1350)
* Route pnpm installs to pnpm upgrade commands (WIP)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Give pnpm installs pnpm upgrade commands
socket-patch --update and the update notice treated every node_modules
install as npm. A pnpm global install was told to run npm update -g,
which never sees pnpm's store, and a pnpm project was told to run
npm install, which writes a stray package-lock.json and breaks the
next pnpm install --frozen-lockfile.
pnpm installs are now recognized by the .pnpm virtual store in the
binary's path, a pnpm home above a global store, or pnpm-lock.yaml
beside node_modules. They are labelled "managed by pnpm" and given
pnpm add -g ...@latest (global), pnpm add ...@latest (project) or
pnpm update --recursive --latest ... (workspace root). vlt installs
are now labelled vlt.
Fixes#1111
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: crates/socket-patch-cli/CLI_CONTRACT.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
@@ -1013,7 +1013,7 @@ Honored global flags: `--json`, `--silent` (errors only), `--yes` (skip the conf
1013
1013
1014
1014
| Detected channel | Hint |
1015
1015
|---|---|
1016
-
| npm (`node_modules` path component) | project-local (the directory holding the outermost `node_modules` has a `package.json`, and it is not directly under `lib`/`npm` or below a yarn/pnpm `global` store): `npm install @socketsecurity/socket-patch@latest`, or `vlt install @socketsecurity/socket-patch@latest` when that directory holds `vlt-lock.json`, or `vlx -y -- @socketsecurity/socket-patch@latest …` when its `package.json` is vlx's (`"name": "vlx"`, the vlx cache); otherwise global (including version-manager prefixes such as nvm-windows and fnm): `npm update -g @socketsecurity/socket-patch` |
1016
+
| npm family (`node_modules` path component) | The refusal names the owning manager (`managed by npm` / `pnpm` / `vlt`). **pnpm** (a `.pnpm` virtual-store component in the path, a `pnpm` home above a `global` store, or `pnpm-lock.yaml` beside the outermost `node_modules`): global store: `pnpm add -g @socketsecurity/socket-patch@latest`; project: `pnpm add @socketsecurity/socket-patch@latest`, or `pnpm update --recursive --latest @socketsecurity/socket-patch` when that directory holds `pnpm-workspace.yaml`. **npm / vlt** project-local (the directory holding the outermost `node_modules` has a `package.json`, and it is not directly under `lib`/`npm` or below a yarn/pnpm `global` store): `npm install @socketsecurity/socket-patch@latest`, or `vlt install @socketsecurity/socket-patch@latest` when that directory holds `vlt-lock.json`, or `vlx -y -- @socketsecurity/socket-patch@latest …` when its `package.json` is vlx's (`"name": "vlx"`, the vlx cache); otherwise global (including a yarn `global` store and version-manager prefixes such as nvm-windows and fnm): `npm update -g @socketsecurity/socket-patch` |
1017
1017
| Legacy PyPI wheel (`site-packages`/`dist-packages`) | `pip uninstall socket-patch` followed by the standalone installer (macOS/Linux) or `npm install -g @socketsecurity/socket-patch` (Windows) |
0 commit comments