Replace ethjs packages with @metamask/ethjs forks

[legobeat]

Explanation

Use MetaMask forks of ethjs packages. This is the first step of a gradual update which will result in removing dependency on babel-runtime@6.x, amongst other improvements.

References

Related

• deps: ethjs@^0.4.0 -> @metamask/ethjs@^0.5.0 eth-method-registry#50
  • Use ganache for tests instead of Infura HTTP API  eth-method-registry#51

Changelog

@metamask/controller-utils

• CHANGED: Update from ethjs-unit to @metamask/ethjs-unit

@metamask/gas-fee-controller

• CHANGED: Update from ethjs-unit to @metamask/ethjs-unit

@metamask/assets-controllers

• CHANGED: Update from ethjs-provider-http to @metamask/ethjs-provider-http

@metamask/transactions-controller

• CHANGED: Update from ethjs-provider-http to @metamask/ethjs-provider-http

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/ethjs-provider-http	0.2.0	environment	+3	465 kB	lgbot
@metamask/ethjs-unit	0.2.1	None	+0	457 kB

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: @metamask/ethjs-unit@0.2.1

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

[legobeat]

@SocketSecurity ignore @metamask/ethjs-unit@0.2.1

[mcmire]

Most of the places we are using these packages are in tests, so there is an opportunity to remove usage entirely, but we can leave that for another PR. Looks good.

[legobeat]

Most of the places we are using these packages are in tests, so there is an opportunity to remove usage entirely, but we can leave that for another PR. Looks good.

Isn't the point of using it in tests to preserve compatibility with existing downstream use, ie extension and mobile? That is, they should be removed there before being removed as tests here.

[mcmire]

Sure, we can definitely wait until we remove them from the clients before removing them here.