Releases: MetaMask/eth-json-rpc-middleware
Releases · MetaMask/eth-json-rpc-middleware
10.0.0
Changed
- BREAKING: Rename the package from
eth-json-rpc-middleware
to@metamask/eth-json-rpc-middleware
(#180) - Change all middleware request and response types to
unknown
(#183)- This more accurately reflects the expectations of the middleware, and the way they had been used. This was required to more easily compose this middleware with others that had non-matching types.
- The block cache and the inflight cache middleware types have been updated to include the
skipCache
request property (#178)- This property was always supported, but it was missing from the type.
9.0.1
9.0.0
8.1.0
8.0.2
8.0.1
8.0.0
Added
- BREAKING: Add
eth_signTransaction
support (#96)- We consider this breaking because a wallet application may not support this method, and would have to explicitly block it until its implications can be adequately represented to the user.
- Add
send
method to provider andethersProviderAsMiddleware
(#97)
7.0.1
7.0.0
Added
- TypeScript types (#68)
Changed
- (BREAKING) Move middleware files to
/src
folder (#60) - (BREAKING) Convert all exports to named (#81)
- Migrate to TypeScript (#68)
- Replace
url
dependency with native URL global (#67) - Ask bundlers to ignore Node-specific depedencies in browser environments (#78, #84)
- Removed various unused production dependencies (#10, #80)
Fixed
retryOnEmpty
middleware error messages (#58)- They were referencing a different middleware.
- Default unrecognized methods to never be cached (#66)
- Only publish necessary files (#70)
- Robustify
providerFromEngine
callback parameter validation (#76)- Previously, it only errored if the parameter was falsy. Now, it will error if it is not a function.
- Passing the previous implementation a truthy, non-function value would cause fatal downstream errors.
- Prevent caching unrecognized requests (#75)
- Previously, nonsense values were sometimes cached, resulting in an ugly state and possibly a minor performance penalty.