This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| pnpm (source) | 6.32.9 -> 7.30.5 |
Release Notes
pnpm/pnpm
v7.30.5
Patch Changes
pnpm auditshould work even if there are nopackage.jsonfile, just apnpm-lock.yamlfile.- Dedupe direct dependencies after hoisting.
- Don't remove automatically installed peer dependencies from the root workspace project, when
dedupe-peer-dependentsistrue#6154.
Our Gold Sponsors
Our Silver Sponsors
v7.30.4
v7.30.3
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
v7.30.1
Patch Changes
- Don't write the
pnpm-lock.yamlfile if it has no changes andpnpm install --frozen-lockfilewas executed #6158. - Fix git-hosted dependencies referenced via
git+sshthat 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 auditoutput #6203 - Aliased packages should be used to resolve peer dependencies too #4301.
Our Gold Sponsors
Our Silver Sponsors
v7.30.0
Minor Changes
- Allow to set a custom directory for storing patch files via the
patches-dirsetting #6215
Patch Changes
- New directories should be prepended to NODE_PATH in command shims, not appended.
- Retry copying file on EBUSY error #6201.
Our Gold Sponsors
Our Silver Sponsors
v7.29.3
Patch Changes
- Command shim should not set higher priority to the
node_modules/.pnpm/node_modulesdirectory through theNODE_PATHenv variable, then the command's ownnode_modulesdirectory #5176. extend-node-pathis set back totrueby default. It was set tofalsein v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extendingNODE_PATH. We have fixed the Jest issue with a different solution #6213.
Our Gold Sponsors
Our Silver Sponsors
v7.29.2
v7.29.1
Patch Changes
- Settings related to authorization should be set/deleted by npm CLI #6181.
Our Gold Sponsors
Our Silver Sponsors
v7.29.0
Minor Changes
A new setting is now supported:
dedupe-peer-dependents.When this setting is set to
true, packages with peer dependencies will be deduplicated after peers resolution.For instance, let's say we have a workspace with two projects and both of them have
webpackin their dependencies.webpackhasesbuildin its optional peer dependencies, and one of the projects hasesbuildin its dependencies. In this case, pnpm will link two instances ofwebpackto thenode_modules/.pnpmdirectory: one withesbuildand another one without it:node_modules .pnpm webpack@1.0.0_esbuild@1.0.0 webpack@1.0.0 project1 node_modules webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack project2 node_modules webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack esbuildThis makes sense because
webpackis used in two projects, and one of the projects doesn't haveesbuild, so the two projects cannot share the same instance ofwebpack. However, this is not what most developers expect, especially since in a hoistednode_modules, there would only be one instance ofwebpack. Therefore, you may now use thededupe-peer-dependentssetting to deduplicatewebpackwhen it has no conflicting peer dependencies (explanation at the end). In this case, if we setdedupe-peer-dependentstotrue, both projects will use the samewebpackinstance, which is the one that hasesbuildresolved:node_modules .pnpm webpack@1.0.0_esbuild@1.0.0 project1 node_modules webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack project2 node_modules webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack esbuildWhat are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:
node_modules .pnpm webpack@1.0.0_react@16.0.0_esbuild@1.0.0 webpack@1.0.0_react@17.0.0 project1 node_modules webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack react (v17) project2 node_modules webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack esbuild react (v16)In this case, we cannot dedupe
webpackaswebpackhasreactin its peer dependencies andreactis resolved from two different versions in the context of the two projects.
Patch Changes
The configuration added by
pnpm setupshould check if the pnpm home directory is already in the PATH before adding to the PATH.Before this change, this code was added to the shell:
export PNPM_HOME="$HOME/Library/pnpm" export PATH="$PNPM_HOME:$PATH"Now this will be added:
export PNPM_HOME="$HOME/Library/pnpm" case ":$PATH:" in *":$PNPM_HOME:"*) ;; *) export PATH="$PNPM_HOME:$PATH" ;; esacAdd
skippedstatus in exec report summary when script is missing #6139.pnpm env -gshould fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.Should not throw an error when local dependency use file protocol #6115.
Fix the incorrect error block when subproject has been patched #6183
Our Gold Sponsors
Our Silver Sponsors
v7.28.0
Minor Changes
- Add
--report-summaryforpnpm execandpnpm run#6008. - Show path info for
pnpm why --jsonor--long#6103. - Extend the
pnpm.peerDependencyRules.allowedVersionspackage.jsonoption to support theparent>childselector syntax. This syntax allows for extending specificpeerDependencies#6108.
Patch Changes
- Update the lockfile if a workspace has a new project with no dependencies.
- Fix a case of installs not being deterministic and causing lockfile changes between repeat installs. When a dependency only declares
peerDependenciesMetaand notpeerDependencies,dependencies, oroptionalDependencies, the dependency's peers were not considered deterministically before. patch-commitshould auto apply patches in workspaces #6048- Automatically fix conflicts in v6 lockfile.
pnpm config setshould write to the global config file by default #5877.
Our Gold Sponsors
Our Silver Sponsors
v7.27.1
Patch Changes
- Add
store pathdescription to thepnpmcli help. - Print a hint that suggests to run
pnpm store prune, when a tarball integrity error happens. - Don't retry installation if the integrity checksum of a package failed and no lockfile was present.
- Fail with a meaningful error message when cannot parse a proxy URL.
- The
strict-ssl,ca,key, andcertsettings should work with HTTPS proxy servers #4689.
Our Gold Sponsors
Our Silver Sponsors
v7.27.0
Minor Changes
- A new
resolution-modeadded:lowest-direct. With this resolution mode direct dependencies will be resolved to their lowest versions. So if there isfoo@^1.1.0in the dependencies, then1.1.0will be installed, even if the latest version offoois1.2.0. - Support script selector with RegExp such as
pnpm run /build:.*/and execute the matched scripts with the RegExp #5871.
Patch Changes
Fix version number replacing for namespaced workspace packages.
workspace:@​foo/bar@*should be replaced withnpm:@​foo/bar@<version>on publish #6052.When resolving dependencies, prefer versions that are already used in the root of the project. This is important to minimize the number of packages that will be nested during hoisting #6054.
Deduplicate direct dependencies.
Let's say there are two projects in the workspace that dependend on
foo. One project hasfoo@1.0.0in the dependencies while another one hasfoo@^1.0.0in the dependencies. In this case,foo@1.0.0should be installed to both projects as satisfies the version specs of both projects.Use Map rather than Object in
createPackageExtenderto prevent read the prototype property to native function
Our Gold Sponsors
Our Silver Sponsors
v7.26.3
Patch Changes
- Directories inside the virtual store should not contain the ( or ) chars. This is to fix issues with storybook and the new v6
pnpm-lock.yamllockfile format #5976. - The update command should not replace dependency versions specified via dist-tags #5996.
- Fixed an issue that was causing pnpm to stuck forever during installation #5909.
Our Gold Sponsors
Our Silver Sponsors
v7.26.2
Patch Changes
- Wrap text in
pnpm auditoutput for better readability #5981 - Fix "cross-device link not permitted" error when
node-linkeris set tohoisted#5992.
Our Gold Sponsors
Our Silver Sponsors
v7.26.1
Patch Changes
- Fixed out of memory error that sometimes happens when
node-linkeris set tohoisted#5988. - Fixed
EMFILE: too many open filesby using graceful-fs for reading bin files of dependencies #5887. - Fix lockfile v6 on projects that use patched dependencies #5967.
Our Gold Sponsors
Our Silver Sponsors
v7.26.0
Minor Changes
- Add a
pnpm dedupecommand that removes dependencies from the lockfile by re-resolving the dependency graph. This work similar to yarn'syarn dedupe --strategy highestcommand #5958
Patch Changes
- Packages hoisted to the virtual store are not removed on repeat install, when the non-headless algorithm runs the installation #5971.
prepublishOnlyandprepublishshould not be executed onpnpm pack#2941.
Our Gold Sponsors
Our Silver Sponsors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates 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.
