chore(deps): update pnpm to v7 #107
Merged
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}
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
64ea4a0 to
2be616d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
2be616d to
c98dabd
Compare
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.33.1->7.5.2Release Notes
pnpm/pnpm
v7.5.2Compare Source
Patch Changes
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.1...v7.5.2
v7.5.1Compare Source
Patch Changes
node_modules#4988.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.0...v7.5.1
v7.5.0Compare Source
Minor Changes
A new value
rollingfor optionsave-workspace-protocol. When selected, pnpm will save workspace versions using a rolling alias (e.g."foo": "workspace:^") instead of pinning the current version number (e.g."foo": "workspace:^1.0.0"). Usage example, in the root of your workspace, create a.npmrcwith the following content:Patch Changes
pnpm remove <pkg>should not fail in a workspace that has patches #4954pnpm env useshould throw an error on a system that use the MUSL libc.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.4.1...v7.5.0
v7.4.1Compare Source
Patch Changes
pnpm installin a workspace with patches should not fail when doing partial installation #4954.--lockfile-onlyis used. Even iffrozen-lockfileistrue#4951.patchedDependenciesfield topnpm-lock.yaml.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.4.0...v7.4.1
v7.4.0Compare Source
Minor Changes
Dependencies patching is possible via the
pnpm.patchedDependenciesfield of thepackage.json.To patch a package, the package name, exact version, and the relative path to the patch file should be specified. For instance:
{ "pnpm": { "patchedDependencies": { "eslint@1.0.0": "./patches/eslint@1.0.0.patch" } } }Two new commands added:
pnpm patchandpnpm patch-commit.pnpm patch <pkg>prepares a package for patching. For instance, if you want to patch express v1, run:pnpm will create a temporary directory with
express@1.0.0that you can modify with your changes.Once you are read with your changes, run:
This will create a patch file and write it to
<project>/patches/express@1.0.0.patch.Also, it will reference this new patch file from the
patchedDependenciesfield inpackage.json:{ "pnpm": { "patchedDependencies": { "express@1.0.0": "patches/express@1.0.0.patch" } } }A new experimental command added:
pnpm deploy. The deploy command takes copies a project from a workspace and installs all of its production dependencies (even if some of those dependencies are other projects from the workspace).For example, the new command will deploy the project named
footo thedistdirectory in the root of the workspace:package-import-methodsupports a new option:clone-or-copy.New setting added:
include-workspace-root. When it is set totrue, therun,exec,add, andtestcommands will include the root package, when executed recursively #4906Patch Changes
Don't crash when
pnpm update --interactiveis cancelled with Ctrl+c.The
use-node-versionsetting should work with prerelease Node.js versions. For instance:Return early when the lockfile is up-to-date.
Resolve native workspace path for case-insensitive file systems #4904.
Don't link local dev dependencies, when prod dependencies should only be installed.
pnpm audit --fixshould not add an override for a vulnerable package that has no fixes released.Update the compatibility database.
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.3.0...v7.4.0
v7.3.0Compare Source
Minor Changes
A new setting added:
pnpm.peerDependencyRules.allowAny.allowAnyis an array of package name patterns, any peer dependency matching the pattern will be resolved from any version, regardless of the range specified inpeerDependencies. For instance:{ "pnpm": { "peerDependencyRules": { "allowAny": ["@​babel/*", "eslint"] } } }The above setting will mute any warnings about peer dependency version mismatches related to
@babel/packages oreslint.The
pnpm.peerDependencyRules.ignoreMissingsetting may accept package name patterns. So you may ignore any missing@babel/*peer dependencies, for instance:{ "pnpm": { "peerDependencyRules": { "ignoreMissing": ["@​babel/*"] } } }Experimental. New settings added:
use-git-branch-lockfile,merge-git-branch-lockfiles,merge-git-branch-lockfiles-branch-pattern#4475.Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.2.1...v7.3.0
v7.2.1Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.2.0...v7.2.1
v7.2.0Compare Source
Minor Changes
A new setting is supported for ignoring specific deprecation messages:
pnpm.allowedDeprecatedVersions. The setting should be provided in thepnpmsection of the rootpackage.jsonfile. The below example will mute any deprecation warnings about therequestpackage and warnings aboutexpressv1:{ "pnpm": { "allowedDeprecatedVersions": { "request": "*", "express": "1" } } }Related issue: #4306
Related PR: #4864
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.9...v7.2.0
v7.1.9Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.8...v7.1.9
v7.1.8Compare Source
Patch Changes
package.jsonfile #4822.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.7...v7.1.8
v7.1.7Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.6...v7.1.7
v7.1.6Compare Source
Patch Changes
auto-install-peersis set totrue#4796.NODE_ENV=production pnpm install --devshould only install dev deps #4745.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.5...v7.1.6
v7.1.5Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.4...v7.1.5
v7.1.4Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.3...v7.1.4
v7.1.3Compare Source
Patch Changes
auto-install-peersis set totrue, automatically install missing peer dependencies without writing them topackage.jsonas dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #4776.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.2...v7.1.3
v7.1.2Compare Source
Patch Changes
pnpm setupshould not fail on Windows ifPNPM_HOMEis not yet in the system registry #4757pnpm dlxshouldn't modify the lockfile in the current working directory #4743.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.1...v7.1.2
v7.1.1Compare Source
Patch Changes
node_modules/.pnpmand inside the global store #4716pnpm create <pkg>should be passed to the executed create app package. Sopnpm create next-app --typescriptshould work`.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.0...v7.1.1
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
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:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR has been generated by Mend Renovate. View repository job log here.