chore(deps): update dependency pnpm to v6.35.1#35
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.28.0→6.35.1Release Notes
pnpm/pnpm (pnpm)
v6.35.1Compare Source
Patch Changes
.npmrcfiles in subdirectories inside a workspace #2570.v6.35.0Compare Source
Patch Changes
Installing a package with
binthat points to an.exefile on Windows #5159.Ignore the
always-authsetting.pnpm will never reuse the registry auth token for requesting the package tarball, if the package tarball is hosted on a different domain.
So, for example, if your registry is at
https://company.registry.com/but the tarballs are hosted athttps://tarballs.com/, then you will have to configure the auth token for both domains in your.npmrc:When an error happens during installation of a subdependency, print some context information in order to be able to locate that subdependency. Print the exact chain of packages that led to the problematic dependency.
v6.34.0Compare Source
Minor Changes
ignore-compatibility-dbis set totrue, the compatibility database will not be used to patch dependencies #5132.Full Changelog: pnpm/pnpm@v6.33.1...v6.34.0
v6.33.1Compare Source
Patch Changes
v6.33.0Compare Source
v6.32.25Compare Source
Patch Changes
pnpm audit --fixshould not add an override for a vulnerable package that has no fixes released.pnpm env useshould throw an error on a system that use the MUSL libc.v6.32.24Compare Source
Patch Changes
Don't crash when
pnpm update --interactiveis cancelled with Ctrl+c.The
use-node-versionsetting should work with prerelease Node.js versions. For instance:v6.32.23Compare Source
Patch Changes
v6.32.22Compare Source
Patch Changes
v6.32.21Compare Source
Patch Changes
v6.32.20Compare Source
Patch Changes
package.jsonfile #4822.v6.32.19Compare Source
Patch Changes
v6.32.18Compare Source
Patch Changes
auto-install-peersis set totrue#4796.NODE_ENV=production pnpm install --devshould only install dev deps #4745.Full Changelog: pnpm/pnpm@v6.32.17...v6.32.18
v6.32.17Compare Source
Patch Changes
v6.32.16Compare Source
Patch Changes
auto-install-peersis set totrue, automatically install missing peer dependencies without writing them topackage.jsonas dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #4776.v6.32.15Compare Source
Patch Changes
pnpm setupshould not fail on Windows ifPNPM_HOMEis not yet in the system registry #4757pnpm dlxshouldn't modify the lockfile in the current working directory #4743.v6.32.14Compare Source
Patch Changes
node_modules/.pnpmand inside the global store #4716Full Changelog: pnpm/pnpm@v6.32.13...v6.32.14
v6.32.13Compare Source
Patch Changes
pnpm setupshould update the config of the current shell, not the preferred shell.pnpm dlxshould work with git-hosted packages. For example:pnpm dlx gengjiawen/envinfo#4714.pnpm setupshould not override the PNPM_HOME env variable on Windows, unless--forceis used.pnpm create <pkg>should be passed to the executed create app package. Sopnpm create next-app --typescriptshould work`.pnpm run --streamshould prefix the output with directory #4702Full Changelog: pnpm/pnpm@v6.32.12...v6.32.13
v6.32.12Compare Source
Patch Changes
pnpm dlxshould work when the bin name of the executed package isn't the same as the package name #4672.pnpm pruneworks in a workspace #4647.pnpm prunedoes not remove hoisted dependencies.pnpm dlxshould print messages about installation to stderr #1698.v6.32.11Compare Source
Patch Changes
pnpm publishshould work correctly in a workspace, when the latest npm CLI is installed #4348.node_modules/.ignoredsubfolder and a package with that name is already present in `node_modules/.ignored' #4626.v6.32.10Compare Source
Patch Changes
v6.32.9Compare Source
Patch Changes
Fix an error with peer resolutions, which was happening when there was a circular dependency and another dependency that had the name of the circular dependency as a substring.
When
pnpm execis running a command in a workspace project, the commands that are in the dependencies of that workspace project should be in the PATH #4481.Hide "WARN deprecated" messages on loglevel error #4507
Don't show the progress bar when loglevel is set to warn or error.
v6.32.8Compare Source
Patch Changes
v6.32.7Compare Source
Patch Changes
auto-install-peerstotrueshould work.v6.32.6Compare Source
Patch Changes
v6.32.5Compare Source
Patch Changes
dependenciesMetashould be saved into the lockfile, when it is added to the package manifest by a hook.v6.32.4Compare Source
Patch Changes
dependenciesMetafield in the manifest should be satisfied by a not set field in the lockfile #4463.package.json#4487.v6.32.3Compare Source
Patch Changes
4941f31: The location of an injected directory dependency should be correctly located, when there is a chain of local dependencies (declared via thefile:protocol`).The next scenario was not working prior to the fix. There are 3 projects in the same folder: foo, bar, qar.
foo/package.json:{ "name": "foo", "dependencies": { "bar": "file:../bar" }, "dependenciesMeta": { "bar": { "injected": true } } }bar/package.json:{ "name": "bar", "dependencies": { "qar": "file:../qar" }, "dependenciesMeta": { "qar": { "injected": true } } }qar/package.json:{ "name": "qar" }Related PR: #4415.
v6.32.2Compare Source
Patch Changes
pnpm installwhen the lockfile is broken andnode-linkeris set tohoisted#4387.v6.32.1Compare Source
Patch Changes
pnpm publishshould work correctly in a workspace, when the latest npm CLI is installed #4348.node_modules/.ignoredsubfolder and a package with that name is already present in `node_modules/.ignored' #4626.v6.32.0Compare Source
Minor Changes
A new setting is supported in the
pnpmsection of thepackage.jsonfile #4001.onlyBuiltDependenciesis an array of package names that are allowed to be executed during installation. If this field exists, only mentioned packages will be able to run install scripts.{ "pnpm": { "onlyBuiltDependencies": ["fsevents"] } }-Fis a short alias of--filter#3467.When adding a new dependency, use the version specifier from the overrides, when present #4313.
Normally, if the latest version of
foois2.0.0, thenpnpm add fooinstallsfoo@^2.0.0. This behavior changes iffoois specified in an override:{ "pnpm": { "overrides": { "foo": "1.0.0" } } }In this case,
pnpm add foowill addfoo@1.0.0to the dependency. However, if a version is explicitly specifying, then the specified version will be used and the override will be ignored. Sopnpm add foo@0will install v0 and it doesn't matter what is in the overrides.Patch Changes
*, just replace any range with*.v6.31.0Compare Source
Minor Changes
Added
--shell-mode/-coption support topnpm exec#4328--shell-mode: shell interpreter. See: https://github.com/sindresorhus/execa/tree/484f28de7c35da5150155e7a523cbb20de161a4f#shellUsage example:
{ "scripts": { "check": " pnpm -r --shell-mode exec -- echo \"\\$PNPM_PACKAGE_NAME\"" } }Patch Changes
publishConfigwhen thepackorpublishcommands are used #4311pnpx,pnpm dlx,pnpm create, andpnpm execcommands should set thenpm_config_user_agentenv variable #3985.v6.30.1Compare Source
Patch Changes
This fixes an issue introduced in pnpm v6.30.0.
When a package is not linked to
node_modules, no info message should be printed about it being "relinked" from the store #4314.v6.30.0Compare Source
Minor Changes
v6.29.2Compare Source
Patch Changes
node_modulesdirectories inside injected dependencies should not be overwritten #4299.v6.29.1Compare Source
Patch Changes
node_modules.v6.29.0Compare Source
Minor Changes
update-notifierconfiguration option #4158.Patch Changes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.