We should bump @metamask/eth-json-rpc-provider to rely on the new changes.
At that point, calling sendAsync will be deprecated; we should use request instead.
There are two middleware which use sendAsync: retryOnEmpty and block-ref.
We also use sendAsync in providerAsMiddleware.
Finally, there are a lot of tests that mock sendAsync on the provider. The tests use a helper, stubProviderRequests which does this in particular. These references need to be changed.
After
SafeEventEmitterProvideris updated to support EIP-1193 and a new version of@metamask/eth-json-rpc-provideris released, we should adapt to the changes:@metamask/eth-json-rpc-providerto rely on the new changes.sendAsyncwill be deprecated; we should userequestinstead.sendAsync:retryOnEmptyandblock-ref.sendAsyncinproviderAsMiddleware.sendAsyncon the provider. The tests use a helper,stubProviderRequestswhich does this in particular. These references need to be changed.