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

claude-test-runner

v0.1.0

Published

Unified test runner with Jest and Playwright support, parallel execution, and detailed failure reporting

Readme

claude-test-runner

Test runner designed for AI agent workflows. Runs Jest/Playwright suites and generates structured reports optimized for LLM consumption.

Why

When AI agents (Claude Code, Cursor, etc.) run tests, they face issues:

  • Token waste - reading verbose logs with ANSI escape codes, duplicate stack traces, framework boilerplate
  • Parsing overhead - different output formats from Jest vs Playwright vs other frameworks
  • Multiple commands - running npm run test:unit, npm run test:e2e separately
  • Noise - agents read full console output when they only need "what failed and why"

What it does

  • Runs all test suites with single npm test command
  • Generates summary.json - structured pass/fail data agents can parse instantly
  • Creates per-test markdown failure reports - clean error + stack trace, no ANSI codes
  • Supports Jest and Playwright JSON output parsing

Output

summary.json                    # Read this first: {"success": false, "failed": 2, ...}
test-results/
  failures/
    unit/
      user-service-login.md     # "Expected 200, got 401" + stack trace
      auth-middleware.md        # Individual failure details

Agent reads summary.json (50 tokens) instead of scrolling through 2000 lines of test output.

Setup

npm install claude-test-runner

Create test-runner.config.ts:

import type { Config } from 'claude-test-runner';

export default {
  artifactsDir: './test-results',
  reporters: ['console', 'json', 'markdown-failures'],
  suites: [
    { name: 'Unit', type: 'jest', command: 'npx jest --json', resultFile: 'unit.json' },
    { name: 'E2E', type: 'playwright', command: 'npx playwright test', resultFile: 'results.json' },
  ],
} satisfies Config;

Usage

npm test

Docs