@metamask/inpage-provider
Advanced tools
Changelog
[8.1.0] - 2021-05-05
BaseProvider
, implementing EIP-1193 without any legacy features (#144)createExternalExtensionProvider
, from the extension-provider package (#152)Changelog
[8.0.0] - 2020-12-07
logger
parameter to initializeProvider
(#116)window.web3
shim, shimWeb3
export (#113, #115)
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
.initProvider
export to initializeProvider
(#114)ethereum.publicConfigStore
with new set of JSON-RPC notifications (#109)_metamask.isEnabled
and _metamask.isApproved
(#112)chainIdChanged
event (#111)ethereum.publicConfigStore
(#109)web3.js
-related functionality (#106)
web3.js
instance at window.web3
, and kept web3.eth.defaultAccount
in sync with ethereum.selectedAddress
.connect
and disconnect
events (#120)
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 connection1011
indicates that a page reload is requiredMetaMaskInpageProvider
logger
to instance variable (#118)
accountsChanged
, chainChanged
, and networkChanged
.Changelog
[7.0.0] - 2020-09-08
Metamask
in all exports to MetaMask
Changelog
[6.3.0] - 2020-09-04
ethereum.networkVersion
and .chainId
now default to null
instead of undefined
Changelog
[6.2.0] - 2020-08-04
logger
object to the provider constructor, to override the default logger
console
globaldebug
, error
, info
, log
, trace