9.1.0

Added

• Add deprecation warning for encryption methods (#218)

9.0.0

Changed

• BREAKING: Move stream functionality from BaseProvider to new StreamProvider (#209)
  • BaseProvider is now a transport-agnostic abstract class. StreamProvider accepts a stream and relies on MetaMask's internal JSON-RPC API for its behavior. See the StreamProvider class for more details.
  • MetaMaskInpageProvider should be completely unaffected except that its prototype chain now includes a class named AbstractStreamProvider.

Version 8.1.1

8.1.1 RC (#172)

* 8.1.1
* Update CHANGELOG.md for lint:fix

Co-authored-by: github-actions <[email protected]>
Co-authored-by: shanejonas <[email protected]>
Co-authored-by: Erik Marks <[email protected]>

Version 8.1.0

8.1.0 RC (#165)

* 8.1.0

* add changelog update for v8.1.0

* Update CHANGELOG.md

* lint fix + better changelog formatting + PR links

* Update CHANGELOG.md

Co-authored-by: github-actions <[email protected]>
Co-authored-by: shanejonas <[email protected]>
Co-authored-by: Erik Marks <[email protected]>

8.0.4

Fixed

• Fix warning on second currentProvider access (#138)

8.0.3

Fixed

• Restore 'data' provider event (#135)

8.0.2

Changed

• Reduce window.web3 shim console noise (#133)

8.0.1

Fixed

• Fix 8.0.0 types (#127)

8.0.0

Added

• Add logger parameter to initializeProvider (#116)
• Add window.web3 shim, shimWeb3 export (#113, #115)
  • This is to maintain window.web3.currentProvider once MetaMask stops injecting window.web3 (very soon), and to log attempts to access any properties on the shim other than currentProvider.
  • initializeWeb3 now has a shouldShimWeb3 argument, which causes the shim to be set as window.web3 if true.

Changed

• (BREAKING) Rename initProvider export to initializeProvider (#114)
• (BREAKING) Replace ethereum.publicConfigStore with new set of JSON-RPC notifications (#109)

Fixed

• Correctly implement connect and disconnect events (#120)
  • See EIP-1193 for the specification of these events.
  • disconnect emits with an RPC error. Like all such errors emitted by this module, they have a code property with a number value. There are currently two codes:
    • 1013 indicates that MetaMask is attempting to reestablish the connection
    • 1011 indicates that a page reload is required
• Send page metadata even if page is already loaded (#119)
• Convert MetaMaskInpageProvider logger to instance variable (#118)
  • Previously, it was erroneously a singleton across all class instances.
• Stop emitting state change events on initialization (#117)
  • Includes accountsChanged, chainChanged, and networkChanged.
  • This prevents sites that handle any of these events by reloading the page from entering into a reload loop.

Removed

• (BREAKING) Remove _metamask.isEnabled and _metamask.isApproved (#112)
• (BREAKING) Remove the chainIdChanged event (#111)
• (BREAKING) Remove ethereum.publicConfigStore (#109)
• (BREAKING) Remove web3.js-related functionality (#106)
  • This functionality caused the page to reload if there was a web3.js instance at window.web3, and kept web3.eth.defaultAccount in sync with ethereum.selectedAddress.
  • This functionality is replicated in @metamask/legacy-web3.

7.0.0

• (BREAKING) Changed casing of Metamask in all exports to MetaMask
  • A brand is a brand ¯\(ツ)/¯