Update pnpm to v6.30.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	6.24.3 -> 6.30.1

---

Release Notes

pnpm/pnpm

v6.30.1

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.0

Compare Source

Minor Changes

• When checking that a package is linked from the store, check the existence of the package and read its stats with a single filesystem operation #​4304.

v6.29.2

Compare Source

Patch Changes

• node_modules directories inside injected dependencies should not be overwritten #​4299.

v6.29.1

v6.29.0

Minor Changes

• Add support of the update-notifier configuration option #​4158.

Patch Changes

• A package should be able to be a dependency of itself.

v6.28.0

Compare Source

Minor Changes

• New option added: embed-readme. When false, pnpm publish doesn't save the readme file's content to package.json before publish #​4265.

Patch Changes

• pnpm exec should look for the executed command in the node_modules/.bin directory that is relative to the current working directory. Only after that should it look for the executable in the workspace root.
• Injected dependencies should work properly in projects that use the hoisted node linker #​4259.

v6.27.2

Compare Source

v6.27.1

Compare Source

Patch Changes

• peerDependencyRules should work when both overrides and packageExtensions are present as well #​4255.
• pnpm list should show information whether a package is private or not #​4246.

v6.27.0

Compare Source

Minor Changes

• Side effects cache is not an experimental feature anymore.

  Side effects cache is saved separately for packages with different dependencies. So if foo has bar in the dependencies, then a separate cache will be created each time foo is installed with a different version of bar #​4238.

Patch Changes

• Update command should work when there is a dependency with emty version in devDependencies #​4196.
• Side effects cache should work in a workspace.

v6.26.1

Compare Source

Patch Changes

• During installation, override any symlinks in node_modules. This was an issue only with node-linker=hoisted #​4229.
• Print warnings about deprecated subdependencies #​4227.

v6.26.0

Compare Source

Minor Changes

• In order to mute some types of peer dependency warnings, a new section in package.json may be used for declaring peer dependency warning rules. For example, the next configuration will turn off any warnings about missing babel-loader peer dependency and about @angular/common, when the wanted version of @angular/common is not v13.

  {
    "name": "foo",
    "version": "0.0.0",
    "pnpm": {
      "peerDependencyRules": {
        "ignoreMissing": ["babel-loader"],
        "allowedVersions": {
          "@​angular/common": "13"
        }
      }
    }
  }

• New setting supported: auto-install-peers. When it is set to true, pnpm add <pkg> automatically installs any missing peer dependencies as devDependencies #​4213.

v6.25.1

Compare Source

Patch Changes

• Run the install scripts of hoisted dependencies in a workspace with no root project #​4209.

v6.25.0

Compare Source

Minor Changes

• New installation mode added that creates a flat node_modules directory without the usage of symlinks. This is similar to the one created by npm and Yarn Classic.

  To use this new installation mode, set the node-linker setting to hoisted. These are the supported values of node-linker:

  • isolated - the default value.
  • hoisted - flat node_modules without symlinks.
  • pnp - no node_modules. Yarn's Plug'n'Play managed by pnpm.

  Related issue: #​4073

• Add support for token helper, a command line tool to obtain a token.

  A token helper is an executable, set in the user's .npmrc which outputs an auth token. This can be used in situations where the authToken is not a constant value, but is something that refreshes regularly, where a script or other tool can use an existing refresh token to obtain a new access token.

  The configuration for the path to the helper must be an absolute path, with no arguments. In order to be secure, it is only permitted to set this value in the user .npmrc, otherwise a project could place a value in a project local .npmrc and run arbitrary executables.

  Usage example:

  ; Setting a token helper for the default registry
  tokenHelper=/home/ivan/token-generator
  
  ; Setting a token helper for the specified registry
  //registry.corp.com:tokenHelper=/home/ivan/token-generator

  Related PRs:

  • pnpm/credentials-by-uri#​2
  • #​4163

• New CLI option: --ignore-workspace. When used, pnpm ignores any workspace configuration found in the current or parent directories.

• If use-beta-cli is true, then don't set npm_config_argv env variable for scripts #​4175.

v6.24.4

Compare Source

---

Configuration

📅 Schedule: "after 9am and before 7pm on friday" in timezone Europe/Berlin.

🚦 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 this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.