mirror/pnpm

0 Fork 0

mirror of https://github.com/pnpm/pnpm.git synced 2026-10-28 10:38:23 -04:00

Files

T

Zoltan Kochan ff295f3904 fix(config): make --global and --location=global read only the global config (#16601 )

`pnpm config get --global` and `pnpm config list --global` printed the
settings from the project's pnpm-workspace.yaml when run inside a
project, and `--global` and `--location=global` disagreed on what the
global config is, although the docs call them the same.

pnpm v12: `ConfigFlags::is_global` resolves both flags in one place,
with `--location` winning. A `get`/`list` scoped that way loads config
the way other global commands do, anchored at the pnpm home, so neither
the project's pnpm-workspace.yaml nor its .npmrc applies. The
pre-command pin checks and the `-w` conflict check use the same helper.
A global config read also implies --ignore-workspace, so
PNPM_CONFIG_WORKSPACE_DIR does not bring a workspace back in.

pnpm v11: config commands turn `--global` into `--location=global`
before loading config, so `--global` no longer loads the config of a
global install. That mode required the global bin directory in PATH and
read the global packages' pnpm-workspace.yaml. The CLI parser lets
`--location` win over `--global` when looking for the workspace.

Both now skip the project .npmrc for these reads, as npm does in global
mode. A new `ignoreProjectNpmrc` getConfig option does it in v11; other
v11 global commands are unchanged.

Closes pnpm/pnpm#16598

2026-10-05 16:20:00 +02:00

src

fix(config): make --global and --location=global read only the global config (#16601 )

2026-10-05 16:20:00 +02:00

test

fix(config): make --global and --location=global read only the global config (#16601 )

2026-10-05 16:20:00 +02:00

package.json

chore(release): 11.28.1, pacquet 12.8.0, pnpr 0.1.0-alpha.14 (#16312 )

2026-09-28 08:57:31 +02:00

README.md

refactor: move the TypeScript pnpm CLI into a pnpm11/ directory (#12537 )