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

textrun-npm

v0.7.0

Published

This package provides [Text-Runner](https://github.com/kevgo/text-runner) actions for verifying the documentation of npm packages.

Readme

Text-Runner Actions for npm

This package provides Text-Runner actions for verifying the documentation of npm packages.

Installation

To use these actions, add this package as a development dependency by running npm i -D textrun-npm.

Verify installation instructions

The npm/install action verifies installation instructions for an npm package. As an example, let's assume we are testing the documentation of an npm package called foobar. Its package.json file would contain amongst other things:

{
  "name": "foobar"
}

In the documentation of this npm package, we want to document how to install this package. It would contain a section that looks something like this:

Install the foobar package by running:

<pre type="npm/install">
npm install foobar
</pre>

or with Yarn:

<pre type="npm/install">
yarn add foobar
</pre>

Text-Runner verifies that the installation instructions contain the correct name of the npm package.

Verify exported binaries

The npm/exported-executable action verifies documentation of exported binaries of npm packages. Let's say our foobar package provides an executable file bin/foo, which is listed as a binary in the package.json file:

{
  "name": "foobar",
  "bin": {
    "foo": "bin/foo"
  }
}

The documentation for the "foobar" package would document this binary like this:

After you install the "foobar" package, you can run the
<code type="npm/exported-executable">foo</code> command in the terminal.

Verify installed binaries

The npm/installed-executable action verifies binaries installed by other npm packages. Let's say you develop technical documentation for a codebase that uses the cucumber command provided by the npm cucumber package:

To run the end-to-end tests, run
<code type="npm/installed-executable">cucumber</code> in the terminal.

Verify script names defined in package.json

The npm/script-name action verifies that you document scripts that your package.json file defines correctly.

Let's say your npm package has this package.json file:

{
  "name": "foobar",
  "scripts": {
    "lint": "echo linting"
  }
}

And your documentation says:

To run the linters, please run the
<code type="npm/script-name">lint</code> script.

Verify calls of scripts defined in package.json

The npm/script-call action verifies that you document calls of scripts defined in your package.json file correctly.

Let's say your npm package has this package.json file:

{
  "name": "foobar",
  "scripts": {
    "lint": "echo linting"
  }
}

And your documentation says:

To run the linters, please execute
<code type="npm/script-call">npm run lint</code>.