Bump @metamask/providers from 16.0.0 to 22.1.1

[dependabot]

Bumps @metamask/providers from 16.0.0 to 22.1.1.

Release notes

Sourced from @​metamask/providers's releases.

22.1.1

Changed

• Update StreamProvider.initialize to call metamask_getProviderState with isInitializingStreamProvider: true (#422)
  • In implementing metamask_getProviderState, the extension makes a request for the network version; this parameter allows us to opt-out of that extra request on UI initialization.

22.1.0

Changed

• Adds a new shouldAnnounceCaip294 flag to initializeProvider options (defaulted to true), so instead of the providerInfo.rdns value determining whether or not to announce the caip-294 target, the caller of initializeProvider can directly control this (#419)

22.0.1

Fixed

• Catch error when ethereum provider is set before we attempt to set it (#416)

22.0.0

Changed

• BREAKING: initializeProvider announces the extensionId, when available, via a caip-348 target on in the new targets property of the CAIP-294 wallet announcement event instead of the previous extensionId property (#413)

21.0.0

Changed

• BREAKING: initializeProvider() no longer accepts the jsonRpcStreamName option param. (#410)
  • This helper no longers instantiates a jsonRpcStreamName named substream from the connectionStream Duplex stream option param.
  • Callers of initializeProvider() should now instantiate their own metamask-provider named substream and pass it in as the value for connectionStream.

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)

... (truncated)

Changelog

Sourced from @​metamask/providers's changelog.

[22.1.1]

Changed

• Update StreamProvider.initialize to call metamask_getProviderState with isInitializingStreamProvider: true (#422)
  • In implementing metamask_getProviderState, the extension makes a request for the network version; this parameter allows us to opt-out of that extra request on UI initialization.

[22.1.0]

Changed

• Adds a new shouldAnnounceCaip294 flag to initializeProvider options (defaulted to true), so instead of the providerInfo.rdns value determining whether or not to announce the caip-294 target, the caller of initializeProvider can directly control this (#419)

[22.0.1]

Fixed

• Catch error when ethereum provider is set before we attempt to set it (#416)

[22.0.0]

Changed

• BREAKING: initializeProvider announces the extensionId, when available, via a caip-348 target on in the new targets property of the CAIP-294 wallet announcement event instead of the previous extensionId property (#413)

[21.0.0]

Changed

• BREAKING: initializeProvider() no longer accepts the jsonRpcStreamName option param. (#410)
  • This helper no longers instantiates a jsonRpcStreamName named substream from the connectionStream Duplex stream option param.
  • Callers of initializeProvider() should now instantiate their own metamask-provider named substream and pass it in as the value for connectionStream.

[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

... (truncated)

Commits

• 4ac0b3e 22.1.1 (#423)
• 21a584b Pass isInitializingStreamProvider to metamask_getProviderState (#422)
• 5b3055f 22.1.0 (#420)
• 93f9493 Refactor caip-294 announcement logic (#419)
• 981fa83 22.0.1 (#417)
• 098e396 fix: catch error when ethereum provider is set before our attempt to set (#416)
• f0ca94b 22.0.0 (#415)
• c237ed7 feat: Add CAIP-294 targets to wallet_announce event data. Announce CAIP-3...
• fe58406 ci: use MetaMask/action-checkout-and-setup@v1 (#414)
• d154423 chore: update security-code-scanner@main to action-security-code-scanner@v1 (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)