chore(deps): update pnpm to v9 - autoclosed

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`8.14.1` -> `9.8.0`

Release Notes

pnpm/pnpm (pnpm)

### [`v9.8.0`](https://togithub.com/pnpm/pnpm/compare/v9.7.1...v9.8.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.7.1...v9.8.0) ### [`v9.7.1`](https://togithub.com/pnpm/pnpm/compare/v9.7.0...v9.7.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.7.0...v9.7.1) ### [`v9.7.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.7.0): pnpm 9.7 [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.6.0...v9.7.0) #### Minor Changes - Added pnpm version management. If the `manage-package-manager-versions` setting is set to `true`, pnpm will switch to the version specified in the `packageManager` field of `package.json` [#8363](https://togithub.com/pnpm/pnpm/pull/8363). This is the same field used by Corepack. Example: ```json { "packageManager": "pnpm@9.3.0" } ``` - Added the ability to apply patch to all versions [#8337](https://togithub.com/pnpm/pnpm/pull/8337). If the key of `pnpm.patchedDependencies` is a package name without a version (e.g. `pkg`), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version of `pkg` installed, `pnpm patch pkg` and subsequent `pnpm patch-commit $edit_dir` will create an entry named `pkg` in `pnpm.patchedDependencies`. And pnpm will attempt to apply this patch to other versions of `pkg` in the future. - Change the default edit dir location when running `pnpm patch` from a temporary directory to `node_modules/.pnpm_patches/pkg[@version]` to allow the code editor to open the edit dir in the same file tree as the main project [#8379](https://togithub.com/pnpm/pnpm/issues/8379). - Substitute environment variables in config keys [#6679](https://togithub.com/pnpm/pnpm/issues/6679). #### Patch Changes - `pnpm install` should run `node-gyp rebuild` if the project has a `binding.gyp` file even if the project doesn't have an install script [#8293](https://togithub.com/pnpm/pnpm/issues/8293). - Print warnings to stderr [#8342](https://togithub.com/pnpm/pnpm/pull/8342). - Peer dependencies of optional peer dependencies should be automatically installed [#8323](https://togithub.com/pnpm/pnpm/issues/8323). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

### [`v9.6.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.6.0): pnpm 9.6 [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.5.0...v9.6.0) #### Minor Changes - Support specifying node version (via `pnpm.executionEnv.nodeVersion` in `package.json`) for running lifecycle scripts per each package in a workspace [#6720](https://togithub.com/pnpm/pnpm/issues/6720). - Overrides now support the [`catalogs:` protocol](https://pnpm.io/catalogs) [#8303](https://togithub.com/pnpm/pnpm/issues/8303). #### Patch Changes - The `pnpm deploy` command now supports the [`catalog:` protocol](https://pnpm.io/catalogs) [#8298](https://togithub.com/pnpm/pnpm/pull/8298). - The `pnpm outdated` command now supports the [`catalog:` protocol](https://pnpm.io/catalogs) [#8304](https://togithub.com/pnpm/pnpm/pull/8304). - Correct the error message when trying to run `pnpm patch` without `node_modules/.modules.yaml` [#8257](https://togithub.com/pnpm/pnpm/issues/8257). - Silent reporting fixed with the `pnpm exec` command [#7608](https://togithub.com/pnpm/pnpm/issues/7608). - Add registries information to the calculation of dlx cache hash [#8299](https://togithub.com/pnpm/pnpm/pull/8299). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

### [`v9.5.0`](https://togithub.com/pnpm/pnpm/compare/v9.5.0-beta.3...v9.5.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.4.0...v9.5.0) ### [`v9.4.0`](https://togithub.com/pnpm/pnpm/compare/v9.3.0...v9.4.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.3.0...v9.4.0) ### [`v9.3.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.3.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.2.0...v9.3.0) #### Minor Changes - **Semi-breaking.** Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the `peers-suffix-max-length` setting [#8177](https://togithub.com/pnpm/pnpm/pull/8177). #### Patch Changes - Set `reporter-hide-prefix` to `true` by default for `pnpm exec`. In order to show prefix, the user now has to explicitly set `reporter-hide-prefix=false` [#8174](https://togithub.com/pnpm/pnpm/issues/8174). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

### [`v9.2.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.2.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.1.4...v9.2.0) #### Minor Changes - If `package-manager-strict-version` is set to `true`, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field of `package.json`. #### Patch Changes - Update `@yarnpkg/pnp` to the latest version, fixing issue with `node:` imports [#8161](https://togithub.com/pnpm/pnpm/issues/8161). - Deduplicate bin names to prevent race condition and corrupted bin scripts [#7833](https://togithub.com/pnpm/pnpm/issues/7833). - pnpm doesn't fail if its version doesn't match the one specified in the "packageManager" field of `package.json` [#8087](https://togithub.com/pnpm/pnpm/issues/8087). - `exec` now also streams prefixed output when `--recursive` or `--parallel` is specified just as `run` does [#8065](https://togithub.com/pnpm/pnpm/issues/8065). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

### [`v9.1.4`](https://togithub.com/pnpm/pnpm/compare/v9.1.3...v9.1.4) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.1.3...v9.1.4) ### [`v9.1.3`](https://togithub.com/pnpm/pnpm/compare/v9.1.2...v9.1.3) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.1.2...v9.1.3) ### [`v9.1.2`](https://togithub.com/pnpm/pnpm/releases/tag/v9.1.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.1.1...v9.1.2) #### Patch Changes - Reduced memory usage during peer dependencies resolution [#8084](https://togithub.com/pnpm/pnpm/pull/8084). - Details in the `pnpm licenses` output are not misplaced anymore [#8071](https://togithub.com/pnpm/pnpm/pull/8071). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

