v10.18.3
📦 pnpmView on GitHub →
🐛 9 fixes🔧 4 symbols
Summary
This patch release fixes several bugs related to configuration handling, publishing, bin linking, and workspace behavior, improving the stability of pnpm commands.
🐛 Bug Fixes
- Fixed infinite recursion in pnpm when using `verifyDepsBeforeInstall: install` and pre/post install scripts that call other pnpm scripts (issue #10060).
- Fixed parsing of scoped registry keys (e.g., `@scope:registry`) as property paths in `pnpm config get` when `--location=project` is used (issue #9362).
- Removed pnpm-specific CLI options before passing to npm publish to prevent "Unknown cli config" warnings (issue #9646).
- Fixed EISDIR error when the bin field points to a directory (issue #9441).
- Preserved version and hasBin for variations packages (issue #10022).
- Fixed `pnpm config set --location=project` incorrectly handling keys with slashes (auth tokens, registry settings) (issue #9884).
- When both `pnpm-workspace.yaml` and `.npmrc` exist, `pnpm config set --location=project` now writes to `pnpm-workspace.yaml` (matching read priority) (issue #10072).
- Prevented a table width error in `pnpm outdated --long` (issue #10040).
- Synchronized bin links after injected dependencies are updated by build scripts, ensuring binaries created during build processes are properly linked and accessible (issue #10057).
🔧 Affected Symbols
pnpm configpnpm outdatedpnpm publishpnpm install