state is not defined ReferenceError: state is not defined

[gpehartz]

Current Behavior

I'm using web3 onboard react in my app. If you configure a chain in web3onboard init and that chain is not in your wallet and you call web3OnBoard.setChain method then web3onboard crashes with the following error message:
state is not defined
ReferenceError: state is not defined

Expected Behavior

Two options:

1. (Preferred) Add the missing chain in the wallet automatically
2. Return a specific response from setChain to indicate that the target chain is not in the wallet

Steps To Reproduce

1. Init web3onboard with two chains

• {
  "id": "0x61",
  "token": "Binance Chain Native Token",
  "label": "Binance Smart Chain Testnet",
  "rpcUrl": "https://data-seed-prebsc-1-s1.binance.org:8545",
  "icon": "/img/cryptologo/binance.svg",
  "color": "#FFFFFF"
  }

• {
  "id": "0x13881",
  "token": "MATIC",
  "label": "Mumbai (Matic Testnet)",
  "rpcUrl": "https://rpc-mumbai.maticvigil.com",
  "icon": "/img/cryptologo/polygon.svg",
  "color": "#FFFFFF"
  }

2. Add these chains to your metamask wallet
3. Use injectedModule()
4. Connect to Metamask with web3onboard modal
5. Try changing chains from web3onboard -> everything is working fine, metamask pops up the confirmation for chain change
6. Remove Binance testnet chain from metamask
7. Try changing chains from web3onboard again -> state is not defined error message

What package is effected by this issue?

@web3-onboard/react

Is this a build or a runtime issue?

Runtime

Package Version

2.8.13

Node Version

No response

What browsers are you seeing the problem on?

Chrome

Relevant log output

Uncaught (in promise) ReferenceError: state is not defined
    at instance$3 (index-4c4d8815.js:8546:1)
    at init$1 (index-4c4d8815.js:1843:1)
    at new SwitchChain (index-4c4d8815.js:8554:1)
    at create_if_block_18 (index-4c4d8815.js:8903:1)
    at Object.p (index-4c4d8815.js:10414:1)
    at update (index-4c4d8815.js:1293:1)
    at flush (index-4c4d8815.js:1253:1)

Anything else?

No response

Sanity Check

• If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.