Every production dApp built in 2022–2023 has the same problem sitting in its package.json : "wagmi" : "^1.4.12" , "ethers" : "^5.7.2" , "@rainbow-me/rainbowkit" : "^1.3.5" Enter fullscreen mode Exit fullscreen mode These three libraries are tightly coupled. wagmi v2 dropped ethers entirely in favor of viem. RainbowKit v2 requires wagmi v2. Migrating one without the others breaks everything. Every team I've seen approach this migration does it the same painful way: manually, file by file, over days or weeks, with a non-trivial chance of introducing bugs. I built a codemod that does it in one command. The Approach The core insight is that these migrations aren't independent — they're a stack. So the tool needs to treat them as one orchestrated workflow, not three separate tools you run and hope don't conflict. The workflow has three phases: Phase 1 — Detection Reads package.json and sets flags for which migrations to run. If you're already on wagmi v2 but still on ethers v5, it only runs the ethers migration.…