-
Notifications
You must be signed in to change notification settings - Fork 38
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
[Easy] npm audit fix #136
[Easy] npm audit fix #136
Conversation
What happened, why did you close the issue? |
I want to make sure it is working first. Also I thought it was the cause of the 🐛 I reported (but no longer believe this to be true). |
This build is failing because of
which appears to be related to this issue. Will look into bignumber and see what the deal is. |
# Conflicts: # package-lock.json # package.json
You could create a PR in the But you are right that the error doesn't make sense. https:/github.com/debris/bignumber.js.git#94d7146671b9719e00a09c29b01a691bc85048c2 does include a |
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.
I cannot assess this one.
Out of curiosity is Denis Granha (the maintainer of abi-decoder) still at Gnosis? There are PRs open in that repo to upgrade the web3 version which could resolve this problem at it's source. I'd rather not find another decoding solution - it's a really nice package. Also, web3 1.0-beta.37 has recently been selected as the official 'stable' version of web3 1.0 and a PR for that release is in progress. This might be an opportune time to revisit abi-decoder maintenance. |
Thanks for the suggestions @cgewecke, I'll get in touch with @denisgranha about this one! |
So finally, the web3 dependency in abi-decoder was updated and this fix no longer depends on using yarn. I am unsure what is the deal with displaying solidity-bytes utils update. This has clearly already been changes in master so should not appear as different here. |
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.
Would love to see the unrelated travis changes be in a separate PR but otherwise this seems good to go.
⬆️
Repairing all vulnerabilities that can be fixed by package upgrade.