chore(deps): update pnpm to v8 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	7.30.5 -> 8.6.5

---

Release Notes

pnpm/pnpm (pnpm)

v8.6.5

Compare Source

Patch Changes

• Improve the performance of searching for auth tokens #​6717.

Our Gold Sponsors

Our Silver Sponsors

v8.6.4

Compare Source

Patch Changes

• In cases where both aliased and non-aliased dependencies exist to the same package, non-aliased dependencies will be used for resolving peer dependencies, addressing issue #​6588.
• Ignore the port in the URL, while searching for authentication token in the .npmrc file #​6354.
• Don't add the version of a local directory dependency to the lockfile. This information is not used anywhere by pnpm and is only causing more Git conflicts #​6695.

Our Gold Sponsors

Our Silver Sponsors

v8.6.3

Compare Source

Patch Changes

• When running a script in multiple projects, the script outputs should preserve colours #​2148.
• Don't crash when the APPDATA env variable is not set on Windows #​6659.
• Don't fail when a package is archived in a tarball with malformed tar headers #​5362.
• Peer dependencies of subdependencies should be installed, when node-linker is set to hoisted #​6680.
• Throw a meaningful error when applying a patch to a dependency fails.
• pnpm update --global --latest should work #​3779.
• pnpm license ls should work even when there is a patched git protocol dependency #​6595

Our Gold Sponsors

Our Silver Sponsors

v8.6.2

Compare Source

Patch Changes

• Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly #​6648
• When patching a dependency, only consider files specified in the 'files' field of its package.json. Ignore all others #​6565
• Should always treat local file dependency as new dependency #​5381
• Output a warning message when "pnpm" or "resolutions" are configured in a non-root workspace project #​6636

Our Gold Sponsors

Our Silver Sponsors

v8.6.1

Compare Source

Patch Changes

• When dedupe-peer-dependents is enabled (default), 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

• Some minor performance improvements by removing await from loops #​6617.

Our Gold Sponsors

Our Silver Sponsors

v8.6.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

• A new setting, exclude-links-from-lockfile, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.

  This setting was primarily added for use by Bit CLI, which links core aspects to node_modules from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.

Patch Changes

• Don't print "Lockfile is up-to-date" message before finishing all the lockfile checks #​6544.
• When updating dependencies, preserve the range prefix in aliased dependencies. So npm:[email protected] becomes npm:[email protected].
• Print a meaningful error when a project referenced by the workspace: protocol is not found in the workspace #​4477.
• pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
• Peers resolution should not fail when a linked in dependency resolves a peer dependency.
• Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

v8.5.1

Compare Source

Patch Changes

• Expanded missing command error, including 'did you mean' #​6492.
• When installation fails because the lockfile is not up-to-date with the package.json file(s), print out what are the differences #​6536.
• Normalize current working directory on Windows #​6524.

Our Gold Sponsors

Our Silver Sponsors

v8.5.0

Compare Source

Minor Changes

• pnpm patch-remove command added #​6521.

Patch Changes

• pnpm link -g <pkg-name> should not modify the package.json file #​4341.
• The deploy command should not ask for confirmation to purge the node_modules directory #​6510.
• Show cyclic workspace dependency details #​5059.
• Node.js range specified through the engines field should match prerelease versions #​6509.

Our Gold Sponsors

Our Silver Sponsors

v8.4.0

Compare Source

Minor Changes

• pnpm publish supports the --provenance CLI option #​6435.

Patch Changes

• Link the bin files of local workspace dependencies, when node-linker is set to hoisted 6486.
• Ask the user to confirm the removal of node_modules directory unless the --force option is passed.
• Do not create a node_modules folder with a .modules.yaml file if there are no dependencies inside node_modules.

Our Gold Sponsors

Our Silver Sponsors

v8.3.1

Compare Source

Patch Changes

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

Our Gold Sponsors

Our Silver Sponsors

v8.3.0

Compare Source

Minor Changes

• A custom compression level may be specified for the pnpm pack command using the pack-gzip-level setting #​6393.
• Add --check flag to pnpm dedupe. No changes will be made to node_modules or the lockfile. Exits with a non-zero status code if changes are possible.
• pnpm install --resolution-only re-runs resolution to print out any peer dependency issues #​6411.

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

v8.2.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

• Add -g to mismatch registries error info when original command has -g option #​6224.
• Don't fail with EBUSY error when trying to copy a file from the store #​6201
• pnpm config get <key> should print boolean values #​6360
• Don't print an info message about linked dependencies if they are real linked dependencies specified via the link: protocol in package.json #​6372

Our Gold Sponsors

Our Silver Sponsors

Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

[10:39:38.197] INFO (9): Installing tool node v18.16.1...
[10:39:38.201] INFO (9): Preparing legacy tool node ...
installing v2 tool node v18.16.1
linking tool node v18.16.1
node: v18.16.1 /usr/local/bin/node
npm: 9.5.1  /usr/local/bin/npm
Installed v2 //usr/local/containerbase/tools/v2/node.sh in 2 seconds
[10:39:40.844] INFO (9): Installed tool node in 2647ms.
[10:39:40.952] INFO (141): Installing tool pnpm v8.6.5...
[10:39:40.955] INFO (141): Preparing legacy tool pnpm ...
installing v2 tool pnpm v8.6.5
linking tool pnpm v8.6.5
8.6.5
Installed v2 //usr/local/containerbase/tools/v2/pnpm.sh in 2 seconds
[10:39:42.283] INFO (141): Installed tool pnpm in 1331ms.
Scope: all 5 projects
undefined
/tmp/worker/657b4b/d38e00/repos/github/vitejs/vite-benchmark/cases/perf-2:
 ERR_PNPM_LINKED_PKG_DIR_NOT_FOUND  Could not install from "/tmp/worker/657b4b/d38e00/repos/github/vitejs/vite-benchmark/cases/vite" as it does not exist.

This error happened while installing a direct dependency of /tmp/worker/657b4b/d38e00/repos/github/vitejs/vite-benchmark/cases/perf-2
undefined