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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency @pnpm/lockfile-file to v7 #418

Merged
merged 1 commit into from
Jan 16, 2023
Merged

chore(deps): update dependency @pnpm/lockfile-file to v7 #418

merged 1 commit into from
Jan 16, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 14, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@pnpm/lockfile-file (source) 6.0.5 -> 7.0.2 age adoption passing confidence

Release Notes

pnpm/pnpm

v7.0.1

Compare Source

Patch Changes
  • Use Yarn's compatibility database to patch broken packages in the ecosystem with package extensions #​4676.
  • pnpm dlx should work when the bin name of the executed package isn't the same as the package name #​4672.
  • Throw an error if arguments are passed to the pnpm init command #​4665.
  • pnpm prune works in a workspace #​4647.
  • Do not report request retry warnings when loglevel is set to error #​4669.
  • pnpm prune does not remove hoisted dependencies #​4647.
Our Sponsors
New Contributors

Full Changelog: pnpm/pnpm@v7.0.0...v7.0.1

v7.0.0

Major Changes

  • Node.js 12 is not supported.

  • When using pnpm run <script>, all command line arguments after the script name are now passed to the script's argv, even --.
    For example, the command below will now pass --hello -- world to the echo script's argv:
    pnpm run echo --hello -- world
    Previously, flagged arguments (e.g. --silent) were interpreted as pnpm arguments unless -- came before it.
    If you want to pass options to pnpm, place them before the script name. For instance:
    pnpm --workspace-root --silent run echo --hello -- world
    Read more details about this in our docs.
    Related PR: #​4290

  • The root package is excluded by default, when running pnpm -r exec|run|add #​2769.

  • Filtering by path is done by globs.

    In pnpm v6, in order to pick packages under a certain directory, the following filter was used: --filter=./apps

    In pnpm v7, a glob should be used: --filter=./apps/**

    For easier upgrade, we have also added a setting to turn back filtering as it was in v6. Just set legacy-dir-filtering=true in .npmrc.

  • The NODE_PATH env variable is not set in the command shims (the files in node_modules/.bin). This env variable was really long and frequently caused errors on Windows.

    Also, the extend-node-path setting is removed.

    Related PR: #​4253

  • The embed-readme setting is false by default.

  • Side effects cache is turned on by default. To turn it off, use side-effects-cache=false.

  • The npm_config_argv env variable is not set for scripts #​4153.

  • pnpx is now just an alias of pnpm dlx.

    If you want to just execute the command of a dependency, run pnpm <cmd>. For instance, pnpm eslint.

    If you want to install and execute, use pnpm dlx <pkg name>.

  • pnpm install -g pkg will add the global command only to a predefined location. pnpm will not try to add a bin to the global Node.js or npm folder. To set the global bin directory, either set the PNPM_HOME env variable or the global-bin-dir setting.

  • pnpm pack should only pack a file as an executable if it's a bin or listed in the publishConfig.executableFiles array.

  • -W is not an alias of --ignore-workspace-root-check anymore. Just use -w or --workspace-root instead, which will also allow to install dependencies in the root of the workspace.

  • Allow to execute a lifecycle script in a directory that doesn't match the package's name. Previously this was only allowed with the --unsafe-perm CLI option #​3709.

  • Local dependencies referenced through the file: protocol are hard linked (not symlinked) #​4408. If you need to symlink a dependency, use the link: protocol instead.

  • strict-peer-dependencies is true by default #​4427.

  • A prerelease version is always added as an exact version to package.json. If the next version of foo is 1.0.0-beta.1 then running pnpm add foo@next will add this to package.json:

    {
  "dependencies": {
    "foo": "1.0.0-beta.1"
  }
}

    PR: #​4435

  • Dependencies of the root workspace project are not used to resolve peer dependencies of other workspace projects #​4469.

  • Don't hoist types by default to the root of node_modules #​4459.

  • Any package with "prettier" in its name is hoisted.

  • Changed the location of the global store from ~/.pnpm-store to <pnpm home directory>/store

    On Linux, by default it will be ~/.local/share/pnpm/store
    On Windows: %LOCALAPPDATA%/pnpm/store
    On macOS: ~/Library/pnpm/store

    Related issue: #​2574

    There is no migration script for moving the global packages from the old location to the old one. Just reinstall all your global packages with pnpm v7.

  • 4bed585: The next deprecated settings were removed:

    • frozen-shrinkwrap
    • prefer-frozen-shrinkwrap
    • shared-workspace-shrinkwrap
    • shrinkwrap-directory
    • lockfile-directory
    • shrinkwrap-only
    • store

  • Use a base32 hash instead of a hex to encode too long dependency paths inside node_modules/.pnpm #​4552.

  • New setting added: git-shallow-hosts. When cloning repositories from "shallow-hosts", pnpm will use shallow cloning to fetch only the needed commit, not all the history #​4548.

  • Lockfile version bumped to v5.4.

  • Exit with an error when running pnpm install in a directory that has no package.json file in it (and in parent directories) #​4609.

Our Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v6.31.0...v7.0.0

Configuration

📅 Schedule: Branch creation - "every weekend" (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.

@codecov-commenter
Copy link

Codecov Report

Base: 64.60% // Head: 64.60% // No change to project coverage 👍

Coverage data is based on head (214aa1e) compared to base (41e75c3).
Patch has no changes to coverable lines.

Additional details and impacted files 
@@           Coverage Diff           @@
##           master     #418   +/-   ##
=======================================
  Coverage   64.60%   64.60%           
=======================================
  Files         105      105           
  Lines        2961     2961           
  Branches      369      369           
=======================================
  Hits         1913     1913           
  Misses       1002     1002           
  Partials       46       46

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@ddadaal ddadaal merged commit 02fdf48 into master Jan 16, 2023
@ddadaal ddadaal deleted the renovate/pnpm-lockfile-file-7.x branch January 16, 2023 03:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@codecov-commenter @ddadaal