deps: replace eth-json-rpc-middleware with @metamask/eth-json-rpc-provider

[legobeat]

eth-json-rpc-middleware has been split into @metamask/eth-json-rpc-middleware and @metamask/eth-json-rpc-provider. Only the parts from the latter is used here.

Also drop @types/node to highest version of lowest currently supported node major 14.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/eth-json-rpc-provider	1.0.0	None	+0	20.5 kB	gudahtt
@types/node	17.0.23...14.18.53	None	+0/-0	1.58 MB	types
@metamask/utils	3.0.1...3.6.0	None	+1/-1	425 kB	metamaskbot

🚮 Removed packages: [email protected]

[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/[email protected]

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 [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

[legobeat]

@SocketSecurity ignore @metamask/[email protected]

no author data OK

[mikesposito]

Maybe we can take the chance to update @metamask/utils to ^6.2.0 as we just use createProjectLogger, createModuleLogger?

[legobeat]

I agree the change is coming up, but let's do that separately.

BTW we could do ^5.0.2 at best without making that bump a breaking change, due to engines.node being >=16.0.0 since 6.0.0.

[legobeat]

#83

[Gudahtt]

LGTM!