MetaMask deprecation console warning

[BytePhoenixCoding]

MetaMask: 'ethereum.send(...)' is deprecated and may be removed in the future. Please use 'ethereum.sendAsync(...)' or 'ethereum.request(...)' instead.
For more information, see: https://eips.ethereum.org/EIPS/eip-1193
send @ inpage.js:1

inpage.js:1 MetaMask: The event 'close' is deprecated and may be removed in the future. Please use 'disconnect' instead.
For more information, see: https://eips.ethereum.org/EIPS/eip-1193#disconnect
_warnOfDeprecation @ inpage.js:1

inpage.js:1 MetaMask: The event 'networkChanged' is deprecated and may be removed in the future. Use 'chainChanged' instead.
For more information, see: https://eips.ethereum.org/EIPS/eip-1193#chainchanged

Getting these warnings in the console. May be worth checking sometime if we should change the function names to avoid deprecation warnings incase MM decides to fuck everyone over with an update one day hahah.

[TG-Brad]

Looking into this, it seems to be a dependency issue, so can't be easily fixed unless the resulting package (assumingly @binance-chain/bsc-connector) fixes it. Most the events it looks for both though, so it should be fine.

[BytePhoenixCoding]

Should be able to edit it in build version maybe, like the hooks error.