@metamask/inpage-provider - npm Package Versions

[6.1.0] - 2020-07-21

Changed

• Only emit data event for notifications present in ^4.0.0 (#73)
  • Some consumers make assumptions about the shape of the object emitted with the event that do not hold for all notifications in ^6.0.0.
• Select icon using rel~="icon" when retrieving site metadata (#76)
  • This is instead of defaulting to rel="shortcut icon".

Fixed

• Emit accountsChanged event after all related state has been updated (#72)
  • For example, ethereum.selectedAddress will now have been updated by the time the event is emitted.
• Enable retrieval of site icons not hosted on the same origin (#78)
  • For example, icons hosted on assets.foo.com that are used on foo.com will now be retrieved successfully.

[6.0.1] - 2020-07-15

Fixed

• Warning message for the data event
  • This deprecated event was added back in 6.0.0, but the warning message was not defined.
• Restore publicConfigStore property as alias for _publicConfigStore
  • The _publicConfigStore was named publicConfigStore before 4.0.0. The original property turned out to be used by consumers. The store is scheduled to be removed completely, and accessing publicConfigStore emits a warning.

[6.0.0] - 2020-07-04

Added

• The data event
  • This event was removed in 4.0.0, as it was thought to only be used internally. This assumption was incorrect, and the event is now restored.

Changed

• BREAKING: Restore the notification event value to its pre-4.0.0 state
  • Prior to 4.0.0 this event was emitted by code in the MetaMask extension. Its value was inadvertently changed when it was moved to this package.

[5.2.1] - 2020-06-29

Changed

• Un-deprecate isConnected method.

[5.2.0] - 2020-06-24

Changed

• Remove property protections
  • Unless we lock down the entire provide object, which we can't do, a determined consumer can break our provider. Thus, protected properties are pointless.
• Fix requests params type checks
• Update deprecation warning messages per most recent deprecation plans

[5.0.2] - 2020-05-22

Changed

• Fix ethereum.send return value for certain argument combination
  • Reverted to pre-4.0.0 state
• Stop protecting overwrites of the following properties, that existed prior to 4.0.0:
  • ethereum.isMetaMask
  • ethereum._metamask
• Protect the following new, private properties required for ethereum.request to work:
  • ethereum._rpcRequest
  • ethereum._rpcEngine

[5.0.1] - 2020-05-11

Changed

• Rename package to @metamask/inpage-provider
• Prevent overwrite of certain properties on the Provider
  • ethereum.request
  • ethereum.isMetaMask
  • ethereum._metamask

[5.0.0] - 2020-04-22

Added

• The most recent EIP 1193 API (#30)
  • The method request
  • The events disconnect and message
• A global initialization event, ethereum#initialized, for asynchronous injection (#31)
• Helper methods for initializing the provider (#31)

Changed

• BREAKING: Use named instead of default exports (#31)
• BREAKING: MetaMaskInpage constructor now takes a connectionStream and an options object (#31)
• BREAKING: _metamask.sendBatch -> _metamask.requestBatch (#30)
• BREAKING: Revert send to match provider in v7.7.8 of metamask-extension (#29)
• The connect event now emits with a ProviderConnectInfo object per EIP 1193 (#30)
• Deprecated the send method (#30)
• Deprecated the events close, networkChanged, and notification, and added deprecation warnings for them (#30)
• Un-deprecated sendAsync (#29)