### [`v9.1.1`](https://togithub.com/pnpm/pnpm/compare/v9.1.0...v9.1.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.1.0...v9.1.1) ### [`v9.1.0`](https://togithub.com/pnpm/pnpm/compare/v9.1.0-0...v9.1.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.6...v9.1.0) ### [`v9.0.6`](https://togithub.com/pnpm/pnpm/compare/v9.0.5...v9.0.6) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.5...v9.0.6) ### [`v9.0.5`](https://togithub.com/pnpm/pnpm/compare/v9.0.4...v9.0.5) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.4...v9.0.5) ### [`v9.0.4`](https://togithub.com/pnpm/pnpm/compare/v9.0.3...v9.0.4) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.3...v9.0.4) ### [`v9.0.3`](https://togithub.com/pnpm/pnpm/compare/v9.0.2...v9.0.3) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.2...v9.0.3) ### [`v9.0.2`](https://togithub.com/pnpm/pnpm/compare/v9.0.1...v9.0.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.1...v9.0.2) ### [`v9.0.1`](https://togithub.com/pnpm/pnpm/compare/v9.0.0...v9.0.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.0.0...v9.0.1) ### [`v9.0.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.0.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.15.9...v9.0.0) ##### 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](https://pnpm.io/installation#using-a-standalone-script) or install the `@pnpm/exe` package. - Configuration updates: - [`dedupe-injected-deps`](https://pnpm.io/npmrc#dedupe-injected-deps): enabled by default. - [`link-workspace-packages`](https://pnpm.io/npmrc#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](https://pnpm.io/workspaces#workspace-protocol-workspace). - [`hoist-workspace-packages`](https://pnpm.io/npmrc#hoist-workspace-packages): enabled by default. - [`enable-pre-post-scripts`](https://pnpm.io/cli/run#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](https://togithub.com/pnpm/pnpm/pull/7470). - Dependency resolution changes: - Correct resolution of peer dependencies that have their own peer dependencies. Related issue: [#7444](https://togithub.com/pnpm/pnpm/issues/7444). Related PR: [#7606](https://togithub.com/pnpm/pnpm/pull/7606). - Optional peer dependencies may be resolved from any packages in the dependency graph [#7830](https://togithub.com/pnpm/pnpm/pull/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](https://togithub.com/pnpm/pnpm/pull/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](https://togithub.com/pnpm/pnpm/issues/3083). - When installing git-hosted dependencies, only pick the files that would be packed with the package [#7638](https://togithub.com/pnpm/pnpm/pull/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](https://togithub.com/pnpm/pnpm/issues/4765). Related PR: [#7487](https://togithub.com/pnpm/pnpm/pull/7487). - `node-gyp` updated to version 10. - PowerShell completion support added [#7597](https://togithub.com/pnpm/pnpm/pull/7597). - Support `node-options` option inside `.npmrc` file when running scripts [#7596](https://togithub.com/pnpm/pnpm/issues/7596). - Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported: `:certfile`, `:keyfile`, and `: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](https://togithub.com/pnpm/pnpm/issues/7427). Related PR: [#7626](https://togithub.com/pnpm/pnpm/pull/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](https://togithub.com/pnpm/pnpm/pull/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](https://togithub.com/pnpm/pnpm/pull/7662). - Added cache for `pnpm dlx` [#5277](https://togithub.com/pnpm/pnpm/issues/5277). ##### Patch Changes - Package tarballs are not downloaded during `--lockfile-only` installation [#1328](https://togithub.com/pnpm/pnpm/issues/1328). - Peer dependency rules should only affect reporting, not data in the lockfile [#7758](https://togithub.com/pnpm/pnpm/pull/7758). - Link overrides should be able to use absolute path [#7749](https://togithub.com/pnpm/pnpm/pull/7749). - `pnpm dlx` should not read settings from the current working directory [#7916](https://togithub.com/pnpm/pnpm/pull/7916). ##### Platinum Sponsors

##### Gold Sponsors

##### Our Silver Sponsors

### [`v8.15.9`](https://togithub.com/pnpm/pnpm/releases/tag/v8.15.9): pnpm 8.15.9 [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.15.8...v8.15.9) #### Patch Changes - Deduplicate bin names to prevent race condition and corrupted bin scripts [#7833](https://togithub.com/pnpm/pnpm/issues/7833). #### Platinum Sponsors

#### Gold Sponsors

This PR was generated by Mend Renovate. View the repository job log.

coderabbitai[bot] commented 6 months ago

[!WARNING]

Rate limit exceeded

@renovate[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 28 seconds before requesting another review.

How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.

Commits
Files that changed from the base of the PR and between d22beef57bb653c56840a519507e84d2614d4afd and 070751293c73cb979ffd20b6443ebba711e87ba2.

Walkthrough

The update involves changing the version of the pnpm package manager in the package.json file from 8.14.1 to 9.7.1. This upgrade signifies an improvement in the package management system, potentially offering better performance, new features, and fixes. The overall structure of the package.json remains intact, ensuring other configurations are preserved while enhancing the application's development and build processes.

Changes

File	Change Summary
`package.json`	Updated `packageManager` from `pnpm@8.14.1` to `pnpm@9.7.1`

Poem

🐇 In the garden where the code does bloom,
A little rabbit hops, dispelling gloom.
With pnpm now bright and new,
Faster builds and features too!
Let's celebrate this version's light,
A leap for joy, everything feels right! 🌼✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

uni-helper / vitesse-uni-app