-
Notifications
You must be signed in to change notification settings - Fork 56
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
Update node #878
Update node #878
Conversation
49eda8c
to
12f3997
Compare
92a4edf
to
12f3997
Compare
Having problems with swarm-js dependency in web3. Already known in web3 project and reported web3/web3.js#5315 but web3 still using this library with vulnerability in last version 1.7.5. So I will leave this PR until we have a solution and will open a spike for figuring out the impact of moving web3 to ethers in these projects (#888) in the case web3 is not solving this vulnerability in new versions. |
We are still having issues regarding dependency vulnerabilities because a transient dependency |
Looks like we have two very similar PRs. |
Oh blast, I forgot I opened this before I went on leave. I'll close it as #908 is more current and has @pawelgrzybek 's suggestions incorporated. |
fixes #876
Updates node to v16.16 (latest lts) and npm to 8.17.
Use of node 8 enables vulnerable dependencies to be overridden with the
overrides
keyword inpackage.json
. This is required to address a vulnerability ingot
;web3js
depends on a vulnerable version.