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

@zuplo/test

v1.4.4

Published

Type definitions for the Zuplo test runner

Readme

@zuplo/test

Type definitions for the test constructs (describe, it, beforeEach, …) and the TestHelper object that @zuplo/cli injects when it runs a Zuplo project's tests. There is no runtime code here — the implementation is generated by the CLI — so dist/index.d.ts is hand-maintained rather than compiled.

This package was moved here from the standalone zuplo/test repository.

Releasing

@zuplo/test is not published as part of a core release. It has its own tag prefix (test-v) and its own workflow, so a version only goes out when someone asks for one:

  1. Run the Run Release workflow and pick @zuplo/test as the product.
  2. That computes and pushes the next test-v<major>.<minor>.<patch> tag.
  3. Pushing the tag runs release-test.yaml, which publishes to npmjs.com and GitHub Packages and cuts a GitHub release.

The version field below is informational — the release workflow overwrites it with the version from the tag before publishing. Because there are no existing test-v* tags yet, the first release seeds its version from that field.

Consequences of being outside the core release:

  • packages/test is excluded from the npm workspaces list, so @zuplo/test still resolves from the registry for local development and CI type-checking. Editing dist/index.d.ts here does not change what npm ci installs until a release goes out.
  • scripts/set-versions.mjs skips this directory so core releases don't overwrite the version.
  • After releasing a new version, bump the @zuplo/test pin in packages/zuplo/package.json (and refresh the lockfile) if the meta-package should ship the new types.