@metamask/providers - npm Package Versions

[13.0.0]

Changed

• BREAKING: Update chainId, networkVersion, and selectedAddress to be read-only (#280)
• Log deprecation warning when accessing chainId, networkVersion, and selectedAddress (#280)
• Remove pump (#281)

[12.0.0]

Changed

• BREAKING: Replace eth-rpc-errors@^4.0.2 with @metamask/rpc-errors@6.0.0 (#277)
• BREAKING: Replace json-rpc-engine@^6.1.0 with @metamask/json-rpc-engine@7.1.1 (#277)
• Upgrade @metamask/utils from ^6.2.0 to ^8.1.0 (#277)

[11.1.2]

Changed

• Update extension-port-stream to ^2.1.1 (#273)

[11.1.1]

Changed

• Update fast-deep-equal (#258)

[11.1.0]

Added

• Add warning for callers of wallet_watchAsset with ERC721 and ERC1155 token types, that support is currently considered experimental (#264)

[11.0.0]

Changed

• BREAKING: Minimum Node.js version 16 (#254)
• Support Flask and Beta in the external extension provider (#252)
• Bump @metamask/safe-event-emitter from 2.0.0 to 3.0.0 (#255)

Fixed

• Fix console warning about deprecated webextension-polyfill-ts (#249)
• Prevent accountsChanged + eth_accounts callback loop (#248)
  • If you listen to the provider accountsChanged event, modify the returned accounts, then call eth_accounts, it was possible to enter an infinite loop. This was caused by the provider mistakenly thinking the accounts had changed because of the mutation performed in the event listener, triggering redundant accountsChanged events. This was fixed; there should be no more redundant accountsChanged events and no infinite loop.

[10.2.1]

Changed

• Update json-rpc-middleware-stream (#234)

[10.2.0]

Changed

• Update json-rpc-middleware-stream (#230)

[10.1.0]

Changed

• Update json-rpc-middleware-stream (#228)

[10.0.0]

Changed

• Retry sending messages to extension when METAMASK_EXTENSION_STREAM_CONNECT is received (#223)
• BREAKING: Update minimum Node.js version to v14 (#225)