npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@deployoor/wagmi

v0.3.0

Published

Source deployoor deployments into @wagmi/cli — typed contract objects for your app.

Readme

@deployoor/wagmi

A @wagmi/cli plugin that sources contracts from a deployoor deployments/ folder.

deployoor deploys your contracts and records each one as deployments/<chainId>-<network>/<Contract>.json. This plugin reads that folder and hands the contracts to @wagmi/cli, which generates the ABIs, per-chain address maps, and framework bindings. You write addresses nowhere — they come from your own deploys.

Install

pnpm add -D @deployoor/wagmi @wagmi/cli

Usage

// wagmi.config.ts
import { defineConfig } from "@wagmi/cli";
import { actions } from "@wagmi/cli/plugins";
import { deployments } from "@deployoor/wagmi";

export default defineConfig({
  out: "src/generated.ts",
  plugins: [
    deployments({ path: "./deployments" }), // default: './deployments'
    actions(), // or react(), or nothing
  ],
});
wagmi generate

The same deployment name across chains is folded into a single entry whose address is a { [chainId]: address } map — exactly the shape @wagmi/cli wants for multi-chain contracts. If records with the same deployment name have different ABIs, generation fails so you can give them distinct deploymentName values instead of silently getting the wrong type.

API

deployments(options?)

Returns a @wagmi/cli Plugin.

  • options.path — path to the deployoor deployments/ folder. Default './deployments'.

readDeploymentContracts(deploymentsPath)

The underlying reader, exported for tooling and tests. Walks the folder, validates each JSON record, and returns @wagmi/cli ContractConfig[] grouped by deployment name. JSON files that aren't deployoor deployment records are skipped.

License

MIT