chore(deps): update pnpm to v8.6.1

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`8.1.1` -> `8.6.1`

Release Notes

pnpm/pnpm

### [`v8.6.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.0...v8.6.1) #### 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](https://togithub.com/pnpm/pnpm/issues/6605) - Some minor performance improvements by removing await from loops [#6617](https://togithub.com/pnpm/pnpm/pull/6617). #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.6.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.5.1...v8.6.0) #### 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](https://togithub.com/pnpm/pnpm/pull/6557) Related issue: [#6312](https://togithub.com/pnpm/pnpm/issues/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](https://togithub.com/teambit/bit), 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](https://togithub.com/pnpm/pnpm/issues/6544). - 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](https://togithub.com/pnpm/pnpm/issues/4477). - `pnpm rebuild` should not fail when `node-linker` is set to `hoisted` and there are skipped optional dependencies [#6553](https://togithub.com/pnpm/pnpm/pull/6553). - Peers resolution should not fail when a linked in dependency resolves a peer dependency. - Build projects in a workspace in correct order [#6568](https://togithub.com/pnpm/pnpm/pull/6568). #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.5.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.5.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.5.0...v8.5.1) #### Patch Changes - Expanded missing command error, including 'did you mean' [#6492](https://togithub.com/pnpm/pnpm/issues/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](https://togithub.com/pnpm/pnpm/pull/6536). - Normalize current working directory on Windows [#6524](https://togithub.com/pnpm/pnpm/issues/6524). #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.5.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.5.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.4.0...v8.5.0) #### Minor Changes - `pnpm patch-remove` command added [#6521](https://togithub.com/pnpm/pnpm/pull/6521). #### Patch Changes - `pnpm link -g ` should not modify the `package.json` file [#4341](https://togithub.com/pnpm/pnpm/issues/4341). - The deploy command should not ask for confirmation to purge the `node_modules` directory [#6510](https://togithub.com/pnpm/pnpm/issues/6510). - Show cyclic workspace dependency details [#5059](https://togithub.com/pnpm/pnpm/issues/5059). - Node.js range specified through the `engines` field should match prerelease versions [#6509](https://togithub.com/pnpm/pnpm/pull/6509). #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.4.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.4.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.3.1...v8.4.0) #### Minor Changes - `pnpm publish` supports the `--provenance` CLI option [#6435](https://togithub.com/pnpm/pnpm/issues/6435). #### Patch Changes - Link the bin files of local workspace dependencies, when `node-linker` is set to `hoisted` [6486](https://togithub.com/pnpm/pnpm/issues/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`](https://togithub.com/pnpm/pnpm/releases/tag/v8.3.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.3.0...v8.3.1) #### Patch Changes - Patch `node-fetch` to fix an error that happens on Node.js 20 [#6424](https://togithub.com/pnpm/pnpm/issues/6424). #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.3.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.3.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.2.0...v8.3.0) #### Minor Changes - A custom compression level may be specified for the `pnpm pack` command using the `pack-gzip-level` setting [#6393](https://togithub.com/pnpm/pnpm/issues/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](https://togithub.com/pnpm/pnpm/pull/6411). #### Patch Changes - Warn user when `publishConfig.directory` of an injected workspace dependency does not exist [#6396](https://togithub.com/pnpm/pnpm/pull/6396). - Use hard links to link the node executable on Windows machines [#4315](https://togithub.com/pnpm/pnpm/issues/4315). #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.2.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.2.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.1.1...v8.2.0) #### 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](https://togithub.com/pnpm/pnpm/issues/6018). #### Patch Changes - Add `-g` to mismatch registries error info when original command has `-g` option [#6224](https://togithub.com/pnpm/pnpm/issues/6224). - Don't fail with EBUSY error when trying to copy a file from the store [#6201](https://togithub.com/pnpm/pnpm/issues/6201) - `pnpm config get ` should print boolean values [#6360](https://togithub.com/pnpm/pnpm/issues/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](https://togithub.com/pnpm/pnpm/issues/6372) #### Our Gold Sponsors

#### Our Silver Sponsors

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

hairyf / markdown-it-vitepress-demo

chore(deps): update pnpm to v8.6.1 #5

Release Notes

Configuration