Input: optionally a target viem version. Without one, use the latest
release on npm.
viem is both a dependency and a peer dependency across the workspace. An
upgrade is complete only when every range agrees and every test passes.
Find every manifest that lists viem under dependencies,
devDependencies, or peerDependencies (grep -l '"viem"' */package.json */*/package.json). Bump each range to the target version. Peer ranges use
the same caret form the manifest already uses.
Run pnpm install so pnpm-lock.yaml resolves the new version. Do not
hand-edit the lockfile.
Read the viem changelog between the old and new versions. List every
breaking change that touches an API this repo calls (transports, actions,
defineChain, error classes, formatters).
Run the tree-wide typecheck. Fix compile errors caused by the upgrade in
the packages that own them; do not loosen types to make errors go away.
Run the tree-wide tests. Snapshot diffs that are only a version string
are expected: update them. A snapshot whose content changes from a
successful result to an error, or whose values change without a viem
changelog entry explaining why, is a regression: fix the code, not the
snapshot, and say so in the PR body.
Add one patch changeset naming every package whose manifest changed,
unless a breaking viem change surfaces through tevm's public types, in
which case the changeset is minor and names the affected exports.
PR title: ⬆️ chore(deps): upgrade viem to <version>. Body: the version
range, the breaking changes considered, and every snapshot that changed with
the reason. Keep unrelated dependency bumps out of this PR.
1---2name: upgrade-viem3description: Upgrade viem4---5# Upgrade viem67Input: optionally a target viem version. Without one, use the latest8release on npm.910viem is both a dependency and a peer dependency across the workspace. An11upgrade is complete only when every range agrees and every test passes.12131. Find every manifest that lists `viem` under `dependencies`,14 `devDependencies`, or `peerDependencies` (`grep -l '"viem"' */package.json15 */*/package.json`). Bump each range to the target version. Peer ranges use16 the same caret form the manifest already uses.172. Run `pnpm install` so `pnpm-lock.yaml` resolves the new version. Do not18 hand-edit the lockfile.193. Read the viem changelog between the old and new versions. List every20 breaking change that touches an API this repo calls (transports, actions,21 `defineChain`, error classes, formatters).224. Run the tree-wide typecheck. Fix compile errors caused by the upgrade in23 the packages that own them; do not loosen types to make errors go away.245. Run the tree-wide tests. Snapshot diffs that are only a version string25 are expected: update them. A snapshot whose content changes from a26 successful result to an error, or whose values change without a viem27 changelog entry explaining why, is a regression: fix the code, not the28 snapshot, and say so in the PR body.296. Add one `patch` changeset naming every package whose manifest changed,30 unless a breaking viem change surfaces through tevm's public types, in31 which case the changeset is `minor` and names the affected exports.3233PR title: `⬆️ chore(deps): upgrade viem to <version>`. Body: the version34range, the breaking changes considered, and every snapshot that changed with35the reason. Keep unrelated dependency bumps out of this PR.
Run npx skillmds@latest add evmts/upgrade-viem in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Upgrade viem It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
evmts (@evmts) published this skill. Their other Agent Skills are listed on their SkillMD profile.
evmts