v3.2.6

Compare Source

Bug Fixes

• undefined reference to response.body when aborted (#​1578) (1c5ed6b)

v3.2.5

Compare Source

Bug Fixes

• use space in accept-encoding values (#​1572) (a92b5d5), closes #​1571

v7.3.0

Compare Source

Minor Changes

• A new setting added: pnpm.peerDependencyRules.allowAny. allowAny is an array of package name patterns, any peer dependency matching the pattern will be resolved from any version, regardless of the range specified in peerDependencies. For instance:

  {
     "pnpm": {
       "peerDependencyRules": {
         "allowAny": ["@​babel/*", "eslint"]
       }
     }
  }

  The above setting will mute any warnings about peer dependency version mismatches related to @babel/ packages or eslint.

• The pnpm.peerDependencyRules.ignoreMissing setting may accept package name patterns. So you may ignore any missing @babel/* peer dependencies, for instance:

  {
    "pnpm": {
      "peerDependencyRules": {
        "ignoreMissing": ["@​babel/*"]
      }
    }
  }

• Experimental. New settings added: use-git-branch-lockfile, merge-git-branch-lockfiles, merge-git-branch-lockfiles-branch-pattern #​4475.

Patch Changes

• Packages that should be built are always cloned or copied from the store. This is required to prevent the postinstall scripts from modifying the original source files of the package.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.2.1...v7.3.0

v7.2.1

Compare Source

Patch Changes

• Support Node.js from v14.6.
• Don't fail when the cafile setting is specified #​4877. This fixes a regression introduced in pnpm v7.2.0.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.2.0...v7.2.1

v7.2.0

Compare Source

Minor Changes

• A new setting is supported for ignoring specific deprecation messages: pnpm.allowedDeprecatedVersions. The setting should be provided in the pnpm section of the root package.json file. The below example will mute any deprecation warnings about the request package and warnings about express v1:

  {
    "pnpm": {
      "allowedDeprecatedVersions": {
        "request": "*",
        "express": "1"
      }
    }
  }

  Related issue: #​4306
  Related PR: #​4864

Patch Changes

• Update the compatibility database.
• Report only the first occurrence of a deprecated package.
• Add better hints to the peer dependency issue errors.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.9...v7.2.0

v7.1.9

Compare Source

Patch Changes

• When the same package is found several times in the dependency graph, correctly autoinstall its missing peer dependencies at all times #​4820.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.8...v7.1.9

v7.1.8

Compare Source

Patch Changes

• Suggest updating using Corepack, when pnpm was installed via Corepack.
• It should be possible to install a git-hosted package that has no package.json file #​4822.
• Fix pre-compiled pnpm binaries crashing when NODE_MODULES is set.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.7...v7.1.8

v7.1.7

Compare Source

Patch Changes

• Improve the performance of the build sequence calculation step #​4815.
• Correctly detect repeated dependency sequence during resolution #​4813.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.6...v7.1.7

v7.1.6

Compare Source

Patch Changes

• Don't fail on projects with linked dependencies, when auto-install-peers is set to true #​4796.
• NODE_ENV=production pnpm install --dev should only install dev deps #​4745.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.5...v7.1.6

v7.1.5

Compare Source

Patch Changes

• Correctly detect the active Node.js version, when the pnpm CLI is bundled to an executable #​4203.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.4...v7.1.5

v7.1.4

Compare Source

Patch Changes

• Correctly detect the active Node.js version, when the pnpm CLI is bundled to an executable #​4203.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.3...v7.1.4

v7.1.3

Compare Source

Patch Changes

• When auto-install-peers is set to true, automatically install missing peer dependencies without writing them to package.json as dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #​4776.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.2...v7.1.3

v7.1.2

Compare Source

Patch Changes

• pnpm setup should not fail on Windows if PNPM_HOME is not yet in the system registry #​4757
• pnpm dlx shouldn't modify the lockfile in the current working directory #​4743.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.1...v7.1.2

v7.1.1

Compare Source

Patch Changes

• When the global bin directory is set to a symlink, check not only the symlink in the PATH but also the target of the symlink #​4744.
• Sanitize the directory names created inside node_modules/.pnpm and inside the global store #​4716
• All arguments after pnpm create <pkg> should be passed to the executed create app package. So pnpm create next-app --typescript should work`.
• Resolve commits from GitHub via https #​4734.

Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.0...v7.1.1