v8.0.0-rc.0

Major Changes

• Node.js 14 support discontinued

  If you still require Node.js 14, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the @pnpm/exe package.

• Configuration updates:

  • auto-install-peers: enabled by default.
  • dedupe-peer-dependents: enabled by default.
  • save-workspace-protocol: set to rolling by default.
  • resolve-peers-from-workspace-root: enabled by default.
  • resolution-mode: set to lowest-direct by default.
  • publishConfig.linkDirectory: enabled by default.

• Lockfile modifications:

  • Lockfile v6 is adopted. This new format improves the readability of the lockfile by removing hashes from package IDs.

    This lockfile is supported in pnpm v7 as an opt-in, so if someone in your team is still using pnpm v7, you may set use-lockfile-v6=true in an .npmrc file in the root of the project and even pnpm v7 will read and write the lockfile in the new format.

  • The registry field is removed from the resolution object in pnpm-lock.yaml.

  • A lockfile is generated even for projects with no dependencies.

• Other changes:

  • When there's a files field in the package.json, only the files that are listed in it will be deployed. The same logic is applied when injecting packages. This behaviour can be changed by setting the deploy-all-files setting to true (Related issue #5911).
  • Direct dependencies are deduped. If a dependency is present in both a project and the workspace root, it will only be linked to the workspace root.

Our Gold Sponsors

Our Silver Sponsors