chore(deps): update pnpm to v8.15.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	8.10.2 -> 8.15.2

---

Release Notes

pnpm/pnpm (pnpm)

v8.15.2

Compare Source

Patch Changes

• When purging multiple node_modules directories, pnpm will no longer print multiple prompts simultaneously.
• Don't print an unnecessary warning when adding new dependencies to a project that uses hoisted node_modules.
• Linking globally the command of a package that has no name in package.json #​4761.
• Installation should work with lockfile created by pnpm v9.0.0-alpha.4

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.1

Compare Source

Patch Changes

• Use the object-hash library instead of node-object-hash for hashing keys of side-effects cache #​7591.
• bundledDependencies should never be added to the lockfile with false as the value #​7576.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.0

Compare Source

Minor Changes

• When the license field does not exist in package.json but a license file exists, try to match and extract the license name #​7530.

Patch Changes

• Running pnpm update -r --latest will no longer downgrade prerelease dependencies #​7436.
• --aggregate-output should work on scripts executed from the same project #​7556.
• Prefer hard links over reflinks on Windows as they perform better #​7564.
• Reduce the length of the side-effects cache key. Instead of saving a stringified object composed from the dependency versions of the package, use the hash calculated from the said object #​7563.
• Throw an error if pnpm update --latest runs with arguments containing versions specs. For instance, pnpm update --latest foo@next is not allowed #​7567.
• Don't fail in Windows CoW if the file already exists #​7554.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.3

Compare Source

Patch Changes

• pnpm pack should work as expected when "prepack" modifies the manifest #​7558.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.2

Compare Source

Patch Changes

• Registry configuration from previous installation should not override current settings #​7507.
• pnpm dlx should not fail, when executed from package.json "scripts" 7424.
• A git-hosted dependency should not be added to the store if it failed to be built #​7407.
• pnpm publish should pack "main" file or "bin" files defined in "publishConfig" #​4195.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.1

Compare Source

Patch Changes

• Resolve the current working directory to its real location before doing any operations #​6524.
• Allow using token helpers in pnpm publish #​7316.
• Handle Git repository names containing capital letters #​7488.
• When hoisted-workspace-packages is true don't hoist the root package even if it has a name. Otherwise we would create a circular symlink.

Our Gold Sponsors

Our Silver Sponsors

v8.14.0

Compare Source

Minor Changes

• A new option added for hoisting packages from the workspace. When hoist-workspace-packages is set to true, packages from the workspace are symlinked to either <workspace_root>/node_modules/.pnpm/node_modules or to <workspace_root>/node_modules depending on other hoisting settings (hoist-pattern and public-hoist-pattern) #​7451.
• The pnpm dedupe command now accepts more command line options that the pnpm install command also accepts. Example: pnpm dedupe --store-dir=local-store-dir

Patch Changes

• The package information output by cat-index should be sorted by key.
• pnpm deploy should not touch the target directory if it already exists and isn't empty #​7351.
• pnpm add a-module-already-in-dev-deps will show a message to notice the user that the package was not moved to "dependencies" #​926 and fix #​7319.
• Don't install Node.js when use-node-version is set in a WebContainer #​7478.
• Fix copy-on-write on Windows Dev Drives #​7468.

Our Gold Sponsors

Our Silver Sponsors

v8.13.1

Minor Changes

• New commands added for inspecting the store:

  • pnpm cat-index: Prints the index file of a specific package in the store. The package is specified by its name and version:

    pnpm cat-index <pkg name>@&#8203;<pkg version>
    

  • pnpm cat-file: Prints the contents of a file based on the hash value stored in the index file. For example:

    pnpm cat-file sha512-mvavhfVcEREI7d8dfvfvIkuBLnx7+rrkHHnPi8mpEDUlNpY4CUY+CvJ5mrrLl18iQYo1odFwBV7z/cOypG7xxQ==
    

  • (EXPERIMENTAL) pnpm find-hash: Lists the packages that include the file with the specified hash. For example:

    pnpm find-hash sha512-mvavhfVcEREI7d8dfvfvIkuBLnx7+rrkHHnPi8mpEDUlNpY4CUY+CvJ5mrrLl18iQYo1odFwBV7z/cOypG7xxQ==
    

    This command is experimental. We might change how it behaves.

  Related issue: #​7413.

• A new setting added for symlinking injected dependencies from the workspace, if their dependencies use the same peer dependencies as the dependent package. The setting is called dedupe-injected-deps #​7416.

• Use --fail-if-no-match if you want the CLI fail if no packages were matched by the command #​7403.

Patch Changes

• pnpm list --parseable should not print the same dependency multiple times #​7429.
• Fix error message texts in the pnpm env commands #​7456.
• Better support for light themed terminals by the pnpm update --interactive command #​7439.
• Fix EPERM error that occasionally happened on Windows during renames in the store #​7213.
• Fix error as in update -i -r with Git specifiers #​7415.
• Added support for boolean values in 'bundleDependencies' package.json fields when installing a dependency. Fix to properly handle 'bundledDependencies' alias #​7411.

Our Gold Sponsors

Our Silver Sponsors

	Configuration 📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (0fead7b) 2.62% compared to head (932a407) 2.62%.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #182   +/-   ##
=====================================
  Coverage   2.62%   2.62%           
=====================================
  Files         14      14           
  Lines        953     953           
=====================================
  Hits          25      25           
  Misses       928     928           

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