You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wagmi v1 was released recently, replacing ethers with viem, supporting BigInt natively, removing Goerli (deprecated testnet) support, and other useful changes.
As a developer, I would like ssx to use wagmi v1 to take advantage of its modern features (and without needing to implement workarounds to juggle multiple versions of wagmi, such as peer deps).
As a user, I would love to use software that uses up-to-date dependencies for security and UX benefits.
The text was updated successfully, but these errors were encountered:
Hey @coopbri! We've looked at migrating to Wagmi v1 — it's on our radar and roadmap! We are supporters of Wagmi and it's important to us to make sure our libraries are really easy to use alongside great packages like Wagmi. The transition to viem away from ethers introduces a bit of complexity to our library's implementation (which aims to have broad compatibility). We are working on this and look forward to pushing out updates
Is there an existing issue for this?
Feature
wagmi v1 was released recently, replacing
ethers
withviem
, supportingBigInt
natively, removing Goerli (deprecated testnet) support, and other useful changes.Migration guide: https://wagmi.sh/core/migration-guide
User Stories
As a developer, I would like ssx to use wagmi v1 to take advantage of its modern features (and without needing to implement workarounds to juggle multiple versions of wagmi, such as peer deps).
As a user, I would love to use software that uses up-to-date dependencies for security and UX benefits.
The text was updated successfully, but these errors were encountered: