rainbowkit

• @rainbow-me/[email protected]

355402b: The wagmi peer dependency has been updated to 0.10.x.

Follow the steps below to migrate.

npm i @rainbow-me/rainbowkit@^0.10.0 wagmi@^0.10.0

If you use wagmi hooks in your application, you will need to check if your application has been affected by the breaking changes in wagmi.

You can see their migration guide here.

• @rainbow-me/[email protected]

49f0ec9: The wagmi peer dependency has been updated to 0.9.x.

Follow the steps below to migrate.

npm i @rainbow-me/rainbowkit@^0.9.0 wagmi@^0.9.0

If you use wagmi hooks in your application, you will need to check if your application has been affected by the breaking changes in wagmi.

You can see their migration guide here.

a1d6776: The wagmi peer dependency has been updated to 0.9.x.

Follow the steps below to migrate.

1. Upgrade RainbowKit and wagmi to their latest version:

npm i @rainbow-me/rainbowkit@^0.8.1 wagmi@^0.9.0

2. Check for breaking changes in wagmi

If you use wagmi hooks in your application, you will need to check if your application has been affected by the breaking changes in wagmi.

You can see their migration guide here.

6b37050: Breaking: Updated the wagmi peer dependency to 0.8.x.

Migration guide

1. Upgrade wagmi to ^0.8.0

npm i wagmi@^0.8.0

2. Follow wagmi's migration guide

You may need to follow wagmi's migration guide to migrate any breaking changes.

1de8203: Add data-testid attributes to support end-to-end testing.

The following set of data-testid attribute values are now provided.

• rk-connect-button
• rk-disconnect-button
• rk-account-button
• rk-chain-button
• rk-wrong-network-button
• rk-wallet-option-${wallet.id}
• rk-chain-option-${chain.id}
• rk-chain-option-disconnect
• rk-auth-message-button

These attributes can be targeted with a selector like this:

[data-testid="rk-connect-button"]

2e6bb8f: Support tree shaking of individual wallets by exposing them as separate imports via the new @rainbow-me/rainbowkit/wallets entry point.

In order to reduce bundle size, you can now select the individual wallets you want to import into your application.

Note that since wallets are no longer namespaced via the wallet object, all wallets now have a Wallet suffix.

-import { connectorsForWallets, wallet } from '@rainbow-me/rainbowkit';
+import { connectorsForWallets } from '@rainbow-me/rainbowkit';
+import {
+  injectedWallet,
+  rainbowWallet,
+  metaMaskWallet,
+  coinbaseWallet,
+  walletConnectWallet,
+} from '@rainbow-me/rainbowkit/wallets';

const wallets = [
-  wallet.injected({ chains }),
-  wallet.rainbow({ chains }),
-  wallet.metaMask({ chains }),
-  wallet.coinbase({ chains, appName: 'My App' }),
-  wallet.walletConnect({ chains }),
+  injectedWallet({ chains }),
+  rainbowWallet({ chains }),
+  metaMaskWallet({ chains }),
+  coinbaseWallet({ chains, appName: 'My App' }),
+  walletConnectWallet({ chains }),
];

2e6bb8f: The Steakwallet backwards compatibility layer has been removed. Omni should be used instead, available via the new @rainbow-me/rainbowkit/wallets entry point.

-import { wallet } from '@rainbow-me/rainbowkit';
+import { omniWallet } from '@rainbow-me/rainbowkit/wallets';

const wallets = [
-  wallet.steak({ chains }),
+  omniWallet({ chains }),
];

85eb3bd: Update the desktop Connect Modal to show "Recently Connected Wallets" within their respective group. Previously, they were being plucked into their own "Recent" group.

fbf9d82: Ensure styles.css directory is included in npm bundle

This is a follow-up to a fix released in v0.5.2 which added a compatibility layer for Jest's module resolver.

d12b75e: Fix crash in Linux/WSL when attempting to rename branch after running git init

When scaffolding a new project, we now honor the system default setting rather than forcibly renaming the branch.