pnpm

Patch Changes

• Deduplicate bin names to prevent race condition and corrupted bin scripts #7833.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Minor Changes

• Added support for catalogs #8122.

  Catalogs may be declared in the pnpm-workspace.yaml file. For example:

  # Default catalogs
  catalog:
    chalk: ^4.1.2
  
  # Named catalogs
  catalogs:
    react16:
      react: ^16.7.0
      react-dom: ^16.7.0
    react17:
      react: ^17.10.0
      react-dom: ^17.10.0
  

  Then, in package.json files, use the catalog: protocol to reference a "default" or "named" catalog:

  {
    "dependencies": {
      "chalk": "catalog:",
      "react": "catalog:react16",
      "react-dom": "catalog:react16"
    }
  }
  

  Shout out to @gluxon for implementing it!

• Bundled pnpm setup now creates the pnpx script #8230.

Patch Changes

• Read authentication information from .npmrc in the current directory when running dlx #7996.
• Updated @pnpm/tabtab to v0.5.4, enabling zsh autocomplete lazy loading #8236.
• Installation with filtering will now work, when dedupe-peer-dependents is set to true #6300.
• Fixed dlx not actually using the Node.js version specified by --use-node-version.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Installation with filtering should work, when dedupe-peer-dependents is set to true #6300.
• Fix dlx not actually using node version specified by --use-node-version.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Minor Changes

• Added support for catalogs #8122.
• Bundled pnpm setup now creates pnpx script #8230.

Patch Changes

• Read authentication information from .npmrc in the current directory when running dlx #7996.
• update @pnpm/tabtab to v0.5.4, enabling zsh autocomplete lazy loading #8236.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Minor Changes

• Some registries allow the exact same content to be published under different package names and/or versions. This breaks the validity checks of packages in the store. To avoid errors when verifying the names and versions of such packages in the store, you may now set the strict-store-pkg-content-check setting to false #4724.

Patch Changes

• Fix package-manager-strict-version missing in config #8195.
• If install is performed on a subset of workspace projects, always create an up-to-date lockfile first. So, a partial install can be performed only on a fully resolved (non-partial) lockfile #8165.
• Handle workspace protocol with any semver range specifier, when used in peer dependencies #7578.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Minor Changes

• Semi-breaking. Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the peers-suffix-max-length setting #8177.

Patch Changes

• Set reporter-hide-prefix to true by default for pnpm exec. In order to show prefix, the user now has to explicitly set reporter-hide-prefix=false #8174.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Minor Changes

• If package-manager-strict-version is set to true, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field of package.json.

Patch Changes

• Update @yarnpkg/pnp to the latest version, fixing issue with node: imports #8161.
• Deduplicate bin names to prevent race condition and corrupted bin scripts #7833.
• pnpm doesn't fail if its version doesn't match the one specified in the "packageManager" field of package.json #8087.
• exec now also streams prefixed output when --recursive or --parallel is specified just as run does #8065.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Improved the performance of the resolution stage by changing how missing peer dependencies are detected #8144.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Fix a bug in which a dependency that is both optional for one package but non-optional for another is omitted when optional=false #8066.
• Clear resolution cache before starting peer dependencies resolution #8109.
• Reduce memory usage by peer dependencies resolution #8072.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Reduced memory usage during peer dependencies resolution #8084.
• Details in the pnpm licenses output are not misplaced anymore #8071.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Improve the performance of the peers resolution stage by utilizing more cache #8058.
• Overrides with link: now preserve absolute path #8053.
• Fix incorrect path when resolving relative file: overrides for workspace package #8053.
• Print a better error message when resolution-mode is set to time-based and the registry fails to return the "time" field in the package's metadata.
• Fix shell completion on MinGW-w64 environment.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Minor Changes

• New setting called virtual-store-dir-max-length added to modify the maximum allowed length of the directories inside node_modules/.pnpm. The default length is set to 120 characters. This setting is particularly useful on Windows, where there is a limit to the maximum length of a file path #7355.

Patch Changes

• A dependency is hoisted to resolve an optional peer dependency only if it satisfies the range provided for the optional peer dependency #8028.
• Details in the pnpm outdated output are wrapped correctly #8037.
• Fix Cannot read properties of undefined (reading 'missingPeersOfChildren') exception that happens on install #8041.
• Explicitly throw an error when user attempts to run publish or pack when bundledDependencies is set but node-linker isn't hoisted.
• pnpm update should not fail when there's an aliased local workspace dependency #7975.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Upgrade tar to v6.2.1 in the dependences #7939.
• If the script-shell option is configured to a .bat/.cmd file on Windows, pnpm will now error with ERR_PNPM_INVALID_SCRIPT_SHELL_WINDOWS. Newer versions of Node.js released in April 2024 do not support executing these files directly without behavior differences. If the script-shell option is necessary for your use-case, please set a .exe file instead.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Minor Changes

• New setting called virtual-store-dir-max-length added to modify the maximum allowed length of the directories inside node_modules/.pnpm. The default length is set to 120 characters. This setting is particularly useful on Windows, where there is a limit to the maximum length of a file path #7355.

Patch Changes

• A dependency is hoisted to resolve an optional peer dependency only if it satisfies the range provided for the optional peer dependency #8028.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Lockfiles that have git-hosted dependencies specified should be correctly converted to the new lockfile format #7990.
• Don't upgrade the lockfile format on pnpm install --frozen-lockfile #7991.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Lockfiles with local or git-hosted dependencies are now successfully converted to the new lockfile format #7955.
• Resolve peer dependencies correctly, when they have prerelease versions #7977.
• Fix aliased dependencies resolution on repeat install with existing lockfile, when the aliased dependency doesn't specify a version or range #7957.
• The lockfile should be saved in the new format even if it is up-to-date.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Fix aliased dependencies resolution on repeat install with existing lockfile #7957.
• The engines.pnpm field in the package.json files of dependencies should be ignored #7965.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• If the script-shell option is configured to a .bat/.cmd file on Windows, pnpm will now error with ERR_PNPM_INVALID_SCRIPT_SHELL_WINDOWS. Newer versions of Node.js released in April 2024 do not support executing these files directly without behavior differences. If the script-shell option is necessary for your use-case, please set a .exe file instead.
• Print a hint about the package-manager-strict setting, when pnpm doesn't match the version specified in the packageManager field in package.json.
• pnpm completion command should work in the standalone version of pnpm #7948.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• Fixed an issue where optional dependencies were not linked into the dependent's node_modules #7943.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

Patch Changes

• pnpm install --frozen-lockfile should work with lockfiles generated by pnpm v8, if they don't need updates #7934.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors