Skip to content

Releases: rainbow-me/rainbowkit

@rainbow-me/[email protected]

29 Jun 00:47
6824e25
Compare
Choose a tag to compare

Patch Changes

  • b2b46ef: Fix WalletConnect deep linking for wallets with custom URL schemes

@rainbow-me/[email protected]

29 Jun 02:16
516f06d
Compare
Choose a tag to compare

Minor Changes

  • 6e25576: Update wagmi dependency to ^0.5.3

@rainbow-me/[email protected]

27 Jun 22:10
47f6a88
Compare
Choose a tag to compare

Patch Changes

  • d905271: Fix issue on iOS in non-Safari browsers and WebViews where a blank tab is left behind after connecting via WalletConnect

@rainbow-me/[email protected]

26 Jun 22:44
b495187
Compare
Choose a tag to compare

Patch Changes

  • 40d838e: Pinned the wagmi peer dependency to 0.4.x
  • 1ab9c07: Fix bug where "onConnecting" callbacks were fired multiple times when toggling between WalletConnect-based wallets
  • 1a7d50c: Update connect button height to be consistent between states.

@rainbow-me/[email protected]

22 Jun 00:30
e9aa8f6
Compare
Choose a tag to compare

Patch Changes

  • ac63f9a: Detect Trust Wallet in-app browser

@rainbow-me/[email protected]

21 Jun 00:14
e10b75e
Compare
Choose a tag to compare

Patch Changes

  • ee81177: Support deep linking of wallet interactions for WalletConnect on Android

@rainbow-me/[email protected]

20 Jun 00:50
80ed738
Compare
Choose a tag to compare

Patch Changes

  • 33a2dd7: Automatically connect to the first chain in the chains array to avoid presenting the "Wrong network" state immediately after connecting

@rainbow-me/[email protected]

16 Jun 01:06
b8ab6e7
Compare
Choose a tag to compare

Patch Changes

@rainbow-me/[email protected]

15 Jun 02:55
e82caf0
Compare
Choose a tag to compare

Minor Changes

  • 233a6d7: Breaking: Removed the chainId parameter from createConnector on the Wallet type (Custom Wallets).

    Note that all built-in wallets are using the new API. Most consumers will be unaffected. This change only affects consumers that have created/consumed custom wallets.

    If you previously derived RPC URLs from the chainId on createConnector, you can now remove that logic as wagmi now handles RPC URLs internally when used with configureChains.

    import { connectorsForWallets, wallet, Chain, Wallet } from '@rainbow-me/rainbowkit';
    import { chain, configureChains } from 'wagmi';
    import { alchemyProvider } from 'wagmi/providers/alchemy';
    import { publicProvider } from 'wagmi/providers/public';
    import { WalletConnectConnector } from 'wagmi/connectors/walletConnect';
    
    export interface MyWalletOptions {
      chains: Chain[];
    }
    
    -const chains = [chain.mainnet]
    +const { chains } = configureChains(
    +  [chain.mainnet],
    +  [
    +    alchemyProvider({ alchemyId: process.env.ALCHEMY_ID }),
    +    publicProvider(),
    +  ]
    +);
    
    export const rainbow = ({ chains }: MyWalletOptions): Wallet => ({
      ...
    - createConnector: ({ chainId }) => {
    + createConnector: () => {
    -   const rpc = chains.reduce(
    -     (rpcUrlMap, chain) => ({
    -       ...rpcUrlMap,
    -       [chainId]: chain.rpcUrls.default,
    -     }),
    -     {}
    -   );
        const connector = new WalletConnectConnector({
          chains,
          options: {
            qrcode: false,
    -       rpc,
          },
        });
      }
      ...
    }
    
    const connectors = connectorsForWallets([
      {
        groupName: 'Recommended',
        wallets: [
          rainbow({ chains }),
        ],
      },
    ]);

@rainbow-me/[email protected]

15 Jun 00:52
64fa3ae
Compare
Choose a tag to compare

Patch Changes

  • ce473cd: Fix WalletConnect in Brave when a large number of WalletConnect-based wallets have been configured

    Brave’s fingerprint prevention logic silently blocks WebSocket connections if too many are opened in the same session. Since we create a fresh WalletConnect connector instance for each wallet, consumers that have configured a large number of wallets can inadvertently break the connection flow in Brave.

    To fix this, we now share WalletConnect connector instances between wallets when the connectors are being provided with the same options.