Skip to content
This repository has been archived by the owner on Apr 14, 2023. It is now read-only.

chore(deps): update pnpm to v7.11.0 #9

Merged
merged 1 commit into from
Sep 10, 2022
Merged

chore(deps): update pnpm to v7.11.0 #9

merged 1 commit into from
Sep 10, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 25, 2022 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) 7.0.0 -> 7.11.0 age adoption passing confidence
pnpm (source) 7.9.5 -> 7.11.0 age adoption passing confidence

Release Notes

pnpm/pnpm

v7.11.0

Compare Source

Minor Changes

  • pnpm patch: edit the patched package in a directory specified by the --edit-dir option. E.g., pnpm patch express@3.1.0 --edit-dir=/home/xxx/src/patched-express #​5304

Patch Changes

  • Auto installing a peer dependency in a workspace that also has it as a dev dependency in another project #​5144.
  • 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.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.10.0...v7.11.0

v7.10.0

Compare Source

Minor Changes

  • New time-based resolution strategy supported.

    When resolution-mode is set to time-based, pnpm will resolve dependencies the following way:

    1. Direct dependencies will be resolved to their lowest versions. So if there is foo@^1.1.0 in the dependencies, then 1.1.0 will be installed.
    2. Subdependencies will be resolved from versions that were published before the last direct dependency was published.

    With this resolution mode installations with hot cache are faster. It also reduces the chance of subdependency hijacking as subdependencies will be updated only if direct dependencies are updated.

    This resolution mode works only with npm's full metadata. So it is slower in some scenarios. However, if you use Verdaccio v5.15.1 or newer, you may set the registry-supports-time-field setting to true, and it will be really fast.

    Related RFC.

  • Enhance pnpm env with the remove command. To remove a Node.js version installed by pnpm, run:

    pnpm env remove --global <node.js version>

Patch Changes

  • pnpm store prune should remove all cached metadata.
  • Don't modify the manifest of the injected workspace project, when it has the same dependency in prod and peer dependencies.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.9.5...v7.10.0

v7.9.5

Compare Source

Patch Changes
  • Set NODE_PATH when prefer-symlinked-executables is enabled #​5251.
  • Fail with a meaningful error when the audit endpoint doesn't exist #​5200.
  • Symlink a local dependency to node_modules, even if the target directory doesn't exist #​5219.
Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors

Full Changelog: pnpm/pnpm@v7.9.4...v7.9.5

v7.9.4

Compare Source

Patch Changes

  • Auto install peer dependencies when auto-install-peers is set to true and the lockfile is up to date #​5213.
  • pnpm env: for Node.js<16 install the x64 build on Darwin ARM as ARM build is not available #​5239.
  • pnpm env: log a message when the node.js tarball starts the download #​5241.
  • Fix pnpm install --merge-git-branch-lockfile when the lockfile is up to date #​5212.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.9.3...v7.9.4

v7.9.3

Compare Source

Patch Changes

  • Remove legacy signal handlers #​5224

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Full Changelog: pnpm/pnpm@v7.9.2...v7.9.3

v7.9.2

Compare Source

Patch Changes

  • When the same package is both in "peerDependencies" and in "dependencies", treat this dependency as a peer dependency if it may be resolved from the dependencies of parent packages #​5210.
  • Update node-gyp to v9.
  • Update the compatibility database.

Our Gold Sponsors

Our Silver Sponsors

v7.9.1

Compare Source

Patch Changes

  • pnpm setup: don't use setx to set env variables on Windows.

Our Gold Sponsors

Our Silver Sponsors

v7.9.0

Compare Source

Minor Changes

  • When ignore-dep-scripts is true, ignore scripts of dependencies but run the scripts of the project.
  • When ignore-compatibility-db is set to true, the compatibility database will not be used to patch dependencies #​5132.
  • Print the versions of packages in peer dependency warnings and errors.
  • Support a new hook for passing a custom package importer to the store controller.

Patch Changes

  • Don't print the same deprecation warning multiple times.
  • On POSIX pnpm setup should suggest users to source the config instead of restarting the terminal.
  • Installing a package with bin that points to an .exe file on Windows #​5159.
  • Fix bug where the package manifest was not resolved if verify-store-integrity is set to false.
  • Fix sorting of keys in lockfile to make it more deterministic and prevent unnecessary churn in the lockfile #​5151.
  • Don't create a separate bundle for pnpx.

Our Gold Sponsors

Our Silver Sponsors

v7.8.0

Compare Source

Minor Changes

  • When publishConfig.directory is set, only symlink it to other workspace projects if publishConfig.linkDirectory is set to true. Otherwise, only use it for publishing #​5115.

Patch Changes

  • Don't incorrectly identify a lockfile out-of-date when the package has a publishConfig.directory field #​5124.
  • Don't crash when a config file contains a setting with an env variable that doesn't exist #​5093.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.7.1...v7.8.0

v7.7.1

Compare Source

Patch Changes

  • pnpm should not consider a lockfile out-of-date if auto-install-peers is set to true and the peer dependency is in devDependencies or optionalDependencies #​5080.
  • Don't incorrectly consider a lockfile out-of-date when workspace:^ or workspace:~ version specs are used in a workspace.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Full Changelog: pnpm/pnpm@v7.7.0...v7.7.1

v7.7.0

Compare Source

Minor Changes

  • Add experimental lockfile format that should merge conflict less in the importers section. Enabled by setting the use-inline-specifiers-lockfile-format = true feature flag in .npmrc.

    If this feature flag is committed to a repo, we recommend setting the minimum allowed version of pnpm to this release in the package.json engines field. Once this is set, older pnpm versions will throw on invalid lockfile versions.

  • Add publishDirectory field to the lockfile and relink the project when it changes.

  • verify-store-integrity=false makes pnpm skip checking the integrities of files in the global content-addressable store.

  • Allow to set only-built-dependencies[] through .npmrc.

Patch Changes

  • It should be possible to publish a package with local dependencies from a custom publish directory (set via publishConfig.directory) #​3901.
  • pnpm deploy should inject local dependencies of all types (dependencies, optionalDependencies, devDependencies) #​5078.
  • When a project in a workspace has a publishConfig.directory set, dependent projects should install the project from that directory #​3901
  • pnpm deploy: accept absolute paths and use cwd instead of workspaceDir for deploy target directory #​4980.
  • pnpm setup should update .zshrc in the right directory when a $ZDOTDIR is set.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.6.0...v7.7.0

v7.6.0

Compare Source

Minor Changes

  • A new setting supported: prefer-symlinked-executables. When true, pnpm will create symlinks to executables in
    node_modules/.bin instead of command shims (but on POSIX systems only).

    This setting is true by default when node-linker is set to hoisted.

    Related issue: #​4782.

  • When lockfile-include-tarball-url is set to true, every entry in pnpm-lock.yaml will contain the full URL to the package's tarball #​5054.

Patch Changes

  • pnpm deploy should include all dependencies by default #​5035.

  • Don't print warnings about file verifications. Just print info messages instead.

  • pnpm publish --help should print the --recursive and --filter options #​5019.

  • It should be possible to run exec/run/dlx with the --use-node-version option.

  • pnpm deploy should not modify the lockfile #​5071

  • pnpm deploy should not fail in CI #​5071

  • When auto-install-peers is set to true, automatically install direct peer dependencies #​5028.

    So if your project the next manifest:

    {
  "dependencies": {
    "lodash": "^4.17.21"
  },
  "peerDependencies": {
    "react": "^18.2.0"
  }
}

    pnpm will install both lodash and react as a regular dependencies.

Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors

Full Changelog: pnpm/pnpm@v7.5.2...v7.6.0

v7.5.2

Compare Source

Patch Changes
  • Don't print any info messages about .pnpmfile.cjs #​5027.
  • Do not print a package with unchanged version in the installation summary #​5031.
Our Gold Sponsors
Our Silver Sponsors
What's Changed

Full Changelog: pnpm/pnpm@v7.5.1...v7.5.2

v7.5.1

Compare Source

Patch Changes
  • Don't symlink the autoinstalled peer dependencies to the root of node_modules #​4988.
  • Avoid retaining a copy of the contents of files deleted during patching #​5003.
  • Remove file reporter logging. Logged file is not useful #​4949.
Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors

Full Changelog: pnpm/pnpm@v7.5.0...v7.5.1

v7.5.0

Compare Source

Minor Changes

  • A new value rolling for option save-workspace-protocol. When selected, pnpm will save workspace versions using a rolling alias (e.g. "foo": "workspace:^") instead of pinning the current version number (e.g. "foo": "workspace:^1.0.0"). Usage example, in the root of your workspace, create a .npmrc with the following content:

    save-workspace-protocol=rolling

Patch Changes

  • pnpm remove <pkg> should not fail in a workspace that has patches #​4954
  • The hash of the patch file should be the same on both Windows and POSIX #​4961.
  • pnpm env use should throw an error on a system that use the MUSL libc.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Full Changelog: pnpm/pnpm@v7.4.1...v7.5.0

v7.4.1

Compare Source

Patch Changes

  • pnpm install in a workspace with patches should not fail when doing partial installation #​4954.
  • Never skip lockfile resolution when the lockfile is not up-to-date and --lockfile-only is used. Even if frozen-lockfile is true #​4951.
  • Never add an empty patchedDependencies field to pnpm-lock.yaml.

Our Gold Sponsors

Our Silver Sponsors

Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update pnpm to v7.9.5 chore(deps): update pnpm to v7.10.0 Sep 4, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.10.0 chore(deps): update pnpm to v7.11.0 Sep 5, 2022
@elonehoo elonehoo merged commit 867f677 into main Sep 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@elonehoo elonehoo elonehoo approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@elonehoo