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 34f13e0
Browse filesBrowse the repository at this point in the historyBrowse files
Fix yarn 1.0.x global packages being missed (#437) (#1798)
* Start fix for #437
Assisted-by: Claude Code:claude-opus-5-5
* Find yarn 1.0.x global packages
Yarn 1.0.0 to 1.0.2 has no `yarn global dir` command, so global scans
(`scan -g`, `get -g`, `rollback -g`, `vex -g`) found none of the
packages installed with `yarn global add` and still reported success.
When `yarn global dir` gives no answer and `yarn --version` reports
1.0.x, the global folder yarn 1.0.x itself uses is crawled instead:
~/.config/yarn/global (/usr/local/share/.config/yarn/global for root),
or %LOCALAPPDATA%\Yarn\config\global on Windows. Newer yarn releases
and machines without yarn behave as before.
Fixes#437
Assisted-by: Claude Code:claude-opus-5-5
* Prefer a configured yarn 1.0.x global folder
Yarn 1.0.x also reads `--global-folder` from .yarnrc, so a configured
global folder that exists is crawled before the default one. The
`yarn --version` probe now runs only when one of those folders exists,
so a Yarn Berry machine (no `yarn global` at all) doesn't pay for a
second yarn process on every global scan.
Assisted-by: Claude Code:claude-opus-5-5
* Read yarn 1.0.x config from the probe dir
The yarn 1.0.x fallback read global-folder settings from the current
project, so a project .yarnrc naming an existing folder could pass a
project directory off as the machine-wide yarn install. It now reads
yarn's config from the same neutral directory the `yarn global dir`
probe runs in.
Assisted-by: Claude Code:claude-opus-5-5
---------
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments