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

@piwitests/server

v0.62.0

Published

Self-hosted dashboard that keeps and explains your Playwright test results — run with npx @piwitests/server

Readme

@piwitests/server

Run the self-hosted Piwi Dashboard server — a permanent home for your Playwright test results — with a single command, no Docker required.

Docker is the recommended way to run Piwi in production (pinned runtime, isolated environment): see the deployment guide. This npm package is a low-friction path for a quick local run or environments where Docker isn't available.

Requirements

  • Node.js 22+

Quick start

npx @piwitests/server

Then open http://localhost:3000.

The server creates a .data/ directory in your current working directory to hold the SQLite database (.data/piwi.db) and file storage (.data/storage/ — HTML reports, traces, attachments). Run the command from the same directory each time to keep your data, or install it as a dependency and add a script:

npm install @piwitests/server
{
  "scripts": {
    "piwi": "piwi-server"
  }
}

Configuration

All configuration is via environment variables (same as the Docker image). PORT (default 3000) sets the listen port; everything else is a PIWI_* variable documented — with its default and whether the Settings UI can override it — in the configuration reference. Most deployments set at least PIWI_SECRET_KEY, the master key for encrypting secrets stored in the database (AI API keys, SCM tokens). Unset, saving any of those credentials fails, so set it in any real deployment. Generate one with:

node -e "console.log(require('node:crypto').randomBytes(32).toString('hex'))"

Enable multi-user access with PIWI_AUTH_ENABLED=true plus PIWI_AUTH_SECRET, and point at PostgreSQL with PIWI_DATABASE_URL.

Set variables the usual way for your shell — for example, on a different port:

# Linux / macOS
PORT=8080 npx @piwitests/server
# Windows (PowerShell)
$env:PORT='8080'; npx @piwitests/server

The server listens on 127.0.0.1 only: with authentication off, anyone who reaches the port is an administrator. To serve other machines, enable authentication and set HOST=0.0.0.0.

Sending results

Add the @piwitests/reporter to your Playwright project and point it at this server — see the getting started guide.

License

FSL-1.1-MIT (fair source): free to use, self-host and modify, at work too. It rules out offering Piwi, or a product built from it, as a commercial product or service that competes with it. Each release becomes MIT two years after it is published. See License.