pnpm/pnpm (pnpm)
### [`v9.0.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.0.0)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.15.7...v9.0.0)
##### Major Changes
- Node.js v16 support discontinued
If you still require Node.js 16, 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](https://pnpm.io/installation#using-a-standalone-script) or install the `@pnpm/exe` package.
- Configuration updates:
- [`dedupe-injected-deps`](https://pnpm.io/npmrc#dedupe-injected-deps): enabled by default.
- [`link-workspace-packages`](https://pnpm.io/npmrc#link-workspace-packages): disabled by default. This means that by default, dependencies will be linked from workspace packages only when they are specified using the [workspace protocol](https://pnpm.io/workspaces#workspace-protocol-workspace).
- [`hoist-workspace-packages`](https://pnpm.io/npmrc#hoist-workspace-packages): enabled by default.
- [`enable-pre-post-scripts`](https://pnpm.io/cli/run#enable-pre-post-scripts): enabled by default.
- Use the same directory for state files on macOS as on Linux (`~/.local/state/pnpm`).
- pnpm will now check the `package.json` file for a `packageManager` field. If this field is present and specifies a different package manager or a different version of pnpm than the one you're currently using, pnpm will not proceed. This ensures that you're always using the correct package manager and version that the project requires.
- Lockfile changes:
- Lockfile v9 is adopted. This new format has changes for better readability, and better resistence to Git conflicts.
- Support for lockfile v5 is dropped. Use pnpm v8 to convert lockfile v5 to lockfile v6 [#7470](https://togithub.com/pnpm/pnpm/pull/7470).
- Dependency resolution changes:
- Correct resolution of peer dependencies that have their own peer dependencies.
Related issue: [#7444](https://togithub.com/pnpm/pnpm/issues/7444).
Related PR: [#7606](https://togithub.com/pnpm/pnpm/pull/7606).
- Optional peer dependencies may be resolved from any packages in the dependency graph [#7830](https://togithub.com/pnpm/pnpm/pull/7830).
- `pnpm licenses list` prints license information of all versions of the same package in case different versions use different licenses. The format of the `pnpm licenses list --json` output has been changed [#7528](https://togithub.com/pnpm/pnpm/pull/7528).
- A new command added for printing completion code to the console: `pnpm completion [shell]`. The old command that modified the user's shell dotfiles has been removed [#3083](https://togithub.com/pnpm/pnpm/issues/3083).
- When installing git-hosted dependencies, only pick the files that would be packed with the package [#7638](https://togithub.com/pnpm/pnpm/pull/7638).
##### Minor Changes
- It is now possible to install only a subdirectory from a Git repository.
For example, `pnpm add github:user/repo#path:packages/foo` will add a dependency from the `packages/foo` subdirectory.
This new parameter may be combined with other supported parameters separated by `&`. For instance, the next command will install the same package from the `dev` branch: `pnpm add github:user/repo#dev&path:packages/bar`.
Related issue: [#4765](https://togithub.com/pnpm/pnpm/issues/4765).
Related PR: [#7487](https://togithub.com/pnpm/pnpm/pull/7487).
- `node-gyp` updated to version 10.
- PowerShell completion support added [#7597](https://togithub.com/pnpm/pnpm/pull/7597).
- Support `node-options` option inside `.npmrc` file when running scripts [#7596](https://togithub.com/pnpm/pnpm/issues/7596).
- Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported: `:certfile`, `:keyfile`, and `:ca`. For instance:
//registry.mycomp.com/:certfile=server-cert.pem
//registry.mycomp.com/:keyfile=server-key.pem
//registry.mycomp.com/:cafile=client-cert.pem
Related issue: [#7427](https://togithub.com/pnpm/pnpm/issues/7427).
Related PR: [#7626](https://togithub.com/pnpm/pnpm/pull/7626).
- Add a field named `ignoredOptionalDependencies`. This is an array of strings. If an optional dependency has its name included in this array, it will be skipped [#7714](https://togithub.com/pnpm/pnpm/pull/7714).
- The checksum of the `.pnpmfile.cjs` is saved into the lockfile. If the pnpmfile gets modified, the lockfile is reanalyzed to apply the changes [#7662](https://togithub.com/pnpm/pnpm/pull/7662).
- Added cache for `pnpm dlx` [#5277](https://togithub.com/pnpm/pnpm/issues/5277).
##### Patch Changes
- Package tarballs are not downloaded during `--lockfile-only` installation [#1328](https://togithub.com/pnpm/pnpm/issues/1328).
- Peer dependency rules should only affect reporting, not data in the lockfile [#7758](https://togithub.com/pnpm/pnpm/pull/7758).
- Link overrides should be able to use absolute path [#7749](https://togithub.com/pnpm/pnpm/pull/7749).
- `pnpm dlx` should not read settings from the current working directory [#7916](https://togithub.com/pnpm/pnpm/pull/7916).
##### Platinum Sponsors
##### Gold Sponsors
##### Our Silver Sponsors
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
8.15.7->9.0.0Release Notes
pnpm/pnpm (pnpm)
### [`v9.0.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.0.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.15.7...v9.0.0) ##### Major Changes - Node.js v16 support discontinued If you still require Node.js 16, 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](https://pnpm.io/installation#using-a-standalone-script) or install the `@pnpm/exe` package. - Configuration updates: - [`dedupe-injected-deps`](https://pnpm.io/npmrc#dedupe-injected-deps): enabled by default. - [`link-workspace-packages`](https://pnpm.io/npmrc#link-workspace-packages): disabled by default. This means that by default, dependencies will be linked from workspace packages only when they are specified using the [workspace protocol](https://pnpm.io/workspaces#workspace-protocol-workspace). - [`hoist-workspace-packages`](https://pnpm.io/npmrc#hoist-workspace-packages): enabled by default. - [`enable-pre-post-scripts`](https://pnpm.io/cli/run#enable-pre-post-scripts): enabled by default. - Use the same directory for state files on macOS as on Linux (`~/.local/state/pnpm`). - pnpm will now check the `package.json` file for a `packageManager` field. If this field is present and specifies a different package manager or a different version of pnpm than the one you're currently using, pnpm will not proceed. This ensures that you're always using the correct package manager and version that the project requires. - Lockfile changes: - Lockfile v9 is adopted. This new format has changes for better readability, and better resistence to Git conflicts. - Support for lockfile v5 is dropped. Use pnpm v8 to convert lockfile v5 to lockfile v6 [#7470](https://togithub.com/pnpm/pnpm/pull/7470). - Dependency resolution changes: - Correct resolution of peer dependencies that have their own peer dependencies. Related issue: [#7444](https://togithub.com/pnpm/pnpm/issues/7444). Related PR: [#7606](https://togithub.com/pnpm/pnpm/pull/7606). - Optional peer dependencies may be resolved from any packages in the dependency graph [#7830](https://togithub.com/pnpm/pnpm/pull/7830). - `pnpm licenses list` prints license information of all versions of the same package in case different versions use different licenses. The format of the `pnpm licenses list --json` output has been changed [#7528](https://togithub.com/pnpm/pnpm/pull/7528). - A new command added for printing completion code to the console: `pnpm completion [shell]`. The old command that modified the user's shell dotfiles has been removed [#3083](https://togithub.com/pnpm/pnpm/issues/3083). - When installing git-hosted dependencies, only pick the files that would be packed with the package [#7638](https://togithub.com/pnpm/pnpm/pull/7638). ##### Minor Changes - It is now possible to install only a subdirectory from a Git repository. For example, `pnpm add github:user/repo#path:packages/foo` will add a dependency from the `packages/foo` subdirectory. This new parameter may be combined with other supported parameters separated by `&`. For instance, the next command will install the same package from the `dev` branch: `pnpm add github:user/repo#dev&path:packages/bar`. Related issue: [#4765](https://togithub.com/pnpm/pnpm/issues/4765). Related PR: [#7487](https://togithub.com/pnpm/pnpm/pull/7487). - `node-gyp` updated to version 10. - PowerShell completion support added [#7597](https://togithub.com/pnpm/pnpm/pull/7597). - Support `node-options` option inside `.npmrc` file when running scripts [#7596](https://togithub.com/pnpm/pnpm/issues/7596). - Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported: `