Update pnpm to v7.33.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	7.11.0 -> 7.33.1

---

Release Notes

pnpm/pnpm

v7.33.1

Compare Source

Patch Changes

• When dedupe-peer-dependents is enabled, use the path (not id) to determine compatibility.

  When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication.

  Resolves: #​6605

• Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly.

Our Gold Sponsors

Our Silver Sponsors

v7.33.0

Compare Source

Minor Changes

• Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.

  A new field will now be present in the lockfile: settings. It will store the values of two settings: autoInstallPeers and excludeLinksFromLockfile. If someone tries to perform a frozen-lockfile installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.

  The lockfile format version is bumped from v6.0 to v6.1.

  Related PR: #​6557
  Related issue: #​6312

Patch Changes

• When updating dependencies, preserve the range prefix in aliased dependencies. So npm:foo@1.0.0 becomes npm:foo@1.1.0.
• Print a meaningful error when a project referenced by the workspace: protocol is not found in the workspace #​4477.
• Should respect ignore patterns in updateConfig.ignoreDependencies #​6548

Our Gold Sponsors

Our Silver Sponsors

v7.32.5

Compare Source

Patch Changes

• pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
• Expanded missing command error, including 'did you mean' #​6492.
• Normalize current working directory on Windows #​6524.
• Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

v7.32.4

Compare Source

Patch Changes

• pnpm link -g <pkg-name> should not modify the package.json file #​4341.
• Node.js range specified through the engines field should match prerelease versions #​6509.
• pnpm publish --otp should work #​6514.

Our Gold Sponsors

Our Silver Sponsors

v7.32.3

Compare Source

Patch Changes

• Link the bin files of local workspace dependencies, when node-linker is set to hoisted 6486.
• Show cyclic workspace dependency details #​5059.

Our Gold Sponsors

Our Silver Sponsors

v7.32.2

Compare Source

Patch Changes

• Patch node-fetch to fix an error that happens on Node.js 20 #​6424.

Our Gold Sponsors

Our Silver Sponsors

v7.32.1

Compare Source

Patch Changes

• Warn user when publishConfig.directory of an injected workspace dependency does not exist #​6396.
• Use hard links to link the node executable on Windows machines #​4315.

Our Gold Sponsors

Our Silver Sponsors

v7.32.0

Compare Source

Minor Changes

• Allow env variables to be specified with default values in .npmrc. This is a convention used by Yarn too.
  Using ${NAME-fallback} will return fallback if NAME isn't set. ${NAME:-fallback} will return fallback if NAME isn't set, or is an empty string #​6018.

Patch Changes

• pnpm config get <key> returns empty when the value is a boolean
• Don't print an info message about linked dependencies if they are real linked dependencies specified via the link: protocol in package.json.
• Add -g to mismatch registries error info when original command has -g option #​6224.

Our Gold Sponsors

Our Silver Sponsors

v7.31.0

Compare Source

Minor Changes

• Add ignore-workspace-cycles to silence workspace cycle warning #​6308.

Patch Changes

• Registries are now passed to the preResolution hook.
• Repeat installation should work on a project that has a dependency with () chars in the scope name #​6348.
• Should report error summary as expected.
• Update @yarnpkg/shell to fix issues in the shell emulator #​6320.
• Installation should not fail when there is a local dependency that starts in a directory that starts with the @ char #​6332.

Our Gold Sponsors

Our Silver Sponsors

v7.30.5

Compare Source

Patch Changes

• pnpm audit should work even if there are no package.json file, just a pnpm-lock.yaml file.
• Dedupe direct dependencies after hoisting.
• Don't remove automatically installed peer dependencies from the root workspace project, when dedupe-peer-dependents is true #​6154.

Our Gold Sponsors

Our Silver Sponsors

v7.30.4

Compare Source

v7.30.3

Compare Source

Patch Changes

• Should use most specific override rule when multiple rules match the same target #​6210.
• Fix regression introduced in v7.30.1 #​6271.

Our Gold Sponsors

Our Silver Sponsors

v7.30.2

Compare Source

