@metamask/providers - npm Package Versions

[20.0.0]

Changed

• BREAKING: An isConnected boolean property is now expected in the result of metamask_getProviderState and metamask_chainChanged events (#404)
• BREAKING: A networkVersion value of loading received by the chainChanged event handler is now interpreted to be null. In this case, the networkChanged event emits a null value as well. (#404)
• BREAKING: The disconnect event is now tied to the new isConnected property instead of the networkVersion property. (#404)
• A change in the isUnlocked boolean property of the metamask_getProviderState and metamask_accountsChanged events (from what is in state) no longer causes the accountsChanged event to be emitted (#405)
• MetaMaskInpageProvider.isUnlocked() will always return true until the inpage to contentscript stream ends and the provider enters a permanently disconnected state (#405)

[19.0.0]

Changed

• BREAKING: StreamProvider no longer accepts a jsonRpcStreamName parameter (#400)
  • Previously, this parameter was used internally to create an ObjectMultiplex stream and substream for JSON-RPC communication
  • Now, the consumer is responsible for creating and managing the stream multiplexing if needed
  • The provider will use the provided stream connection directly without any multiplexing
• BREAKING: MetaMaskInpageProvider no longer accepts a jsonRpcStreamName parameter (#400)
  • This change is inherited from StreamProvider, as MetaMaskInpageProvider extends StreamProvider
  • Stream multiplexing should be handled before provider instantiation
• initializeInpageProvider now handles stream multiplexing internally (#400)
  • Creates an ObjectMultiplex instance and substream using the provided jsonRpcStreamName
  • This maintains backwards compatibility for consumers using initializeInpageProvider
• createExternalExtensionProvider now handles stream multiplexing internally (#400)
  • Creates an ObjectMultiplex instance and substream for JSON-RPC communication
  • This maintains backwards compatibility for consumers using createExternalExtensionProvider

[18.3.1]

Changed

• Bump @metamask/json-rpc-engine from ^10.0.1 to ^10.0.2 (#397)
• Bump @metamask/json-rpc-middleware-stream from ^8.0.5 to ^8.0.6 (#397)
• Bump @metamask/rpc-errors from ^7.0.1 to ^7.0.2 (#397)
• Bump @metamask/utils from ^10.0.0 to ^11.0.1 (#397)

[18.3.0]

Added

• Implement Wallet Discovery via CAIP-294 for Wallet Multichain API (#395)

[18.2.0]

Added

• Add new export for initializeInpageProvider with legacy build system support (#391)
  • Previously this module could be imported from /dist/initializeInpageProvider, but this only worked with build systems that support the exports field (e.g. browserify).
  • This new initializeInpageProvider export has a JavaScript redirect for older build systems, so it should work correctly in all cases.

[18.1.2]

Fixed

• Allow optional jsonRpcStreamName for initializeInpageProvider (#390)
  • This parameter was accidentally made required in v18.1.0

[18.1.1]

Changed

• Bump MetaMask dependencies (#385, #384, #383)

[18.1.0]

Added

• Add intializeInpageProvider as package export (#380)

Fixed

• Remove spurious typescript reference (#381)

[18.0.0]

Changed

• BREAKING: Bump @metamask/json-rpc-engine from ^9.0.1 to ^10.0.0 (#378)
• BREAKING: Bump @metamask/rpc-errors from ^6.4.0 to ^7.0.0 (#373)
• Bump @metamask/object-multiplex from ^2.0.0 to ^2.1.0 (#375)
• Bump @metamask/utils from ^9.2.1 to ^9.3.0 (#370)

[17.2.1]

Fixed

• Add support for edge-chromium to createExternalExtensionProvider (#318, #368)
• Fix ESM-related build issues (#362, #363)