v6.24.0 #4127
zkochan
started this conversation in
Show and tell
v6.24.0
#4127
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Minor Changes
Peer dependency issues are grouped and rendered in a nice hierarchy view.
This is how the peer dependency issues were printed in previous versions:
This is how they are displayed in pnpm v6.24:
New option added for:
node-mirror:<releaseDir>
#4083. The string value of this dynamic option is used as the base URL for downloading node whenuse-node-version
is specified. The<releaseDir>
portion of this argument can be any dir inhttps://nodejs.org/download
. Which<releaseDir>
dynamic config option gets selected depends on the value ofuse-node-version
. If 'use-node-version' is a simplex.x.x
version string,<releaseDir>
becomesrelease
andnode-mirror:release
is read. Defaults tohttps://nodejs.org/download/<releaseDir>/
.927c4a0: A new option
--aggregate-output
forappend-only
reporter is added. It aggregates lifecycle logs output for each command that is run in parallel, and only prints command logs when command is finished.Related discussion: #4070.
Patch Changes
Don't fail when the version of a package in the store is not a semver version #4077.
pnpm store prune
should not fail if there are unexpected subdirectories in the content-addressable store #4072.Don't make unnecessary retries when fetching Git-hosted packages #2731.
pnpm should read the auth token of a github-registry-hosted package, when the registry path contains the owner #4034.
So this should work:
When
strict-peer-dependencies
is used, don't fail on the first peer dependency issue. Print all the peer dependency issues and then stop the installation process #4082.When sorting workspace projects, don't ignore the manifests of those that don't have a version field #3933.
This discussion was created from the release v6.24.0.
Beta Was this translation helpful? Give feedback.
All reactions