Migration Guide
Migrating RainbowKit
The wagmi peer dependency has been updated to 0.12.x
.
RainbowKit has adopted the WalletConnectLegacyConnector
connector in wagmi
for continued WalletConnect v1 support. Support for WalletConnect v2 and WalletConnectConnector
will soon be available as a patch release, without breaking changes.
Wallets will be transitioned automatically in future releases.
Follow the steps below to migrate.
The wagmi peer dependency has been updated to 0.11.x
.
Follow the steps below to migrate.
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.
The wagmi peer dependency has been updated to 0.10.x
.
Follow the steps below to migrate.
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.
The wagmi peer dependency has been updated to 0.9.x
.
Follow the steps below to migrate.
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.
The wagmi peer dependency has been updated to 0.8.x
.
Follow the steps below to migrate.
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.
If you're creating a custom wallet list, you must now import each wallet individually in order to reduce bundle size. Note that since wallets are no longer namespaced via the wallet
object, all wallets now have a Wallet
suffix.
Also note that the Steakwallet backwards compatibility layer has been removed. Omni should be used instead.
RainbowKit has updated the wagmi
peer dependency to 0.5.x
.
Follow the steps below to migrate.
Upgrade RainbowKit and wagmi to their latest version
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.
Removed the chainId
parameter from createConnector
on the Wallet
type.
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
.
RainbowKit has updated the wagmi
peer dependency to ^0.4
.
Follow the steps below to migrate.
Upgrade RainbowKit and wagmi to their latest version
Import configureChains
from wagmi instead of RainbowKit:
RainbowKit no longer exports an apiProvider
API. Replace it with your desired provider from wagmi.
Import alchemyProvider
from wagmi/providers/alchemy
.
Import infuraProvider
from wagmi/providers/infura
.
Import jsonRpcProvider
from wagmi/providers/jsonRpc
.
Import publicProvider
from wagmi/providers/public
.
Rename WamgiProvider
to WagmiConfig
.
And you're done! 🌈