build(deps): update pnpm to v8 #121

renovate · 2023-03-31T14:54:38Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`7.28.0` -> `8.1.0`

Release Notes

pnpm/pnpm

`v8.1.0`

Compare Source

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.
Add ignore-workspace-cycles to silence workspace cycle warning #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.
Improve the outdated lockfile error message #6304.

Our Gold Sponsors

Our Silver Sponsors

`v8.0.0`

Compare Source

We are excited to announce the latest release of pnpm! To install it, check the installation page.

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.
resolve-peers-from-workspace-root: enabled by default.
save-workspace-protocol: set to rolling by default.
resolution-mode: set to lowest-direct by default.
publishConfig.linkDirectory: 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 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. 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.

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.30.5`

Compare Source

Patch Changes

pnpm audit should work even if there are no package.json file, just a pnpm-lock.yaml file.
Dedupe direct dependencies after hoisting.
Don't remove automatically installed peer dependencies from the root workspace project, when dedupe-peer-dependents is true #6154.

Our Gold Sponsors

Our Silver Sponsors

`v7.30.4`

Compare Source

`v7.30.3`

Compare Source

Patch Changes

Should use most specific override rule when multiple rules match the same target #6210.
Fix regression introduced in v7.30.1 #6271.

Our Gold Sponsors

Our Silver Sponsors

`v7.30.2`

Compare Source

`v7.30.1`

Compare Source

Patch Changes

Don't write the pnpm-lock.yaml file if it has no changes and pnpm install --frozen-lockfile was executed #6158.
Fix git-hosted dependencies referenced via git+ssh that use semver selectors #6239.
When publish some package throws an error, the exit code should be non-zero #5528.
Only three paths are displayed in pnpm audit output #6203
Aliased packages should be used to resolve peer dependencies too #4301.

Our Gold Sponsors

Our Silver Sponsors

`v7.30.0`

Compare Source

Minor Changes

Allow to set a custom directory for storing patch files via the patches-dir setting #6215

Patch Changes

New directories should be prepended to NODE_PATH in command shims, not appended.
Retry copying file on EBUSY error #6201.

Our Gold Sponsors

Our Silver Sponsors

`v7.29.3`

Compare Source

Patch Changes

Command shim should not set higher priority to the node_modules/.pnpm/node_modules directory through the NODE_PATH env variable, then the command's own node_modules directory #5176.
extend-node-path is set back to true by default. It was set to false in v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extending NODE_PATH. We have fixed the Jest issue with a different solution #6213.

Our Gold Sponsors

Our Silver Sponsors

`v7.29.2`

Compare Source

`v7.29.1`

Compare Source

Patch Changes

Settings related to authorization should be set/deleted by npm CLI #6181.

Our Gold Sponsors

Our Silver Sponsors

`v7.29.0`

Compare Source

Minor Changes

A new setting is now supported: dedupe-peer-dependents.

When this setting is set to true, packages with peer dependencies will be deduplicated after peers resolution.

For instance, let's say we have a workspace with two projects and both of them have webpack in their dependencies. webpack has esbuild in its optional peer dependencies, and one of the projects has esbuild in its dependencies. In this case, pnpm will link two instances of webpack to the node_modules/.pnpm directory: one with esbuild and another one without it:
```
node_modules
  .pnpm
    [email protected][email protected]
    [email protected]
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/[email protected]/node_modules/webpack
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/[email protected][email protected]/node_modules/webpack
    esbuild
```
This makes sense because webpack is used in two projects, and one of the projects doesn't have esbuild, so the two projects cannot share the same instance of webpack. However, this is not what most developers expect, especially since in a hoisted node_modules, there would only be one instance of webpack. Therefore, you may now use the dedupe-peer-dependents setting to deduplicate webpack when it has no conflicting peer dependencies (explanation at the end). In this case, if we set dedupe-peer-dependents to true, both projects will use the same webpack instance, which is the one that has esbuild resolved:
```
node_modules
  .pnpm
    [email protected][email protected]
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/[email protected][email protected]/node_modules/webpack
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/[email protected][email protected]/node_modules/webpack
    esbuild
```
What are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:
```
node_modules
  .pnpm
    [email protected][email protected][email protected]
    [email protected][email protected]
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/[email protected]/node_modules/webpack
    react (v17)
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/[email protected][email protected]/node_modules/webpack
    esbuild
    react (v16)
```
In this case, we cannot dedupe webpack as webpack has react in its peer dependencies and react is resolved from two different versions in the context of the two projects.

Patch Changes

The configuration added by pnpm setup should check if the pnpm home directory is already in the PATH before adding to the PATH.

Before this change, this code was added to the shell:

export PNPM_HOME="$HOME/Library/pnpm"
export PATH="$PNPM_HOME:$PATH"

Now this will be added:

export PNPM_HOME="$HOME/Library/pnpm"
case ":$PATH:" in
  *":$PNPM_HOME:"*) ;;
  *) export PATH="$PNPM_HOME:$PATH" ;;
esac

Add skipped status in exec report summary when script is missing #6139.
pnpm env -g should fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.
Should not throw an error when local dependency use file protocol #6115.
Fix the incorrect error block when subproject has been patched #6183

Our Gold Sponsors

Our Silver Sponsors

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" in timezone Australia/Sydney, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate bot added the dependencies label Mar 31, 2023

build(deps): update pnpm to v8

7cfcfd3

renovate bot force-pushed the renovate/pnpm-8.x branch from 2d3ccc0 to 7cfcfd3 Compare April 1, 2023 23:54

jcwillox approved these changes Apr 3, 2023

View reviewed changes

jcwillox merged commit 3525559 into main Apr 3, 2023

jcwillox deleted the renovate/pnpm-8.x branch April 3, 2023 01:40

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

build(deps): update pnpm to v8 #121

build(deps): update pnpm to v8 #121

renovate bot commented Mar 31, 2023 •

edited

Loading

build(deps): update pnpm to v8 #121

build(deps): update pnpm to v8 #121

Conversation

renovate bot commented Mar 31, 2023 • edited Loading

Release Notes

Minor Changes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Major Changes

Node.js 14 Support Discontinued

Configuration Updates

Lockfile Modifications

Other Changes

Migration Instructions

pnpm v7 Support

Our Gold Sponsors

Our Silver Sponsors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Minor Changes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Minor Changes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Configuration

renovate bot commented Mar 31, 2023 •

edited

Loading