v7.9.3

Compare Source

Patch Changes

• Remove legacy signal handlers #​5224

Our Gold Sponsors

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

v7.9.1

Compare Source

Patch Changes

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

Our Gold 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

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

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

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

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

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