pnpm/pnpm
### [`v8.6.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.0)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.5.1...v8.6.0)
#### Minor Changes
- Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.
A new field will now be present in the lockfile: `settings`. It will store the values of two settings: `autoInstallPeers` and `excludeLinksFromLockfile`. If someone tries to perform a `frozen-lockfile` installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.
The lockfile format version is bumped from v6.0 to v6.1.
Related PR: [#6557](https://togithub.com/pnpm/pnpm/pull/6557)
Related issue: [#6312](https://togithub.com/pnpm/pnpm/issues/6312)
- A new setting, `exclude-links-from-lockfile`, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.
This setting was primarily added for use by [Bit CLI](https://togithub.com/teambit/bit), which links core aspects to `node_modules` from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.
#### Patch Changes
- Don't print "Lockfile is up-to-date" message before finishing all the lockfile checks [#6544](https://togithub.com/pnpm/pnpm/issues/6544).
- When updating dependencies, preserve the range prefix in aliased dependencies. So `npm:foo@1.0.0` becomes `npm:foo@1.1.0`.
- Print a meaningful error when a project referenced by the `workspace:` protocol is not found in the workspace [#4477](https://togithub.com/pnpm/pnpm/issues/4477).
- `pnpm rebuild` should not fail when `node-linker` is set to `hoisted` and there are skipped optional dependencies [#6553](https://togithub.com/pnpm/pnpm/pull/6553).
- Peers resolution should not fail when a linked in dependency resolves a peer dependency.
- Build projects in a workspace in correct order [#6568](https://togithub.com/pnpm/pnpm/pull/6568).
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.5.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.5.1)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.5.0...v8.5.1)
#### Patch Changes
- Expanded missing command error, including 'did you mean' [#6492](https://togithub.com/pnpm/pnpm/issues/6492).
- When installation fails because the lockfile is not up-to-date with the `package.json` file(s), print out what are the differences [#6536](https://togithub.com/pnpm/pnpm/pull/6536).
- Normalize current working directory on Windows [#6524](https://togithub.com/pnpm/pnpm/issues/6524).
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.5.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.5.0)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.4.0...v8.5.0)
#### Minor Changes
- `pnpm patch-remove` command added [#6521](https://togithub.com/pnpm/pnpm/pull/6521).
#### Patch Changes
- `pnpm link -g ` should not modify the `package.json` file [#4341](https://togithub.com/pnpm/pnpm/issues/4341).
- The deploy command should not ask for confirmation to purge the `node_modules` directory [#6510](https://togithub.com/pnpm/pnpm/issues/6510).
- Show cyclic workspace dependency details [#5059](https://togithub.com/pnpm/pnpm/issues/5059).
- Node.js range specified through the `engines` field should match prerelease versions [#6509](https://togithub.com/pnpm/pnpm/pull/6509).
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.4.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.4.0)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.3.1...v8.4.0)
#### Minor Changes
- `pnpm publish` supports the `--provenance` CLI option [#6435](https://togithub.com/pnpm/pnpm/issues/6435).
#### Patch Changes
- Link the bin files of local workspace dependencies, when `node-linker` is set to `hoisted` [6486](https://togithub.com/pnpm/pnpm/issues/6486).
- Ask the user to confirm the removal of `node_modules` directory unless the `--force` option is passed.
- Do not create a `node_modules` folder with a `.modules.yaml` file if there are no dependencies inside `node_modules`.
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.3.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.3.1)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.3.0...v8.3.1)
#### Patch Changes
- Patch `node-fetch` to fix an error that happens on Node.js 20 [#6424](https://togithub.com/pnpm/pnpm/issues/6424).
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.3.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.3.0)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.2.0...v8.3.0)
#### Minor Changes
- A custom compression level may be specified for the `pnpm pack` command using the `pack-gzip-level` setting [#6393](https://togithub.com/pnpm/pnpm/issues/6393).
- Add `--check` flag to `pnpm dedupe`. No changes will be made to `node_modules` or the lockfile. Exits with a non-zero status code if changes are possible.
- `pnpm install --resolution-only` re-runs resolution to print out any peer dependency issues [#6411](https://togithub.com/pnpm/pnpm/pull/6411).
#### Patch Changes
- Warn user when `publishConfig.directory` of an injected workspace dependency does not exist [#6396](https://togithub.com/pnpm/pnpm/pull/6396).
- Use hard links to link the node executable on Windows machines [#4315](https://togithub.com/pnpm/pnpm/issues/4315).
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.2.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.2.0)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.1.1...v8.2.0)
#### Minor Changes
- Allow env variables to be specified with default values in `.npmrc`. This is a convention used by Yarn too.
Using `${NAME-fallback}` will return `fallback` if `NAME` isn't set. `${NAME:-fallback}` will return `fallback` if `NAME` isn't set, or is an empty string [#6018](https://togithub.com/pnpm/pnpm/issues/6018).
#### Patch Changes
- Add `-g` to mismatch registries error info when original command has `-g` option [#6224](https://togithub.com/pnpm/pnpm/issues/6224).
- Don't fail with EBUSY error when trying to copy a file from the store [#6201](https://togithub.com/pnpm/pnpm/issues/6201)
- `pnpm config get ` should print boolean values [#6360](https://togithub.com/pnpm/pnpm/issues/6360)
- Don't print an info message about linked dependencies if they are real linked dependencies specified via the `link:` protocol in `package.json` [#6372](https://togithub.com/pnpm/pnpm/issues/6372)
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.1.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.1.1)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.1.0...v8.1.1)
#### Patch Changes
- Repeat installation should work on a project that has a dependency with parentheses in the scope name [#6348](https://togithub.com/pnpm/pnpm/issues/6348).
- Error summary should be reported as expected.
- Update `@yarnpkg/shell` to fix issues in the shell emulator [#6320](https://togithub.com/pnpm/pnpm/issues/6320).
- Installation should not fail when there is a local dependency in a directory that starts with the `@` character [#6332](https://togithub.com/pnpm/pnpm/issues/6332).
- Registries are now passed to the `preResolution` hook.
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.1.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.1.0)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.0.0...v8.1.0)
#### Minor Changes
- A new setting has been added called `dedupe-direct-deps`, which is disabled by default. When set to `true`, dependencies that are already symlinked to the root `node_modules` directory of the workspace will not be symlinked to subproject `node_modules` directories. This feature was enabled by default in v8.0.0 but caused issues, so it's best to disable it by default [#6299](https://togithub.com/pnpm/pnpm/issues/6299).
- Add `ignore-workspace-cycles` to silence workspace cycle warning [#6308](https://togithub.com/pnpm/pnpm/pull/6308).
#### Patch Changes
- Print the right lowest supported Node.js version in the error message, when pnpm is executed with an old Node.js version [#6297](https://togithub.com/pnpm/pnpm/issues/6297).
- Improve the outdated lockfile error message [#6304](https://togithub.com/pnpm/pnpm/pull/6304).
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.0.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.0.0)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.32.5...v8.0.0)
We are excited to announce the latest release of pnpm! To install it, check the [installation page](https://pnpm.io/installation).
#### 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](https://pnpm.io/installation#using-a-standalone-script) or install the `@pnpm/exe` package.
##### Configuration Updates
- [`auto-install-peers`](https://pnpm.io/npmrc#auto-install-peers): enabled by default.
- [`dedupe-peer-dependents`](https://pnpm.io/npmrc#dedupe-peer-dependents): enabled by default.
- [`resolve-peers-from-workspace-root`](https://pnpm.io/npmrc#resolve-peers-from-workspace-root): enabled by default.
- [`save-workspace-protocol`](https://pnpm.io/npmrc#save-workspace-protocol): set to `rolling` by default.
- [`resolution-mode`](https://pnpm.io/npmrc#resolution-mode): set to `lowest-direct` by default.
- [`publishConfig.linkDirectory`](https://pnpm.io/package_json#publishconfiglinkdirectory): enabled by default.
Most of the configuration changes are related to peer dependencies. Most of these settings were implemented long ago, and we recommended them to users encountering peer dependency issues. The recently added `dedupe-peer-dependents` resolved many such problems. With these new defaults, pnpm will face significantly fewer issues during migration from other package managers.
##### Lockfile Modifications
- [Lockfile v6](https://togithub.com/pnpm/pnpm/pull/5810) is adopted. This new format improves the readability of the lockfile by removing hashes from package IDs. It also has some rearrangement of fields in the `importers` section. **The new `pnpm-lock.yaml` file is more resistant to git merge conflicts!**
- 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](https://pnpm.io/cli/deploy). The same logic is applied when [injecting packages](https://pnpm.io/package_json#dependenciesmetainjected). This behaviour can be changed by setting the [`deploy-all-files`](https://pnpm.io/8.x/npmrc#deploy-all-files) setting to `true` (Related issue [#5911](https://togithub.com/pnpm/pnpm/issues/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.
#### Migration Instructions
Before updating pnpm to v8 in your CI, regenerate your `pnpm-lock.yaml`. To upgrade your lockfile, run `pnpm install` and commit the changes. Existing dependencies will not be updated; however, due to configuration changes in pnpm v8, some missing peer dependencies may be added to the lockfile and some packages may get deduplicated.
You can commit the new lockfile even before upgrading Node.js in the CI, as pnpm v7 already supports the new lockfile format.
#### pnpm v7 Support
pnpm v7 will likely not receive any new features, but it will continue to get bug fixes for a few months and vulnerability fixes for at least a year.
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v7.32.5`](https://togithub.com/pnpm/pnpm/releases/tag/v7.32.5)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.32.4...v7.32.5)
#### Patch Changes
- `pnpm rebuild` should not fail when `node-linker` is set to `hoisted` and there are skipped optional dependencies [#6553](https://togithub.com/pnpm/pnpm/pull/6553).
- Expanded missing command error, including 'did you mean' [#6492](https://togithub.com/pnpm/pnpm/issues/6492).
- Normalize current working directory on Windows [#6524](https://togithub.com/pnpm/pnpm/issues/6524).
- Build projects in a workspace in correct order [#6568](https://togithub.com/pnpm/pnpm/pull/6568).
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v7.32.4`](https://togithub.com/pnpm/pnpm/releases/tag/v7.32.4)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.32.3...v7.32.4)
#### Patch Changes
- `pnpm link -g ` should not modify the `package.json` file [#4341](https://togithub.com/pnpm/pnpm/issues/4341).
- Node.js range specified through the `engines` field should match prerelease versions [#6509](https://togithub.com/pnpm/pnpm/pull/6509).
- `pnpm publish --otp` should work [#6514](https://togithub.com/pnpm/pnpm/issues/6514).
#### Our Gold Sponsors
#### Our Silver Sponsors
### [`v7.32.3`](https://togithub.com/pnpm/pnpm/releases/tag/v7.32.3)
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.32.2...v7.32.3)
#### Patch Changes
- Link the bin files of local workspace dependencies, when `node-linker` is set to `hoisted` [6486](https://togithub.com/pnpm/pnpm/issues/6486).
- Show cyclic workspace dependency details [#5059](https://togithub.com/pnpm/pnpm/issues/5059).
#### Our Gold Sponsors
This PR contains the following updates:
7.16.1->8.6.0Release Notes
pnpm/pnpm
### [`v8.6.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.5.1...v8.6.0) #### Minor Changes - Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created. A new field will now be present in the lockfile: `settings`. It will store the values of two settings: `autoInstallPeers` and `excludeLinksFromLockfile`. If someone tries to perform a `frozen-lockfile` installation and their active settings don't match the ones in the lockfile, then an error message will be thrown. The lockfile format version is bumped from v6.0 to v6.1. Related PR: [#6557](https://togithub.com/pnpm/pnpm/pull/6557) Related issue: [#6312](https://togithub.com/pnpm/pnpm/issues/6312) - A new setting, `exclude-links-from-lockfile`, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile. This setting was primarily added for use by [Bit CLI](https://togithub.com/teambit/bit), which links core aspects to `node_modules` from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations. #### Patch Changes - Don't print "Lockfile is up-to-date" message before finishing all the lockfile checks [#6544](https://togithub.com/pnpm/pnpm/issues/6544). - When updating dependencies, preserve the range prefix in aliased dependencies. So `npm:foo@1.0.0` becomes `npm:foo@1.1.0`. - Print a meaningful error when a project referenced by the `workspace:` protocol is not found in the workspace [#4477](https://togithub.com/pnpm/pnpm/issues/4477). - `pnpm rebuild` should not fail when `node-linker` is set to `hoisted` and there are skipped optional dependencies [#6553](https://togithub.com/pnpm/pnpm/pull/6553). - Peers resolution should not fail when a linked in dependency resolves a peer dependency. - Build projects in a workspace in correct order [#6568](https://togithub.com/pnpm/pnpm/pull/6568). #### Our Gold Sponsors