v7.30.1

Compare Source

Patch Changes

• Don't write the pnpm-lock.yaml file if it has no changes and pnpm install --frozen-lockfile was executed #​6158.
• Fix git-hosted dependencies referenced via git+ssh that use semver selectors #​6239.
• When publish some package throws an error, the exit code should be non-zero #​5528.
• Only three paths are displayed in pnpm audit output #​6203
• Aliased packages should be used to resolve peer dependencies too #​4301.

Our Gold Sponsors

Our Silver Sponsors

v7.30.0

Compare Source

Minor Changes

• Allow to set a custom directory for storing patch files via the patches-dir setting #​6215

Patch Changes

• New directories should be prepended to NODE_PATH in command shims, not appended.
• Retry copying file on EBUSY error #​6201.

Our Gold Sponsors

Our Silver Sponsors

v7.29.3

Compare Source

Patch Changes

• Command shim should not set higher priority to the node_modules/.pnpm/node_modules directory through the NODE_PATH env variable, then the command's own node_modules directory #​5176.
• extend-node-path is set back to true by default. It was set to false in v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extending NODE_PATH. We have fixed the Jest issue with a different solution #​6213.

Our Gold Sponsors

Our Silver Sponsors

v7.29.2

Compare Source

v7.29.1

Compare Source

Patch Changes

• Settings related to authorization should be set/deleted by npm CLI #​6181.

Our Gold Sponsors

Our Silver Sponsors

v7.29.0

Compare Source

Minor Changes

• A new setting is now supported: dedupe-peer-dependents.

  When this setting is set to true, packages with peer dependencies will be deduplicated after peers resolution.

  For instance, let's say we have a workspace with two projects and both of them have webpack in their dependencies. webpack has esbuild in its optional peer dependencies, and one of the projects has esbuild in its dependencies. In this case, pnpm will link two instances of webpack to the node_modules/.pnpm directory: one with esbuild and another one without it:

  node_modules
    .pnpm
      webpack@1.0.0_esbuild@1.0.0
      webpack@1.0.0
  project1
    node_modules
      webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack
  project2
    node_modules
      webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
      esbuild
  

  This makes sense because webpack is used in two projects, and one of the projects doesn't have esbuild, so the two projects cannot share the same instance of webpack. However, this is not what most developers expect, especially since in a hoisted node_modules, there would only be one instance of webpack. Therefore, you may now use the dedupe-peer-dependents setting to deduplicate webpack when it has no conflicting peer dependencies (explanation at the end). In this case, if we set dedupe-peer-dependents to true, both projects will use the same webpack instance, which is the one that has esbuild resolved:

  node_modules
    .pnpm
      webpack@1.0.0_esbuild@1.0.0
  project1
    node_modules
      webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
  project2
    node_modules
      webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
      esbuild
  

  What are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:

  node_modules
    .pnpm
      webpack@1.0.0_react@16.0.0_esbuild@1.0.0
      webpack@1.0.0_react@17.0.0
  project1
    node_modules
      webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack
      react (v17)
  project2
    node_modules
      webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
      esbuild
      react (v16)
  

  In this case, we cannot dedupe webpack as webpack has react in its peer dependencies and react is resolved from two different versions in the context of the two projects.

Patch Changes

• The configuration added by pnpm setup should check if the pnpm home directory is already in the PATH before adding to the PATH.

  Before this change, this code was added to the shell:

  export PNPM_HOME="$HOME/Library/pnpm"
  export PATH="$PNPM_HOME:$PATH"

  Now this will be added:

  export PNPM_HOME="$HOME/Library/pnpm"
  case ":$PATH:" in
    *":$PNPM_HOME:"*) ;;
    *) export PATH="$PNPM_HOME:$PATH" ;;
  esac

• Add skipped status in exec report summary when script is missing #​6139.

• pnpm env -g should fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.

• Should not throw an error when local dependency use file protocol #​6115.

• Fix the incorrect error block when subproject has been patched #​6183

Our Gold Sponsors

Our Silver Sponsors

Mend Renovate. View repository job log here.