chore(deps): update pnpm to v7.33.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	7.1.5 -> 7.33.7

---

Release Notes

pnpm/pnpm (pnpm)

v7.33.7

Compare Source

Patch Changes

• Remove vulnerable "ip" package from the dependencies #​7652.

v7.33.6

Compare Source

Patch Changes

• Authorization token should be found in the configuration, when the requested URL is explicitly specified with a default port (443 on HTTPS or 80 on HTTP) #​6863.

Our Gold Sponsors

Our Silver Sponsors

v7.33.5

Compare Source

Patch Changes

• Temporarily revert the fix to #​6805 to fix the regression it caused #​6827.

Our Gold Sponsors

Our Silver Sponsors

v7.33.4

Compare Source

Patch Changes

• When the same file is appended multiple times into a tarball, the last occurrence is selected when unpacking the tarball.
• Added support for publishConfig.registry in package.json for publishing #​6775.
• Fixed a bug in which pnpm passed the wrong scheme to git ls-remote, causing a fallback to git+ssh and resulting in a 'host key verification failed' issue #​6805

Our Gold Sponsors

Our Silver Sponsors

v7.33.3

Compare Source

Patch Changes

• Improve the performance of searching for auth tokens.
• Installation of a git-hosted dependency without package.json should not fail, when the dependency is read from cache #​6721.
• Local workspace bin files that should be compiled first are linked to dependent projects after compilation #​1801.
• Prefer versions found in parent package dependencies only #​6737.

Our Gold Sponsors

Our Silver Sponsors

v7.33.2

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.
• 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.
• Ignore the port in the URL, while searching for authentication token in the .npmrc file #​6354.
• Throw a meaningful error when applying a patch to a dependency fails.
• pnpm update --global --latest should work #​3779.

Our Gold Sponsors

Our Silver Sponsors

v7.33.1

Compare Source

Patch Changes

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

• Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly.

Our Gold Sponsors

Our Silver Sponsors

v7.33.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

Patch Changes

• 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.
• Should respect ignore patterns in updateConfig.ignoreDependencies #​6548

Our Gold Sponsors

Our Silver Sponsors

v7.32.5

Compare Source

Patch Changes

• pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
• Expanded missing command error, including 'did you mean' #​6492.
• Normalize current working directory on Windows #​6524.
• Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

v7.32.4

Compare Source

Patch Changes

• pnpm link -g <pkg-name> should not modify the package.json file #​4341.
• Node.js range specified through the engines field should match prerelease versions #​6509.
• pnpm publish --otp should work #​6514.

Our Gold Sponsors

Our Silver Sponsors

v7.32.3

Compare Source

Patch Changes

• Link the bin files of local workspace dependencies, when node-linker is set to hoisted 6486.
• Show cyclic workspace dependency details #​5059.

Our Gold Sponsors

Our Silver Sponsors

v7.32.2

Compare Source

Patch Changes

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

Our Gold Sponsors

Our Silver Sponsors

v7.32.1

Compare Source

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

v7.32.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

• pnpm config get <key> returns empty when the value is a boolean
• Don't print an info message about linked dependencies if they are real linked dependencies specified via the link: protocol in package.json.
• Add -g to mismatch registries error info when original command has -g option #​6224.

Our Gold Sponsors

Our Silver Sponsors

v7.31.0

Compare Source

Minor Changes

• Add ignore-workspace-cycles to silence workspace cycle warning #​6308.

Patch Changes

• Registries are now passed to the preResolution hook.
• Repeat installation should work on a project that has a dependency with () chars in the scope name #​6348.
• Should report error summary as expected.
• Update @yarnpkg/shell to fix issues in the shell emulator #​6320.
• Installation should not fail when there is a local dependency that starts in a directory that starts with the @ char #​6332.

Our Gold Sponsors

Our Silver Sponsors

v7.30.5

Compare Source

Patch Changes

• pnpm audit should work even if there are no package.json file, just a pnpm-lock.yaml file.
• Dedupe direct dependencies after hoisting.
• Don't remove automatically installed peer dependencies from the root workspace project, when dedupe-peer-dependents is true #​6154.

Our Gold Sponsors

Our Silver Sponsors

v7.30.4

Compare Source

v7.30.3

Compare Source

Patch Changes

• Should use most specific override rule when multiple rules match the same target #​6210.
• Fix regression introduced in v7.30.1 #​6271.

Our Gold Sponsors

Our Silver Sponsors

v7.30.2

Compare Source

v7.30.1

Compare Source

Patch Changes

• Don't write the pnpm-lock.yaml file if it has no changes and pnpm install --frozen-lockfile was executed #​6158.
• Fix git-hosted dependencies referenced via git+ssh that use semver selectors #​6239.
• When publish some package throws an error, the exit code should be non-zero #​5528.
• Only three paths are displayed in pnpm audit output #​6203
• Aliased packages should be used to resolve peer dependencies too #​4301.

Our Gold Sponsors

---

Configuration

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

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
typed-vuex	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 15, 2024 4:33pm

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a16c245) 100.00% compared to head (d8aae79) 100.00%.

❗ Current head d8aae79 differs from pull request most recent head 88f25b3. Consider uploading reports for the commit 88f25b3 to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #309   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          117       117           
  Branches        28        28           
=========================================
  Hits           117       117           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

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?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.