v10.18.1

Compare Source

Patch Changes

• Don't print a warning, when--lockfile-only is used#​8320.
• pnpm setup creates a command shim to the pnpm executable. This is needed to be able to runpnpm self-update on Windows#​5700.
• When using pnpm catalogs and running a normalpnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when usingpnpm add --save-catalog as originally intended.

v10.18.0

Compare Source

Minor Changes

• Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

  Added configuration options for warning thresholds:fetchWarnTimeoutMs andfetchMinSpeedKiBps.
  Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

  Related PR:#​10025.

Patch Changes

• Retry filesystem operations on EAGAIN errors#​9959.
• Outdated command respectsminimumReleaseAge configuration#​10030.
• Correctly apply thecleanupUnusedCatalogs configuration when removing dependent packages.
• Don't fail with a meaningless error whenscriptShell is set tofalse#​8748.
• pnpm dlx should not fail whenminimumReleaseAge is set#​10037.

v10.17.1

Compare Source

Patch Changes

• When a version specifier cannot be resolved because the versions don't satisfy theminimumReleaseAge setting, print this information out in the error message#​9974.
• Fixstate.json creation path when executingpnpm patch in a workspace project#​9733.
• WhenminimumReleaseAge is set and thelatest tag is not mature enough, prefer a non-deprecated version as the newlatest#​9987.

v10.17.0

Compare Source

Minor Changes

• TheminimumReleaseAgeExclude setting now supports patterns. For instance:

  minimumReleaseAge:1440minimumReleaseAgeExclude:  -"@​eslint/*"

  Related PR:#​9984.

Patch Changes

• Don't ignore theminimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache#​9978.
• WhenminimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one#​9979.