Gathering detailed insights and metrics for @zwik/yarn-upgrade-all
Gathering detailed insights and metrics for @zwik/yarn-upgrade-all
Gathering detailed insights and metrics for @zwik/yarn-upgrade-all
Gathering detailed insights and metrics for @zwik/yarn-upgrade-all
npm install @zwik/yarn-upgrade-all
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
76 Commits
2 Watchers
1 Branches
1 Contributors
Updated on Nov 19, 2024
Latest Version
0.0.12
Package Id
@zwik/yarn-upgrade-all@0.0.12
Unpacked Size
5.81 kB
Size
2.40 kB
File Count
5
NPM Version
6.9.0
Node Version
10.16.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
4
Based on yarn-upgrade-all which is very slow and was missing some functionality, such as exact/tilde/caret versioning, I've decided to rework it a bit resulting in this packages.
This is a command line utility program to upgrade all the packages in your package.json
to the latest version
(potentially upgrading packages across major versions).
yarn add --dev @zwik/yarn-upgrade-all
yarn global add @zwik/yarn-upgrade-all
npm install -g @zwik/yarn-upgrade-all
:exclamation: Don't use yarn
to install it on Windows because there is a bug: yarnpkg/yarn#2224.
npx @zwik/yarn-upgrade-all
Will update packages with caret ^
versioning.
npx @zwik/yarn-upgrade-all -E
Will update packages with exact versioning.
npx @zwik/yarn-upgrade-all -T
Will update packages with tilde versioning.
For every package in package.json
, it runs yarn add [--dev|--peer] <package-name>
.
yarn upgrade --latest
?Most of the time yarn upgrade --latest
works. But I did meet some cases when it didn't work. I am not sure of the reason, maybe it's yarn's bug.
This library is very robust because it goes the hard way.
In that case, that package will be skipped and an error message will be printed.
You need to read the error message and manually install that package.
It is the recommended flow. Because if a package failed to install, most of the time, you need to manually troubleshoot the issue and fix the issue.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
Found 0/2 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
21 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More