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

@avasapp/dhoni

v0.5.2

Published

dhoni CLI — React Native build tooling and dev bundle distribution

Readme

@avasapp/dhoni

The dhoni CLI, distributed as prebuilt binaries so nobody has to install Go or rebuild after every pull.

bun add -g @avasapp/dhoni
dhoni help

Private to the @avasapp scope — installing needs a token that can read it.

How it works

The wrapper package ships only a Node shim. The actual binary arrives through optionalDependencies, one package per platform, each declaring os and cpu so npm installs exactly the one that matches:

| Platform | Package | | ----------- | ------------------------------- | | macOS arm64 | @avasapp/dhoni-darwin-arm64 | | macOS x64 | @avasapp/dhoni-darwin-x64 | | Linux arm64 | @avasapp/dhoni-linux-arm64 | | Linux x64 | @avasapp/dhoni-linux-x64 |

Windows is not published. Adding it is a one-line change to TARGETS in scripts/release-cli.sh, plus a .exe case in the shim.

Installing with --no-optional leaves the shim with no binary to run. It detects that and says so rather than failing with a confusing resolution error.

Releasing

scripts/release-cli.sh 0.2.0 --dry-run   # cross-compile and pack
scripts/release-cli.sh 0.2.0             # publish

The script cross-compiles all four targets, stamps the version into every manifest, and publishes the platform packages before the wrapper. That order matters: the wrapper pins its platform packages to an exact version, so publishing it first opens a window where installs resolve nothing and the CLI silently has no binary.