Update pnpm to v8.14.0

[renovate]

This PR contains the following updates:

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

---

Release Notes

pnpm/pnpm (pnpm)

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

v8.12.1

Compare Source

Patch Changes

• Don't report dependencies with optional dependencies as being added on repeat install. This was a bug in reporting #​7384.
• Fix a bug where --fix-lockfile crashes on tarballs #​7368.
• Do not create empty patch directory.
• Installation should not fail if an empty node_modules directory cannot be removed #​7405.

Our Gold Sponsors

Our Silver Sponsors

v8.12.0

Compare Source

Minor Changes

• Add support for basic authorization header #​7371.

Patch Changes

• Fix a bug where pnpm incorrectly passes a flag to a run handler as a fallback command #​7244.
• When dedupe-direct-deps is set to true, commands of dependencies should be deduplicated #​7359.

Our Gold Sponsors

Our Silver Sponsors

v8.11.0

Compare Source

Minor Changes

• (IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain /<pkg_name>@&#8203;<pkg_version, not <domain>/<pkg_name>@&#8203;<pkg_version>.

  This change is a fix to avoid the same package from being added to node_modules/.pnpm multiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile.

  We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile.

  Related PR: #​7318.

Patch Changes

• 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.
• The modules directory should not be removed if the registry configuration has changed.
• Fix missing auth tokens in registries with paths specified (e.g. //npm.pkg.github.com/pnpm). #​5970 #​2933

Our Gold Sponsors

Our Silver Sponsors

v8.10.5

Compare Source

Patch Changes

• Don't fail on an empty pnpm-workspace.yaml file #​7307.

Our Gold Sponsors

Our Silver Sponsors

v8.10.4

Compare Source

Patch Changes

• Fixed out-of-memory exception that was happening on dependencies with many peer dependencies, when node-linker was set to hoisted #​6227.

Our Gold Sponsors

Our Silver Sponsors

v8.10.3

Compare Source

Patch Changes

• (Important) Increased the default amount of allowed concurrent network request on systems that have more than 16 CPUs #​7285.

• pnpm patch should reuse existing patch when shared-workspace-file=false #​7252.

• Don't retry fetching missing packages, since the retries will never work #​7276.

• When using pnpm store prune --force alien directories are removed from the store #​7272.

• Downgraded npm-packlist because the newer version significantly slows down the installation of local directory dependencies, making it unbearably slow.

  npm-packlist was upgraded in this PR to fix #​6997. We added our own file deduplication to fix the issue of duplicate file entries.

• Fixed a performance regression on running installation on a project with an up to date lockfile #​7297.

• Throw an error on invalid pnpm-workspace.yaml file #​7273.

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.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
reactive	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 5, 2024 11:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 660e7e9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR