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

@hwbdev/say-something

v1.0.10

Published

A package with some executable bins

Readme

This package has two binary executables. See the "bin" entry in package.json. We can use npx to run commands. Here are some forms:

npx <name> If is a binary executable in cwd/node_module/.bin, run it. Otherwise, if it is package name, install package in cache, then run the "primary" executable. The primary executable is determined by looking at that "bin" entry in the package's package.json file, and it is the one associated to a bin entry of the same name as the package.

npx --package=<package-name> -c "<shell-command> <args>" Install the package in cache, add the cache path to PATH, then run the shell command. This can be tested by running npx --package=@hwbdev/say-something -c "which say-something". You'll see the output shows the cache path. The -c flag and the quotation mark can also be ommited. The difference with or without the -c (and quotation) is that with the -c flag and quotation, variable expansions are delayed. If a package has multiple bin entries in the package.json file, this command can be used to execute the non-primary executable. For example, npx --package=@hwbdev/say-something print-test.

npx -c "<shell-command> <args>..." Add cwd/node_module/.bin to PATH and run the command provided. This can be tested by running npx -c "echo $PATH".

Note the last form is only useful if you already have installed the package (after running npm i <package> or npm i -g <package>).