MigrateX: wagmi v1 -> v2 codemod package
Production-ready deterministic migration package for wagmi v1 to v2, built for Codemod Registry and CLI workflows.
Published package
Current published version: 0.1.6
Repository: https://github.com/Nifemi0/migratex
What it does
- Scans repository usage of
wagmi - Runs conservative deterministic codemods
- Skips ambiguous cases instead of risky edits
- Writes migration outputs to
migratex-output/migrate-report.jsonmigrate-summary.txt- patch output (Git/snapshot mode support)
Safety model
- Deterministic-first, no broad guesses
- Unknown/low-confidence patterns are skipped and reported
- Dry-run default behavior
- No incorrect transformations observed in reviewed apply-mode diffs
Real Repository Validation
Batch apply-mode validation on real repositories with pattern-level scoring:
- Repositories tested: 7
- Repositories in-scope (
wagmi@1.x): 3 - Actionable patterns detected (in-scope): 72
- Patterns migrated deterministically (in-scope): 34
- Deterministic migration coverage (pattern-level): 47.2%
- False positives observed in reviewed diffs: 0
Case study: Tytandoteth/MAGBaseBridge
Repository: https://github.com/Tytandoteth/MAGBaseBridge
Actionable patterns detected: 28
Patterns migrated deterministically: 21
Deterministic coverage: 75.0%
Changed files: src/main.tsx, src/components/BridgeInterface.tsx, src/components/BridgeStatus.tsx, src/components/NetworkSelector.tsx, src/components/TransactionToast.tsx, src/hooks/useBridge.ts, src/hooks/useRpcProvider.ts, and 4 test files
False positives: 0
Validation:
- Build check on real repository run (
LIT-Protocol/lit-pkp-auth-demo): passed
Apply-mode validation (real writes, non-dry-run)
Validated with cloned repositories and wagmi-v2 --apply:
| Repository | wagmi version | Files changed | Changed files |
|---|---|---|---|
Tytandoteth/MAGBaseBridge | ^1.4.7 | 11 | src/main.tsx, multiple components/hooks, and test files |
rabbitholegg/gateway | 1.4.2 | 4 | contexts/ConnectKitProvider.tsx, components/ContractInteractionButton/ContractInteractionButton.tsx, components/pages/QuestDetails.tsx, components/QuestDetailPage/useQuestState.ts |
gerardcastell/insurechain | ^1.4.0 | 2 | apps/client-web/config/WagmiConfigProvider.tsx, libs/web/blockchain/src/lib/wallet-connector/useSiweAuth.ts |
bnb-chain/greenfield-data-marketplace-frontend | ^0.12.12 | 0 | out-of-scope (v0) |
LIT-Protocol/lit-pkp-auth-demo | ^0.12.8 | 0 | out-of-scope (v0) |
Example Outputs
Generated in migratex-output/:
migrate-report.jsonmigrate-summary.txtpatch.diff(when patch generation is run)
Testing
- Fixture tests for deterministic codemods (
tests/codemods/*) - Integration test for report persistence (
tests/integration/report-persistence.test.ts) - Optional real-repo integration test (
tests/integration/real-repo.test.ts) - CI workflow validation (
npm run codemod:workflow:validate)
Limitations / skipped patterns
- Current deterministic rules intentionally target high-confidence wagmi v1 patterns only.
- Ambiguous wrappers and non-standard abstractions are skipped and reported instead of edited.
- This favors zero-risk edits over broad automation; AI-assisted edge-case handling remains opt-in.
Local development
Run local CLI directly:
Codemod workflow commands
Validate package/workflow:
Run local workflow package:
Or with Codemod CLI directly:
Release and publish
Release quality gate:
Authenticate:
Publish (recommended staged publish to avoid local package bloat):
Direct publish:
CI/CD
- CI:
.github/workflows/ci.yml- build
- test
- codemod workflow validation
- Publish:
.github/workflows/publish.yml- tag trigger:
v* - OIDC trusted publishing via
codemod/publish-action@v1
- tag trigger:
Project structure
codemod.yaml- Codemod package metadataworkflow.yaml- workflow entrypointsrc/- scanner, codemods, orchestrator, validator, reportingtests/- fixture/unit/integration testsscripts/publish-staged.mjs- staged publish helper
Notes
- Package is published under user scope:
@nifemi0/wagmi-v1-to-v2. - If Codemod CLI asks for shell-step approvals during package execution, approve the workflow steps to proceed.