Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update pnpm to v9 #5581

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

chore(deps): update pnpm to v9 #5581

wants to merge 5 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) 8.10.3 -> 9.0.5 age adoption passing confidence

Release Notes

pnpm/pnpm (pnpm)

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

v9.0.1

Compare Source

v9.0.0

Compare Source

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 or install the @pnpm/exe package.

  • Configuration updates:

    • dedupe-injected-deps: enabled by default.
    • 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.
    • hoist-workspace-packages: enabled by default.
    • 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.
  • Dependency resolution changes:

    • Correct resolution of peer dependencies that have their own peer dependencies.
      Related issue: #​7444.
      Related PR: #​7606.
    • Optional peer dependencies may be resolved from any packages in the dependency graph #​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.

  • 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.

  • When installing git-hosted dependencies, only pick the files that would be packed with the package #​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.
    Related PR: #​7487.

  • node-gyp updated to version 10.

  • PowerShell completion support added #​7597.

  • Support node-options option inside .npmrc file when running scripts #​7596.

  • Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported: <registryURL>:certfile, <registryURL>:keyfile, and <registryURL>: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.
    Related PR: #​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.

  • 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.

  • Added cache for pnpm dlx #​5277.

Patch Changes
  • Package tarballs are not downloaded during --lockfile-only installation #​1328.
  • Peer dependency rules should only affect reporting, not data in the lockfile #​7758.
  • Link overrides should be able to use absolute path #​7749.
  • pnpm dlx should not read settings from the current working directory #​7916.
Platinum Sponsors
Gold Sponsors
Our Silver Sponsors

v8.15.7

Compare Source

v8.15.6

Compare Source

Patch Changes

  • The exit code of the child process should be preserved on pnpm run #​7817.
  • When sorting packages in a workspace, take into account workspace dependencies specified as peerDependencies #​7813.
  • Add --ignore-scripts argument to prune command #​7836.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v8.15.5

Compare Source

v8.15.4

Compare Source

v8.15.3

Compare Source

Patch Changes

  • Remove vulnerable "ip" package from the dependencies #​7652.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.2

Compare Source

Patch Changes

  • When purging multiple node_modules directories, pnpm will no longer print multiple prompts simultaneously.
  • Don't print an unnecessary warning when adding new dependencies to a project that uses hoisted node_modules.
  • Linking globally the command of a package that has no name in package.json #​4761.
  • Installation should work with lockfile created by pnpm v9.0.0-alpha.4

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.1

Compare Source

Patch Changes

  • Use the object-hash library instead of node-object-hash for hashing keys of side-effects cache #​7591.
  • bundledDependencies should never be added to the lockfile with false as the value #​7576.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.0

Compare Source

Minor Changes

  • When the license field does not exist in package.json but a license file exists, try to match and extract the license name #​7530.

Patch Changes

  • Running pnpm update -r --latest will no longer downgrade prerelease dependencies #​7436.
  • --aggregate-output should work on scripts executed from the same project #​7556.
  • Prefer hard links over reflinks on Windows as they perform better #​7564.
  • Reduce the length of the side-effects cache key. Instead of saving a stringified object composed from the dependency versions of the package, use the hash calculated from the said object #​7563.
  • Throw an error if pnpm update --latest runs with arguments containing versions specs. For instance, pnpm update --latest foo@next is not allowed #​7567.
  • Don't fail in Windows CoW if the file already exists #​7554.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.3

Compare Source

Patch Changes

  • pnpm pack should work as expected when "prepack" modifies the manifest #​7558.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.2

Compare Source

Patch Changes

  • Registry configuration from previous installation should not override current settings #​7507.
  • pnpm dlx should not fail, when executed from package.json "scripts" 7424.
  • A git-hosted dependency should not be added to the store if it failed to be built #​7407.
  • pnpm publish should pack "main" file or "bin" files defined in "publishConfig" #​4195.

Platinum Sponsors


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.

Copy link

netlify bot commented Apr 22, 2024

Deploy Preview for fastidious-cascaron-4ded94 ready!

Name Link
🔨 Latest commit cbe2fcc
🔍 Latest deploy log https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/662851832d7de10008b78ab8
😎 Deploy Preview https://deploy-preview-5581--fastidious-cascaron-4ded94.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor Author

renovate bot commented Apr 22, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

"description": "Next generation testing framework powered by Vite",
"engines": {
"node": "^18.0.0 || >=20.0.0"
},
"scripts": {
"ci": "ni && nr typecheck && nr lint && nr build && nr test:all",
"ci:docs": "pnpm run build && pnpm run docs:build",
"build": "pnpm -r --filter='./packages/**' run build",
"build": "pnpm -r --filter @vitest/ui --filter='./packages/**' run build",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now I did the same trick from #5499 (comment) for the cyclic build issue.

I'm not sure if we should fix something more fundamentally.

@patak-dev
Copy link
Member

We're going to wait in Vite a bit before updating to pnpm v9. Maybe it would be good to coordinate and update Vite and Vitest together

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants