Releases: rainbow-me/rainbowkit
@rainbow-me/[email protected]
Patch Changes
-
8841891: Added real-time balance fetching based on the Recent Transaction API. As a transaction is confirmed on-chain, the user's gas balance will be updated to reflect the transaction.
import { useAddRecentTransaction } from "@rainbow-me/rainbowkit"; export default () => { const addRecentTransaction = useAddRecentTransaction(); return ( <button onClick={() => { addRecentTransaction({ hash: "0x...", description: "...", }); }} > Add recent transaction </button> ); };
@rainbow-me/[email protected]
@rainbow-me/[email protected]
@rainbow-me/[email protected]
Patch Changes
- 4dd1e45: Fixed an issue that allowed duplicate wallets to be added to the Connect Modal when using
connectorsForWallets
- 1a0f209: Added a small check to throw an error if the wallet list is empty overall or empty within any category.
- ec41346: Amended the
getDefaultConfig
return type to prevent indirect type annotation errors and better infer type for parameters from Wagmi'screateConfig
. - fc4d7e1: Resolved a bug where if
multiInjectedProviderDiscovery
was set tofalse
theroninWallet
would prevent showingOpening Ronin Wallet...
UI in the connect modal. - 81ba812: Added support for
zetachain
andzetachainAthensTestnet
testnet chain - b11118f: Added Kaikas Wallet support with
kaikasWallet
wallet connector and addedklaytn
chain withklaytnBaobab
testnet support.
@rainbow-me/[email protected]
@rainbow-me/[email protected]
@rainbow-me/[email protected]
Patch Changes
- b80e8fa: Improved the synchronous connection flow for the
RainbowButton
component
@rainbow-me/[email protected]
Patch Changes
- 524d7a0:
connectModalOpen
state for theuseConnectModal
hook will now also encompass the Web3Modal modal presentation status for users that interact withwalletConnectWallet
- 2f637e4: Fixed a bug where wagmi would throw
ChainNotConfiguredError
ifmainnet
is not configured as a chain. This is happening when fetching ens name and ens avatar. - c021746: Resolved an issue where the Connect Modal wallet list would appear empty for EIP-6963 connectors when using the
WalletButton
component - df572f1: Resolved an issue for Custom Wallets that displayed a "missing translation" error for instructions during connect and installation flows. Now Custom Wallets will display their original strings without attempted translation.
@rainbow-me/[email protected]
Patch Changes
- bb56562: Fixed a bug where the
showBalance
prop on<ConnectButton />
didn't accept a boolean, and had only accepted responsive modal values. - 5149dbd: Added Ramper Wallet support with
ramperWallet
wallet connector - 1e7d3f4: Added Ronin Wallet support with
roninWallet
wallet connector - c16541a: Added Kresus support with
kresusWallet
wallet connector - dbca966: Added Bloom Wallet support with
bloomWallet
wallet connector - 1a08977: Added EIP-6963 support for
coin98Wallet
wallet connector - f69c0e1: Added support for
ronin
chain
@rainbow-me/[email protected]
Major Changes
-
aa0269e: Breaking:
The wagmi and viem peer dependencies have reached
2.x.x
with breaking changes.Follow the steps below to migrate.
1. Upgrade RainbowKit,
wagmi
, andviem
to their latest versionsnpm i @rainbow-me/rainbowkit@2 wagmi@2 [email protected]
2. Install
@tanstack/react-query
peer dependencyWith Wagmi v2, TanStack Query is now a required peer dependency.
Install it with the following command:
npm i @tanstack/react-query
3. Upgrade your RainbowKit and Wagmi configurations
import '@rainbow-me/rainbowkit/styles.css' + import { QueryClient, QueryClientProvider } from '@tanstack/react-query' - import { createPublicClient, http } from 'viem' - import { WagmiConfig } from 'wagmi' + import { WagmiProvider, http } from 'wagmi' - import { configureChains, createConfig } from 'wagmi' import { mainnet } from 'wagmi/chains' import { RainbowKitProvider } from '@rainbow-me/rainbowkit' - import { getDefaultWallets, connectorsForWallets } from '@rainbow-me/rainbowkit' + import { getDefaultConfig } from '@rainbow-me/rainbowkit' /* getDefaultWallets is now optional */ - const { wallets } = getDefaultWallets({ - appName: 'RainbowKit demo', - projectId: 'YOUR_PROJECT_ID', - chains, - }) /* connectorsForWallets is now optional */ - const connectors = connectorsForWallets([...wallets]) - const { chains, publicClient } = configureChains( - [mainnet, sepolia], - [publicProvider(), publicProvider()], - ) - const config = createConfig({ - autoConnect: true, - publicClient, - }) /* New API that includes Wagmi's createConfig and bundles getDefaultWallets and connectorsForWallets */ + const config = getDefaultConfig({ + appName: 'RainbowKit demo', + projectId: 'YOUR_PROJECT_ID', + chains: [mainnet], + transports: { + [mainnet.id]: http(), + }, + }) + const queryClient = new QueryClient() const App = () => { return ( - <WagmiConfig config={config}> + <WagmiProvider config={config}> + <QueryClientProvider client={queryClient}> - <RainbowKitProvider chains={chains}> + <RainbowKitProvider> {/* Your App */} </RainbowKitProvider> + </QueryClientProvider> - </WagmiConfig> + </WagmiProvider> ) }
You can read an in-depth migration guide here.
4. Check for breaking changes in
wagmi
andviem
If you use
wagmi
hooks andviem
actions in your dApp, you will need to follow the migration guides for v2: