chore(deps): update pnpm to v9 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	8.15.7 -> 9.0.6

---

Release Notes

pnpm/pnpm (pnpm)

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

v9.0.1

Compare Source

v9.0.0

Compare Source

Major Changes

• Node.js v16 support discontinued

  If you still require Node.js 16, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the @pnpm/exe package.

• Configuration updates:

  • dedupe-injected-deps: enabled by default.
  • link-workspace-packages: disabled by default. This means that by default, dependencies will be linked from workspace packages only when they are specified using the workspace protocol.
  • hoist-workspace-packages: enabled by default.
  • enable-pre-post-scripts: enabled by default.
  • Use the same directory for state files on macOS as on Linux (~/.local/state/pnpm).
  • pnpm will now check the package.json file for a packageManager field. If this field is present and specifies a different package manager or a different version of pnpm than the one you're currently using, pnpm will not proceed. This ensures that you're always using the correct package manager and version that the project requires.

• Lockfile changes:

  • Lockfile v9 is adopted. This new format has changes for better readability, and better resistence to Git conflicts.
  • Support for lockfile v5 is dropped. Use pnpm v8 to convert lockfile v5 to lockfile v6 #​7470.

• Dependency resolution changes:

  • Correct resolution of peer dependencies that have their own peer dependencies.
    Related issue: #​7444.
    Related PR: #​7606.
  • Optional peer dependencies may be resolved from any packages in the dependency graph #​7830.

• pnpm licenses list prints license information of all versions of the same package in case different versions use different licenses. The format of the pnpm licenses list --json output has been changed #​7528.

• A new command added for printing completion code to the console: pnpm completion [shell]. The old command that modified the user's shell dotfiles has been removed #​3083.

• When installing git-hosted dependencies, only pick the files that would be packed with the package #​7638.

Minor Changes

• It is now possible to install only a subdirectory from a Git repository.

  For example, pnpm add github:user/repo#path:packages/foo will add a dependency from the packages/foo subdirectory.

  This new parameter may be combined with other supported parameters separated by &. For instance, the next command will install the same package from the dev branch: pnpm add github:user/repo#dev&path:packages/bar.

  Related issue: #​4765.
  Related PR: #​7487.

• node-gyp updated to version 10.

• PowerShell completion support added #​7597.

• Support node-options option inside .npmrc file when running scripts #​7596.

• Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported: <registryURL>:certfile, <registryURL>:keyfile, and <registryURL>:ca. For instance:

  //registry.mycomp.com/:certfile=server-cert.pem
  //registry.mycomp.com/:keyfile=server-key.pem
  //registry.mycomp.com/:cafile=client-cert.pem
  

  Related issue: #​7427.
  Related PR: #​7626.

• Add a field named ignoredOptionalDependencies. This is an array of strings. If an optional dependency has its name included in this array, it will be skipped #​7714.

• The checksum of the .pnpmfile.cjs is saved into the lockfile. If the pnpmfile gets modified, the lockfile is reanalyzed to apply the changes #​7662.

• Added cache for pnpm dlx #​5277.

Patch Changes

• Package tarballs are not downloaded during --lockfile-only installation #​1328.
• Peer dependency rules should only affect reporting, not data in the lockfile #​7758.
• Link overrides should be able to use absolute path #​7749.
• pnpm dlx should not read settings from the current working directory #​7916.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

[cloudflare-pages]

Deploying unplugin-vue-router with    Cloudflare Pages

Latest commit:	9d7b37e
Status:	✅  Deploy successful!
Preview URL:	https://ad625d2c.unplugin-vue-router.pages.dev
Branch Preview URL:	https://renovate-pnpm-9-x.unplugin-vue-router.pages.dev

View logs

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@tanstack/vue-query@5.32.0	environment Transitive: filesystem	+4	2.94 MB	tannerlinsley
npm/@vue/compiler-sfc@3.4.24	environment, eval, filesystem, unsafe	+11	4.9 MB	yyx990803
npm/prettier@3.2.5	environment, filesystem, unsafe	0	8.39 MB	prettier-bot
npm/rimraf@5.0.5	environment, filesystem Transitive: shell	+12	1.65 MB	isaacs
npm/rollup@4.16.4	environment, filesystem	+18	46.9 MB	lukastaegert
npm/scule@1.3.0	None	0	29.6 kB	pi0
npm/semver@7.6.0	None	+1	552 kB	npm-cli-ops
npm/ts-expect@1.3.0	None	0	29.9 kB	blakeembrey
npm/tsup@8.0.2	environment, eval, filesystem Transitive: shell, unsafe	+11	1.83 MB	egoist
npm/typescript@5.4.5	None	0	32.4 MB	typescript-bot
npm/unplugin-auto-import@0.17.5	filesystem Transitive: environment	+4	1.04 MB	antfu
npm/unplugin-vue-markdown@0.26.2	unsafe	0	96.7 kB	antfu
npm/unplugin@1.10.1	filesystem	+2	798 kB	antfu
npm/vite@5.2.10	environment, eval, filesystem, network, shell, unsafe	+5	4.11 MB	vitebot
npm/vitepress@1.1.3	filesystem, network, shell, unsafe Transitive: environment	+5	10.8 MB	brc-dd
npm/vitest@1.5.0	environment, eval	+13	2.23 MB	vitestbot
npm/vue-router-mock@1.1.0	None	0	36.3 kB	posva
npm/vue-router@4.3.2	environment	0	802 kB	posva
npm/vue-tsc@2.0.14	None	0	4.94 kB	johnsoncodehk
npm/vue@3.4.24	environment, eval	+5	4.05 MB	yyx990803
npm/vuefire@3.1.23	environment Transitive: filesystem	+1	242 kB	posva
npm/webpack@5.91.0	environment, filesystem, network, unsafe Transitive: eval	+10	6.09 MB	evilebottnawi
npm/yaml@2.4.1	environment	0	671 kB	eemeli
npm/yorkie@2.0.0	environment, filesystem	+1	30.8 kB	yyx990803

🚮 Removed packages: npm/json-server@0.17.4, npm/mande@2.0.8, npm/nuxt@3.10.2

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/yorkie@2.0.0	Install script: install Source: node bin/install.js	package.json pnpm-lock.yaml
Install scripts	npm/protobufjs@7.2.6	Install script: postinstall Source: node scripts/postinstall	package.json pnpm-lock.yaml
Install scripts	npm/vue-demi@0.14.7	Install script: postinstall Source: node -e "try{require('./scripts/postinstall.js')}catch(e){}"	package.json playground/package.json pnpm-lock.yaml

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/yorkie@2.0.0
• @SocketSecurity ignore npm/protobufjs@7.2.6
• @SocketSecurity ignore npm/vue-demi@0.14.7