chore(deps): update pnpm to v6.32.13

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	6.27.1 -> 6.32.13

---

Release Notes

pnpm/pnpm

v6.32.13

Compare Source

Patch Changes

• pnpm setup should update the config of the current shell, not the preferred shell.
• pnpm dlx should work with git-hosted packages. For example: pnpm dlx gengjiawen/envinfo #​4714.
• pnpm setup should not override the PNPM_HOME env variable on Windows, unless --force is used.
• All arguments after pnpm create <pkg> should be passed to the executed create app package. So pnpm create next-app --typescript should work`.
• pnpm run --stream should prefix the output with directory #​4702

Full Changelog: pnpm/pnpm@v6.32.12...v6.32.13

v6.32.12

Compare Source

Patch Changes

• Use Yarn's compatibility database to patch broken packages in the ecosystem with package extensions.
• pnpm dlx should work when the bin name of the executed package isn't the same as the package name #​4672.
• pnpm prune works in a workspace #​4647.
• pnpm prune does not remove hoisted dependencies.
• pnpm dlx should print messages about installation to stderr #​1698.

v6.32.11

Compare Source

Patch Changes

• pnpm publish should work correctly in a workspace, when the latest npm CLI is installed #​4348.
• Installation shouldn't fail when a package from node_modules is moved to the node_modules/.ignored subfolder and a package with that name is already present in `node_modules/.ignored' #​4626.

Full Changelog: pnpm/pnpm@v6.32.10...v6.32.11

v6.32.10

Compare Source

Patch Changes

• It should be possible to use a chain of local file dependencies #​4611.
• Filtering by directory should work with directories that have unicode chars in the name #​4595.

Full Changelog: pnpm/pnpm@v6.32.9...v6.32.10

v6.32.9

Compare Source

Patch Changes

• Fix an error with peer resolutions, which was happening when there was a circular dependency and another dependency that had the name of the circular dependency as a substring.

• When pnpm exec is running a command in a workspace project, the commands that are in the dependencies of that workspace project should be in the PATH #​4481.

• Hide "WARN deprecated" messages on loglevel error #​4507

  Don't show the progress bar when loglevel is set to warn or error.

Full Changelog: pnpm/pnpm@v6.32.8...v6.32.9

v6.32.8

Compare Source

Patch Changes

• Don't check the integrity of the store with the package version from the lockfile, when the package was updated #​4580.
• Don't update a direct dependency that has the same name as a dependency in the workspace, when adding a new dependency to a workspace project #​4575.

Full Changelog: pnpm/pnpm@v6.32.7...v6.32.8

v6.32.7

Compare Source

Patch Changes

• Setting the auto-install-peers to true should work.

Full Changelog: pnpm/pnpm@v6.32.6...v6.32.7

v6.32.6

Compare Source

Patch Changes

• Linked in dependencies should be considered when resolving peer dependencies #​4541.
• Peer dependency should be correctly resolved from the workspace, when it is declared using a workspace protocol #​4529.

Full Changelog: pnpm/pnpm@v6.32.5...v6.32.6

v6.32.5

Compare Source

v6.32.4

Compare Source

Patch Changes

• Show a friendly error message when it is impossible to get the current Git branch name during publish #​4488.
• When checking if the lockfile is up-to-date, an empty dependenciesMeta field in the manifest should be satisfied by a not set field in the lockfile #​4463.
• It should be possible to reference a workspace project that has no version specified in its package.json #​4487.

v6.32.3

Compare Source

Patch Changes

