Update eth-json-rpc-filters

[rekmarks]

This fixes an eth-json-rpc-filters-related memory leak. Specifically, the subscription manager middleware would not be torn down when a connection was closed, and some listeners would never be removed. That middleware now exposes a destroy function, which will be called by the extension on connection teardown, here:

metamask-extension/app/scripts/metamask-controller.js

Lines 1422 to 1436 in 8dfb0e8

	pump(
	outStream,
	providerStream,
	outStream,
	(err) => {
	// cleanup filter polyfill middleware
	engine._middleware.forEach((mid) => {
	if (mid.destroy && typeof mid.destroy === 'function') {
	mid.destroy()
	}
	})
	if (err) log.error(err)
	}
	)
	}

Changes

• add eth-json-rpc-filters@4.1.1
  • Add destruction function to sub manager middleware eth-json-rpc-filters#10
• add gaba@1.7.4 (depends on eth-json-rpc-filters)
  • Update web3-provider-engine core#166
    • Update eth-json-rpc-filters web3-provider-engine#321
      • Add destruction function to sub manager middleware eth-json-rpc-filters#10

Result

yarn why eth-json-rpc-filters
=> Found "eth-json-rpc-filters@4.1.1"
info Has been hoisted to "eth-json-rpc-filters"
info Reasons this module exists
   - Specified in "dependencies"
   - Hoisted from "gaba#web3-provider-engine#eth-json-rpc-filters"

[Gudahtt]

Looks good!