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

@cartesi/wagmi-plugin

v1.0.0-alpha.2

Published

wagmi CLI plugin for Cartesi Rollups contracts

Readme

Cartesi wagmi CLI plugin

A wagmi CLI plugin that generates code for the Cartesi Rollups smart contracts straight from an official release: ABIs come from the foundry build artifacts tarball, and deployment addresses from the deployment addresses tarball.

Installation

pnpm add -D @cartesi/wagmi-plugin @wagmi/cli

Usage

Add the plugin to your wagmi.config.ts. By default it uses the tarballs of the rollups-contracts v3.0.0-alpha.6 GitHub release, verified against known SHA-256 hashes.

import { rollupsContracts } from "@cartesi/wagmi-plugin";
import { defineConfig } from "@wagmi/cli";

export default defineConfig({
    out: "src/generated.ts",
    plugins: [rollupsContracts()],
});

Then run codegen:

pnpm wagmi generate

Using a different release

Point artifacts and deployments at the tarballs of another rollups-contracts release, optionally with an expected SHA-256 hash for integrity verification:

const version = "3.0.0-alpha.6";
const releaseUrl = `https://github.com/cartesi/rollups-contracts/releases/download/v${version}`;

rollupsContracts({
    artifacts: {
        url: `${releaseUrl}/rollups-contracts-${version}-artifacts.tar.gz`,
        sha256: "ad1e0880766d25419fc6da1858ea4e7b9074b400e9d9ef68da88b12f4a8bba45",
    },
    deployments: {
        url: `${releaseUrl}/rollups-contracts-${version}-deployment-addresses.tar.gz`,
        sha256: "bd6ee9b339e0541ce464ea3368e5e70595627b35fe0a68c6f5e044ef433ab895",
    },
});

Selecting contracts

Use include and exclude to select which contracts are generated. Both accept contract names or regular expressions, and apply to every contract in the artifacts, whether it has a deployment or not:

  • Neither defined: all contracts are included.
  • Only include: only the matching contracts are included.
  • Only exclude: all contracts are included except the matching ones.
  • Both: include is applied first, then exclude.

For example, to generate only the Inputs and Outputs contracts:

rollupsContracts({
    include: ["Inputs", "Outputs"],
});

Or to generate all portal contracts except the interfaces:

rollupsContracts({
    include: [/Portal$/],
    exclude: [/^I[A-Z]/],
});

Behavior

  • Tarballs are downloaded and extracted to the OS temporary directory and cached across runs.
  • Deployed contracts get their address on every chain: a single address when it is identical across chains, or a per-chain record otherwise.

See the documentation for more details.