Skip to main content

​
Prerequisites

  • Node & a package manager (npm, pnpm, or yarn).
  • A project already using AppKit:
"dependencies": {
  "@reown/appkit": "1.8.1",
  "@reown/appkit-adapter-wagmi": "1.8.1"
}
More @reown/* packages can be used in your project. This is an example of a project using AppKit and Wagmi for EVM networks.

​
1. Find the latest AppKit version

Use the registry to read the current published version (do this once, and use the same number for every @reown/* package you install): 
# npm
npm view @reown/appkit version

# pnpm
pnpm view @reown/appkit version

# yarn
yarn npm info @reown/appkit version

# bun
bun info @reown/appkit version
You can also eyeball the version on npm’s package page for @reown/appkit.

​
2. Update your dependencies (all @reown/* to the same version)

Replace X.Y.Z below with the version you just looked up. 
npm install \
  @reown/appkit@X.Y.Z \
  @reown/appkit-adapter-wagmi@X.Y.Z
AppKit publishes its packages in coordinated releases; mixing versions can cause subtle peer-dep and type mismatches, so keep @reown/* on the exact same X.Y.Z.

​
3. Pin in package.json (Optional)

If you prefer explicit pins (no carets), update package.json: 
"dependencies": {
  "@reown/appkit": "X.Y.Z",
  "@reown/appkit-adapter-wagmi": "X.Y.Z"
}
Then reinstall to refresh your lockfile: 
rm -rf node_modules package-lock.json && npm install

​
4. Try Locally (Optional)

After updating dependencies, test the changes locally: 
npm run dev

​
5. Commit & CI

Commit package.json + the lockfile, and let CI run your build/tests.

​
6. Done ✅

That’s it. This keeps your AppKit stack consistent and aligned with the latest release. All the releases information are available in the AppKit GitHub Releases.
⌘I