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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@dao-dao/utils

v2.7.1-rc.5

Published

A collection of simple utility functions used across packages.

Downloads

56

Readme

@dao-dao/utils

A collection of simple utility functions used across packages.

Scripts

cwgen

Generate types, clients, and queries for CosmWasm contracts, modify them for use with this codebase, and install them in the right places.

Usage: yarn cwgen [options]

Options:
  -n, --name <name>  contract name
  -p, --path <path>  path to contract folder that contains "schema" folder
  -h, --help         display help for command

log-code-ids

Get Code IDs for a chain in the format for a dao-contracts tagged release.

Usage: yarn log-code-ids [options]

Options:
  -c, --chain-id <string>  chain ID
  -h, --help               display help for command

dump-go-relayer

Dump the specified chain Polytone connection(s) in the format expected by the Go relayer.

Usage: yarn dump-go-relayer [options]

dump Polytone relayer entries for one or multiple chains. passing no arguments will dump entries for all chains

Options:
  -s, --src <string>   source chain(s)
  -d, --dest <string>  destination chain(s)
  -h, --help           display help for command
  • To dump all entries for all chains, pass no arguments.
  • To dump the entries out of a specific chain and into another, specify both chains (with -s and -d).
  • To dump all entries coming out of a specific chain, specify the source chain with -s and no destination chain.
  • To dump all entries going into a specific chain, specify the destination chain with -d and no source chain.

dump-hermes-relayer

Dump the specified chain Polytone connection(s) in the format expected by the Hermes relayer.

Usage: yarn dump-hermes-relayer [options]

dump Polytone relayer entries for one or multiple chains. passing no arguments will dump entries for all chains

Options:
  -a, --chain-a <string>  chain A
  -b, --chain-b <string>  chain B
  -m, --many <string>     comma-separated list of chains to dump
  -h, --help              display help for command

To dump the entries between two specific chains, specify both chains (with -a and -b). To dump all entries for one or multiple chains, use either -a, -b, or -m. To dump all entries for all chains, pass no arguments.

verify-code-ids

Validate that versions and code IDs in the codeIds.json file are correct by finding contracts that currently exist on-chain for each code ID and checking their version info.

Usage: yarn verify-code-ids

verify-code-hashes

Validate that the code hashes in the codeHashes.json file are correct by comparing with their on-chain hashes. This is only needed for Secret Network.

Usage: yarn verify-code-hashes