-
Notifications
You must be signed in to change notification settings - Fork 753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Equalizing dependency versions #782
Conversation
Codecov Report
@@ Coverage Diff @@
## master #782 +/- ##
==========================================
- Coverage 90.47% 84.50% -5.97%
==========================================
Files 49 16 -33
Lines 3170 1265 -1905
Branches 485 249 -236
==========================================
- Hits 2868 1069 -1799
+ Misses 204 126 -78
+ Partials 98 70 -28
Continue to review full report at Codecov.
|
33ac401
to
28d4512
Compare
28d4512
to
5e3605b
Compare
LGTM. Did you use any automated software to equalize these dependencies? Is it an idea to centralize (i.e. in the root) the packages which multiple packages in the monorepo use? EDIT: Hmm. Looks like the checks are not succesful. |
@jochem-brouwer thanks for the review. Although moving dependencies to the root package.json would work in our machines and CI, that would not work whenever people installed individual libraries. Patricio raised a PR (#770) with a script that helps detecting sub-packages with different versions, so it will help us detecting these early and often.
I normalized those manually, doing some regular expressions and find/replaces. And I didn't want to update them all to latest major, because that requires more time investment, and my goal for now is just to simplify the dependency tree. Regarding failing checks: linting problems 😣 |
5e3605b
to
cf67e2a
Compare
Right, this is now ready for review again. I was using the same lint from another PR 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, nice work!
"@ethereumjs/config-prettier": "^1.1.0", | ||
"@ethereumjs/config-tsc": "^1.1.0", | ||
"@ethereumjs/config-tslint": "^1.1.0", | ||
"@ethereumjs/config-nyc": "^1.1.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my understanding: this is just a cosmetic change, right? Or does this make a difference on CI caching or something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@holgerd77 Even though the version ranges result in the same version being used, it is a requirement for lerna bootsrap --hoist
to work properly. See big chunk of warnings described in #730.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or more explicitly: the repo must use the same exact versions so they get properly hoisted.
* Normalizing dependency versions * lint: Side-effects of package updates * Updates merkle-patricia-tree dep * test: side-effect of updating nyc * Updates @types/tape dep * refactor: using tape whithout paths * Updates -tx and ethereumjs-util
This PR equalizes package versions.
Remaining work that is being done (or will be done) in other PRs:
async
dependency Remove async dependency #779Related: #730, #770.