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

@piyushdoorwar/yamlet

v1.13.0

Published

Run Yamlet API collections (Git-friendly YAML) from the command line or CI.

Readme

@piyushdoorwar/yamlet

Run Yamlet API collections from the command line, for example in CI. It fails the build when a request errors, returns a status outside 2xx/3xx, or a pm.test assertion fails.

Install

npm install -g @piyushdoorwar/yamlet
# or run without installing
npx @piyushdoorwar/yamlet run ./my-workspace

It installs the yamlet command. Requires Node.js 22 or newer.

Usage

yamlet run <workspace> [options]

<workspace> is a Yamlet workspace folder (it contains collections/ and environments/), or its parent: the same folder you open in the app. Requests run in tree order, collection by collection. Pre-request and post-response scripts run, and pm.test assertions are counted.

| Option | Meaning | |---|---| | -e, --env <name\|file> | Environment to use: a name from the workspace (dev) or a path to an environment YAML file | | -g, --globals <file> | Use these globals instead of the workspace's | | -c, --collection <name> | Only run this collection (repeat for several) | | -n, --iterations <n> | Run everything n times | | -d, --data <file> | CSV (with a header row) or JSON array of objects; one iteration per row. Values are available as {{column}} and pm.iterationData.get("column") | | --delay <ms> | Wait between requests | | --bail | Stop after the first failing request | | -r, --reporter <name> | table (default), json or junit | | -o, --out <file> | Write the json / junit report to a file | | --no-color | Plain output (also honors NO_COLOR) |

The exit code is 0 when every request passed and 1 otherwise.

yamlet run ./api --env dev
yamlet run ./api --env environments/staging.yaml --collection Payments --bail
yamlet run ./api --env dev --data users.csv --reporter junit --out yamlet-results.xml

GitHub Actions

- uses: actions/setup-node@v5
  with:
    node-version: 24
- name: API tests
  run: npx --yes @piyushdoorwar/yamlet run ./api --env ci --reporter junit --out yamlet-results.xml
- name: Publish results
  if: always()
  uses: actions/upload-artifact@v4
  with:
    name: yamlet-results
    path: yamlet-results.xml

License

MIT