@rainbow-me/rainbowkit@0.12.17

Patch Changes

• e1fd3df: Fixed an issue with MetaMask Mobile's connector that blocked WalletConnect pairings

@rainbow-me/rainbowkit@1.0.4

Patch Changes

• 6d361b4: Support for wagmi 1.3.x and viem 1.1.x peer dependencies.

@rainbow-me/rainbowkit@0.12.16

Patch Changes

• 6af1db7: Upgraded minimum wagmi peer dependency to 0.12.18 for improved WalletConnect v2 support.

@rainbow-me/rainbowkit@1.0.3

Patch Changes

• d00c777: Added zora and zoraTestnet chain support

@rainbow-me/rainbowkit@1.0.2

Patch Changes

• e2b1072: Support for WalletConnect v2 is now standard in RainbowKit.

  Every dApp that relies on WalletConnect now needs to obtain a projectId from WalletConnect Cloud. This is absolutely free and only takes a few minutes.

  This must be completed before WalletConnect v1 bridge servers are shutdown on June 28, 2023.

  Upgrade RainbowKit and provide the projectId to getDefaultWallets and individual RainbowKit wallet connectors like the following:

  const projectId = 'YOUR_PROJECT_ID';
  
  const { wallets } = getDefaultWallets({
    appName: 'My RainbowKit App',
    projectId,
    chains,
  });
  
  const connectors = connectorsForWallets([
    ...wallets,
    {
      groupName: 'Other',
      wallets: [
        argentWallet({ projectId, chains }),
        trustWallet({ projectId, chains }),
        ledgerWallet({ projectId, chains }),
      ],
    },
  ]);

  You can read the full migration guide here.

  Advanced options

  If a dApp requires supporting a legacy wallet that has not yet migrated to WalletConnect v2, the WalletConnect version can be overriden.

  metaMaskWallet(options: {
    chains: Chain[];
    walletConnectVersion: '1',
  });

  Once the WalletConnect v1 servers are shutdown, a custom bridge server is required.

  walletConnectWallet(options: {
    chains: Chain[];
    version: '1',
    options: {
      bridge: 'https://bridge.myhostedserver.com',
    },
  });
  
  customWallet(options: {
    chains: Chain[];
    walletConnectVersion: '1',
    walletConnectOptions: {
      bridge: 'https://bridge.myhostedserver.com',
    },
  });

  Reference the docs for additional supported options.

• e2b1072: The wagmi peer dependency has been updated to ~1.2.0. RainbowKit remains compatible with ~1.1.0 and ~1.0.1.

  The viem peer dependency has been updated to ^1.0.0. RainbowKit remains compatible with ~0.3.19 and beyond.

  It is recommended that you upgrade to recent versions of wagmi and viem to ensure a smooth transition to WalletConnect v2.

  Reference the viem migration guide here.

rainbow-me/rainbowkit@0.12.15

Patch Changes

• e2b1072: Support for WalletConnect v2 is now standard in RainbowKit.

  Every dApp that relies on WalletConnect now needs to obtain a projectId from WalletConnect Cloud. This is absolutely free and only takes a few minutes.

  This must be completed before WalletConnect v1 bridge servers are shutdown on June 28, 2023.

  Upgrade RainbowKit and provide the projectId to getDefaultWallets and individual RainbowKit wallet connectors like the following:

  const projectId = 'YOUR_PROJECT_ID';
  
  const { wallets } = getDefaultWallets({
    appName: 'My RainbowKit App',
    projectId,
    chains,
  });
  
  const connectors = connectorsForWallets([
    ...wallets,
    {
      groupName: 'Other',
      wallets: [
        argentWallet({ projectId, chains }),
        trustWallet({ projectId, chains }),
        ledgerWallet({ projectId, chains }),
      ],
    },
  ]);

  You can read the full migration guide here.

  We are continuing support for 0.12.x in case your dApp has not yet upgraded to wagmi v1 and RainbowKit v1.

  It is recommended that 0.12.x dApps begin to upgrade to wagmi v1, as stability improvements for WalletConnect v2 will only be included in future versions of wagmi.

  Advanced options

  If a dApp requires supporting a legacy wallet that has not yet migrated to WalletConnect v2, the WalletConnect version can be overriden.

  metaMaskWallet(options: {
    chains: Chain[];
    walletConnectVersion: '1',
  });

  Once the WalletConnect v1 servers are shutdown, a custom bridge server is required.

  walletConnectWallet(options: {
    chains: Chain[];
    version: '1',
    options: {
      bridge: 'https://bridge.myhostedserver.com',
    },
  });
  
  customWallet(options: {
    chains: Chain[];
    walletConnectVersion: '1',
    walletConnectOptions: {
      bridge: 'https://bridge.myhostedserver.com',
    },
  });

  Reference the docs for additional supported options.

@rainbow-me/create-rainbowkit@0.2.3

Patch Changes

• e2b1072: The wagmi peer dependency has been updated to ~1.2.0. RainbowKit remains compatible with ~1.1.0 and ~1.0.1.

  The viem peer dependency has been updated to ^1.0.0. RainbowKit remains compatible with ~0.3.19 and beyond.

@rainbow-me/rainbowkit@1.0.1

Patch Changes

• 9432a2f: The ConnectButton component is now tagged with use client; to support the Next 13 App Router and server-side rendered dApps. You can reference a full app/ directory implementation example here.

• b2c66ff: Modified acceptable peer dependency versions to ensure proper peer warnings for future versions of wagmi and viem. wagmi now requires ~1.0.1 and viem now requires ~0.3.19.

• bcb3d18: Modal Hooks including useConnectModal, useAccountModal, and useChainModal now each return a boolean with the status of the modal.

  const { connectModalOpen } = useConnectModal();
  const { accountModalOpen } = useAccountModal();
  const { chainModalOpen } = useChainModal();

@rainbow-me/create-rainbowkit@0.2.2

Patch Changes

• 86a1ddd: Upgraded templates to support Next 13

@rainbow-me/create-rainbowkit@0.2.1

Patch Changes

• 371c988: Adopted fs, net, and tls polyfills in the @rainbow-me/create-rainbowkit templates for better wagmi@1 and viem Webpack bundler support.

  These modules are required by WalletConnect packages upstream, and were previously polyfilled by ethers. Reference the discussion here.