• 4941f31: The location of an injected directory dependency should be correctly located, when there is a chain of local dependencies (declared via the file: protocol`).

  The next scenario was not working prior to the fix. There are 3 projects in the same folder: foo, bar, qar.

  foo/package.json:

  {
    "name": "foo",
    "dependencies": {
      "bar": "file:../bar"
    },
    "dependenciesMeta": {
      "bar": {
        "injected": true
      }
    }
  }

  bar/package.json:

  {
    "name": "bar",
    "dependencies": {
      "qar": "file:../qar"
    },
    "dependenciesMeta": {
      "qar": {
        "injected": true
      }
    }
  }

  qar/package.json:

  {
    "name": "qar"
  }

  Related PR: #​4415.

v6.32.2

Compare Source

Patch Changes

• In order to guarantee that only correct data is written to the store, data from the lockfile should not be written to the store. Only data directly from the package tarball or package metadata #​4395.
• Throw a meaningful error message on pnpm install when the lockfile is broken and node-linker is set to hoisted #​4387.

v6.32.1

Compare Source

Patch Changes

• onlyBuiltDependencies should work #​4377. The new onlyBuiltDependencies feature was released with a bug in v6.32.0, so it didn't work.

v6.32.0

Compare Source

Minor Changes

• A new setting is supported in the pnpm section of the package.json file #​4001. onlyBuiltDependencies is an array of package names that are allowed to be executed during installation. If this field exists, only mentioned packages will be able to run install scripts.

  {
    "pnpm": {
      "onlyBuiltDependencies": ["fsevents"]
    }
  }

• -F is a short alias of --filter #​3467.

• When adding a new dependency, use the version specifier from the overrides, when present #​4313.

  Normally, if the latest version of foo is 2.0.0, then pnpm add foo installs foo@^2.0.0. This behavior changes if foo is specified in an override:

  {
    "pnpm": {
      "overrides": {
        "foo": "1.0.0"
      }
    }
  }

  In this case, pnpm add foo will add foo@1.0.0 to the dependency. However, if a version is explicitly specifying, then the specified version will be used and the override will be ignored. So pnpm add foo@0 will install v0 and it doesn't matter what is in the overrides.

Patch Changes

• Ignore case, when verifying package name in the store #​4367.
• When a peer dependency range is extended with *, just replace any range with *.
• When some dependency types are skipped, let the user know via the installation summary.

Full Changelog: pnpm/pnpm@v6.31.0...v6.32.0

v6.31.0

Compare Source

Minor Changes

• Added --shell-mode/-c option support to pnpm exec #​4328

  • --shell-mode: shell interpreter. See: https://github.com/sindresorhus/execa/tree/484f28de7c35da5150155e7a523cbb20de161a4f#shell

  Usage example:

  pnpm -r --shell-mode exec -- echo \"\$PNPM_PACKAGE_NAME\"
  pnpm -r -c exec -- echo \"\$PNPM_PACKAGE_NAME\"

  {
    "scripts": {
      "check": " pnpm -r --shell-mode exec -- echo \"\\$PNPM_PACKAGE_NAME\""
    }
  }

Patch Changes

• Remove meaningless keys from publishConfig when the pack or publish commands are used #​4311
• The pnpx, pnpm dlx, pnpm create, and pnpm exec commands should set the npm_config_user_agent env variable #​3985.

What's Changed

• fix: the dlx and create commands should set npm_config_user_agent by @​zkochan in https://github.com/pnpm/pnpm/pull/4317
• refactor(publish): remove meaningless key in publishConfig by @​BlackHole1 in https://github.com/pnpm/pnpm/pull/4334
• feat(exec): support shell interpreter by @​BlackHole1 in https://github.com/pnpm/pnpm/pull/4328

New Contributors

• @​BlackHole1 made their first contribution in https://github.com/pnpm/pnpm/pull/4334

Full Changelog: pnpm/pnpm@v6.30.1...v6.31.0

v6.30.1

Compare Source

Patch Changes

• This fixes an issue introduced in pnpm v6.30.0.

  When a package is not linked to node_modules, no info message should be printed about it being "relinked" from the store #​4314.

v6.30.0

Compare Source

Minor Changes

• When checking that a package is linked from the store, check the existence of the package and read its stats with a single filesystem operation #​4304.

v6.29.2

Compare Source

Patch Changes

• node_modules directories inside injected dependencies should not be overwritten #​4299.

v6.29.1

Compare Source

Patch Changes

• Installation should not hang when there are broken symlinks in node_modules.

v6.29.0

Compare Source

Minor Changes

• Add support of the update-notifier configuration option #​4158.

Patch Changes

• A package should be able to be a dependency of itself.

v6.28.0

Compare Source

Minor Changes

• New option added: embed-readme. When false, pnpm publish doesn't save the readme file's content to package.json before publish #​4265.

Patch Changes

• pnpm exec should look for the executed command in the node_modules/.bin directory that is relative to the current working directory. Only after that should it look for the executable in the workspace root.
• Injected dependencies should work properly in projects that use the hoisted node linker #​4259.

v6.27.2

Compare Source

---

Configuration

📅 Schedule: 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, click this checkbox.

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
pintorajs	✅ Ready (Inspect)	Visit Preview	May 14, 2022 at 1:04AM (UTC)

[codecov]

Codecov Report

Merging #57 (25280c7) into master (45311c6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #57   +/-   ##
=======================================
  Coverage   90.86%   90.86%           
=======================================
  Files          61       61           
  Lines        3797     3797           
  Branches      728      728           
=======================================
  Hits         3450     3450           
  Misses        347      347           

Flag	Coverage Δ
unittests	90.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
packages/pintora-diagrams/src/util/graph.ts	91.89% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update acfda83...25280c7. Read the comment docs.

[cypress]

---

Test summary

7 • 0 • 0 • 0

---

Run details

Project	pintora
Status	Passed
Commit	c59c650 ℹ️
Started	May 14, 2022 1:02 AM
Ended	May 14, 2022 1:04 AM
Duration	01:23 💡
OS	Linux Ubuntu - 20.04
Browser	Electron 94

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (6.32.13). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.