chore(deps): update all non-major dependencies

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	`^20.3.1` -> `^20.3.2`
pnpm (source)	`8.4.0` -> `8.6.5`

Release Notes

pnpm/pnpm (pnpm)

### [`v8.6.5`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.5) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.4...v8.6.5) #### Patch Changes - Improve the performance of searching for auth tokens [#6717](https://togithub.com/pnpm/pnpm/pull/6717). #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.6.4`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.4) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.3...v8.6.4) #### 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](https://togithub.com/pnpm/pnpm/issues/6588). - Ignore the port in the URL, while searching for authentication token in the `.npmrc` file [#6354](https://togithub.com/pnpm/pnpm/issues/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](https://togithub.com/pnpm/pnpm/pull/6695). #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.6.3`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.3) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.2...v8.6.3) #### Patch Changes - When running a script in multiple projects, the script outputs should preserve colours [#2148](https://togithub.com/pnpm/pnpm/issues/2148). - Don't crash when the `APPDATA` env variable is not set on Windows [#6659](https://togithub.com/pnpm/pnpm/issues/6659). - Don't fail when a package is archived in a tarball with malformed tar headers [#5362](https://togithub.com/pnpm/pnpm/issues/5362). - Peer dependencies of subdependencies should be installed, when `node-linker` is set to `hoisted` [#6680](https://togithub.com/pnpm/pnpm/pull/6680). - Throw a meaningful error when applying a patch to a dependency fails. - `pnpm update --global --latest` should work [#3779](https://togithub.com/pnpm/pnpm/issues/3779). - `pnpm license ls` should work even when there is a patched git protocol dependency [#6595](https://togithub.com/pnpm/pnpm/issues/6595) #### Our Gold Sponsors

#### Our Silver Sponsors

### [`v8.6.2`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.1...v8.6.2) #### Patch Changes - Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly [#6648](https://togithub.com/pnpm/pnpm/issues/6648) - When patching a dependency, only consider files specified in the 'files' field of its package.json. Ignore all others [#6565](https://togithub.com/pnpm/pnpm/issues/6565) - Should always treat local file dependency as new dependency [#5381](https://togithub.com/pnpm/pnpm/issues/5381) - Output a warning message when "pnpm" or "resolutions" are configured in a non-root workspace project [#6636](https://togithub.com/pnpm/pnpm/issues/6636) #### Our Gold Sponsors

#### Our Silver Sponsors

### [`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

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

unjs / consola

chore(deps): update all non-major dependencies #187

Release Notes

Configuration

Codecov Report