This PR contains the following updates:
Release Notes
pnpm/pnpm (pnpm)
Compare Source
Patch Changes
- Remove vulnerable "ip" package from the dependencies #7652.
Compare Source
Patch Changes
- Authorization token should be found in the configuration, when the requested URL is explicitly specified with a default port (443 on HTTPS or 80 on HTTP) #6863.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
- Temporarily revert the fix to #6805 to fix the regression it caused #6827.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
- When the same file is appended multiple times into a tarball, the last occurrence is selected when unpacking the tarball.
- Added support for
publishConfig.registry in package.json for publishing #6775.
- Fixed a bug in which pnpm passed the wrong scheme to
git ls-remote, causing a fallback to git+ssh and resulting in a 'host key verification failed' issue #6805
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
- Improve the performance of searching for auth tokens.
- Installation of a git-hosted dependency without
package.json should not fail, when the dependency is read from cache #6721.
- Local workspace bin files that should be compiled first are linked to dependent projects after compilation #1801.
- Prefer versions found in parent package dependencies only #6737.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
- In cases where both aliased and non-aliased dependencies exist to the same package, non-aliased dependencies will be used for resolving peer dependencies, addressing issue #6588.
- Don't crash when the APPDATA env variable is not set on Windows #6659.
- Don't fail when a package is archived in a tarball with malformed tar headers #5362.
- Peer dependencies of subdependencies should be installed, when
node-linker is set to hoisted #6680.
- Ignore the port in the URL, while searching for authentication token in the
.npmrc file #6354.
- Throw a meaningful error when applying a patch to a dependency fails.
-
pnpm update --global --latest should work #3779.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
-
When dedupe-peer-dependents is enabled, use the path (not id) to determine compatibility.
When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication.
Resolves: #6605
-
Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Minor Changes
-
Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.
A new field will now be present in the lockfile: settings. It will store the values of two settings: autoInstallPeers and excludeLinksFromLockfile. If someone tries to perform a frozen-lockfile installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.
The lockfile format version is bumped from v6.0 to v6.1.
Related PR: #6557
Related issue: #6312
Patch Changes
- When updating dependencies, preserve the range prefix in aliased dependencies. So
npm:[email protected] becomes npm:[email protected].
- Print a meaningful error when a project referenced by the
workspace: protocol is not found in the workspace #4477.
- Should respect ignore patterns in
updateConfig.ignoreDependencies #6548
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
-
pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #6553.
- Expanded missing command error, including 'did you mean' #6492.
- Normalize current working directory on Windows #6524.
- Build projects in a workspace in correct order #6568.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
-
pnpm link -g <pkg-name> should not modify the package.json file #4341.
- Node.js range specified through the
engines field should match prerelease versions #6509.
-
pnpm publish --otp should work #6514.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
- Link the bin files of local workspace dependencies, when
node-linker is set to hoisted 6486.
- Show cyclic workspace dependency details #5059.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
- Patch node-fetch to fix an error that happens on Node.js 20 #6424.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
- Warn user when
publishConfig.directory of an injected workspace dependency does not exist #6396.
- Use hard links to link the node executable on Windows machines #4315.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Minor Changes
- Allow env variables to be specified with default values in
.npmrc. This is a convention used by Yarn too.
Using ${NAME-fallback} will return fallback if NAME isn't set. ${NAME:-fallback} will return fallback if NAME isn't set, or is an empty string #6018.
Patch Changes
-
pnpm config get <key> returns empty when the value is a boolean
- Don't print an info message about linked dependencies if they are real linked dependencies specified via the
link: protocol in package.json.
- Add -g to mismatch registries error info when original command has -g option #6224.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Minor Changes
- Add
ignore-workspace-cycles to silence workspace cycle warning #6308.
Patch Changes
- Registries are now passed to the preResolution hook.
- Repeat installation should work on a project that has a dependency with () chars in the scope name #6348.
- Should report error summary as expected.
- Update
@yarnpkg/shell to fix issues in the shell emulator #6320.
- Installation should not fail when there is a local dependency that starts in a directory that starts with the
@ char #6332.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Patch Changes
-
pnpm audit should work even if there are no package.json file, just a pnpm-lock.yaml file.
- Dedupe direct dependencies after hoisting.
- Don't remove automatically installed peer dependencies from the root workspace project, when
dedupe-peer-dependents is true #6154.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Compare Source
Patch Changes
- Should use most specific override rule when multiple rules match the same target #6210.
- Fix regression introduced in v7.30.1 #6271.
Our Gold Sponsors
Our Silver Sponsors
Compare Source
Compare Source
Patch Changes
- Don't write the
pnpm-lock.yaml file if it has no changes and pnpm install --frozen-lockfile was executed #6158.
- Fix git-hosted dependencies referenced via
git+ssh that use semver selectors #6239.
- When publish some package throws an error, the exit code should be non-zero #5528.
- Only three paths are displayed in
pnpm audit output #6203
- Aliased packages should be used to resolve peer dependencies too #4301.
Our Gold Sponsors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "before 4am on Monday" (UTC).
🚦 Automerge: Enabled.
♻ 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.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name |
Status |
Preview |
Updated |
| typed-vuex |
❌ Failed (Inspect) |
|
Nov 20, 2022 at 4:34PM (UTC) |
⚠ Artifact update problem
Renovate 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:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: pnpm-lock.yaml
real 0m4.113s
user 0m3.497s
sys 0m0.463s
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:
Coverage data is based on head (5c5560d) compared to base (a16c245).
Patch has no changes to coverable lines.
Additional details and impacted files
@@ Coverage Diff @@
## main #309 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 10 10
Lines 117 117
Branches 28 28
=========================================
Hits 117 117
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
typed-vuex copied to clipboard
danielroe
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
![codecov[bot] avatar](https://avatars.githubusercontent.com/in/254?v=4 "Published by a pub.dev verified publisher"){kind=small}