chore(deps): update pnpm to v7 #62
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov Report
@@ Coverage Diff @@
## master #62 +/- ##
=======================================
Coverage 90.86% 90.86%
=======================================
Files 61 61
Lines 3797 3797
Branches 728 728
=======================================
Hits 3450 3450
Misses 347 347
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
e28c2ef to
c20aac0
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
c20aac0 to
4aa733d
Compare
|
Test summary
Run details
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 Ignore NotificationAs this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 7.x releases. However, if you upgrade to 7.x manually then Renovate will reenable minor and patch updates automatically. 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.27.1->7.1.0Release Notes
pnpm/pnpm
v7.1.0Compare Source
Minor Changes
libcfield inpackage.json#4454.Patch Changes
pnpm setupshould update the config of the current shell, not the preferred shell.pnpm setupshould not override the PNPM_HOME env variable, unless--forceis used.pnpm dlxshould print messages about installation to stderr #1698.pnpm dlxshould work with git-hosted packages. For example:pnpm dlx gengjiawen/envinfo#4714.pnpm run --streamshould prefix the output with directory #4702Our Sponsors
Full Changelog: pnpm/pnpm@v7.0.1...v7.1.0
v7.0.1Compare Source
Patch Changes
pnpm dlxshould work when the bin name of the executed package isn't the same as the package name #4672.pnpm initcommand #4665.pnpm pruneworks in a workspace #4647.error#4669.pnpm prunedoes not remove hoisted dependencies #4647.Our Sponsors
Full Changelog: pnpm/pnpm@v7.0.0...v7.0.1
v7.0.0Compare Source
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 -- worldto theechoscript'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=./appsIn 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=truein.npmrc.The
NODE_PATHenv variable is not set in the command shims (the files innode_modules/.bin). This env variable was really long and frequently caused errors on Windows.Also, the
extend-node-pathsetting is removed.Related PR: #4253
The
embed-readmesetting isfalseby default.Side effects cache is turned on by default. To turn it off, use
side-effects-cache=false.The
npm_config_argvenv variable is not set for scripts #4153.pnpxis now just an alias ofpnpm 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 pkgwill 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 thePNPM_HOMEenv variable or theglobal-bin-dirsetting.pnpm packshould only pack a file as an executable if it's a bin or listed in thepublishConfig.executableFilesarray.-Wis not an alias of--ignore-workspace-root-checkanymore. Just use-wor--workspace-rootinstead, 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-permCLI option #3709.Local dependencies referenced through the
file:protocol are hard linked (not symlinked) #4408. If you need to symlink a dependency, use thelink:protocol instead.strict-peer-dependenciesistrueby default #4427.A prerelease version is always added as an exact version to
package.json. If thenextversion offoois1.0.0-beta.1then runningpnpm add foo@nextwill add this topackage.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-storeto<pnpm home directory>/storeOn Linux, by default it will be
~/.local/share/pnpm/storeOn Windows:
%LOCALAPPDATA%/pnpm/storeOn macOS:
~/Library/pnpm/storeRelated issue: #2574
4bed585: The next deprecated settings were removed: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 installin a directory that has nopackage.jsonfile in it (and in parent directories) #4609.Our Sponsors
Full Changelog: pnpm/pnpm@v6.31.0...v7.0.0
v6.32.12Compare Source
Patch Changes
pnpm dlxshould work when the bin name of the executed package isn't the same as the package name #4672.pnpm pruneworks in a workspace #4647.pnpm prunedoes not remove hoisted dependencies.pnpm dlxshould print messages about installation to stderr #1698.v6.32.11Compare Source
Patch Changes
pnpm publishshould work correctly in a workspace, when the latest npm CLI is installed #4348.node_modules/.ignoredsubfolder 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.10Compare Source
Patch Changes
Full Changelog: pnpm/pnpm@v6.32.9...v6.32.10
v6.32.9Compare 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 execis 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.8Compare Source
Patch Changes
Full Changelog: pnpm/pnpm@v6.32.7...v6.32.8
v6.32.7Compare Source
Patch Changes
auto-install-peerstotrueshould work.Full Changelog: pnpm/pnpm@v6.32.6...v6.32.7
v6.32.6Compare Source
Patch Changes
Full Changelog: pnpm/pnpm@v6.32.5...v6.32.6
v6.32.5Compare Source
v6.32.4Compare Source
Patch Changes
dependenciesMetafield in the manifest should be satisfied by a not set field in the lockfile #4463.package.json#4487.v6.32.3Compare 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 thefile: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.2Compare Source
Patch Changes
pnpm installwhen the lockfile is broken andnode-linkeris set tohoisted#4387.v6.32.1Compare Source
Patch Changes
onlyBuiltDependenciesshould work #4377. The newonlyBuiltDependenciesfeature was released with a bug in v6.32.0, so it didn't work.v6.32.0Compare Source
Minor Changes
A new setting is supported in the
pnpmsection of thepackage.jsonfile #4001.onlyBuiltDependenciesis 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"] } }-Fis 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
foois2.0.0, thenpnpm add fooinstallsfoo@^2.0.0. This behavior changes iffoois specified in an override:{ "pnpm": { "overrides": { "foo": "1.0.0" } } }In this case,
pnpm add foowill addfoo@1.0.0to the dependency. However, if a version is explicitly specifying, then the specified version will be used and the override will be ignored. Sopnpm add foo@0will install v0 and it doesn't matter what is in the overrides.Patch Changes
*, just replace any range with*.Full Changelog: pnpm/pnpm@v6.31.0...v6.32.0
v6.31.0Compare Source
Minor Changes
Added
--shell-mode/-coption support topnpm exec#4328--shell-mode: shell interpreter. See: https://github.com/sindresorhus/execa/tree/484f28de7c35da5150155e7a523cbb20de161a4f#shellUsage example:
{ "scripts": { "check": " pnpm -r --shell-mode exec -- echo \"\\$PNPM_PACKAGE_NAME\"" } }Patch Changes
publishConfigwhen thepackorpublishcommands are used #4311pnpx,pnpm dlx,pnpm create, andpnpm execcommands should set thenpm_config_user_agentenv variable #3985.What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v6.30.1...v6.31.0
v6.30.1Compare 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.0Compare Source
Minor Changes
v6.29.2Compare Source
Patch Changes
node_modulesdirectories inside injected dependencies should not be overwritten #4299.v6.29.1Compare Source
Patch Changes
node_modules.v6.29.0Compare Source
Minor Changes
update-notifierconfiguration option #4158.Patch Changes
v6.28.0Compare Source
Minor Changes
embed-readme. Whenfalse,pnpm publishdoesn't save the readme file's content topackage.jsonbefore publish #4265.Patch Changes
pnpm execshould look for the executed command in thenode_modules/.bindirectory that is relative to the current working directory. Only after that should it look for the executable in the workspace root.v6.27.2Compare 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.