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

@beoks/belay

v1.0.0

Published

Black-box scenario test harness — executable specs that survive rewrites. Zero dependencies.

Readme

Belay is a black-box scenario harness. Your project goes in src/. Your specs go in test/ as Gherkin scenarios backed by TypeScript step definitions. One command boots the mock infrastructure, starts your app, waits until it is genuinely ready, runs every scenario, collects evidence, and tears everything down.

The specs never import your code. They only knock on the surfaces a user can reach — HTTP, GraphQL, WebSocket, gRPC, CLI, the browser. That single constraint is what makes them survive a rewrite.

Install

npm install -g @beoks/belay
belay init
belay run

Or per project:

npm install -D @beoks/belay
npx belay init

Requires Node ≥ 22. Zero runtime dependencies.

Writing a step

import { Given, Then, expect, World } from '@beoks/belay';

Given('the audit system answers {int}', function (this: World, status: number) {
  this.mock.audit.onPost('/events').reply(status);   // the stub is ours; program it freely
});

Then('the status is {int}', function (this: World, status: number) {
  expect(this.last.status).toBe(status);
});

Commands

belay init                    # scaffold config + test skeleton (interactive)
belay init --from ../my-api   # adopt an existing project (--link symlink|submodule|move|copy)
belay analyze                 # inventory existing code into a scenario checklist
belay run                     # boot → run → collect → tear down
belay run --only L1           # one layer          (--upto L2 also works)
belay run --grep signup       # filter by name     (--tags "@smoke" too)
belay run --bail              # stop at first failure
belay run --watch             # re-run on change; the environment stays up
belay new L1-account/signup   # create a .feature and its steps together
belay approve cart-empty      # accept a visual baseline, after reviewing the diff
belay report --open           # open the latest HTML report
belay doctor                  # check ports, Docker, engines, config
belay down                    # clean up a kept environment

Optional peers

The browser driver and visual gate need optional peers, installed only if you use them:

npm i -D playwright pngjs pixelmatch && npx playwright install chromium

The gRPC driver needs @grpc/grpc-js and @grpc/proto-loader.

Language

Scaffolding and Gherkin are English by default; set BELAY_LANG=ko for Korean.

belay init                # English scaffolding and Gherkin
BELAY_LANG=ko belay init  # Korean scaffolding and Gherkin

The full design document covers the layer model, the driver surfaces, the mock infrastructure and the agent workflow.

MIT © BEOKS