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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@janwirth/b2b

v0.0.17

Published

✨ Write tests in human language (Gherkin) and verify program behavior with headless browser automation (Puppeteer).

Downloads

36

Readme

B2B 🎛️🎚️🎛️

✨ Write tests in human language (Gherkin) and verify program behavior with headless browser automation (Puppeteer).

🚀 Easy setup. No test-ids needed in your html - it reads the page like a human.

Demo

Quick Start

  1. 🌐 Start a server on localhost:3000

  2. ⚡ Run bun x @janwirth/b2b init This will create an example feature file:

    Feature: Example
    
    Scenario: Example
      When I open localhost:3000
      Then I see "Hello, World!"
  3. 👀 Run bun x @janwirth/b2b watch to start interactive mode

  4. ✅ Run bun x @janwirth/b2b run to run all features

Watch mode

Use Cases

  • 🛡️ Quality Assurance: Prevent regression bugs. Avoid the "two steps forward, one step back" problem.

  • 🗺️ Design Handoff via (Happy) Path Mapping: Map user journeys through UI designs. Gherkin files mirror design complexity and reveal user effort required.

  • 🤝 Client Handoff: Demonstrate functionality with executable specifications. Clients see exactly how features work; requirement changes reflect immediately in test scenarios.

  • 🤖 AI-Assisted Engineering: Natural language test scenarios work well with AI tools like Cursor. Unit tests fall short for long-running processes and UI testing. The structured Gherkin format helps AI understand requirements and suggest improvements.

Features

  • 📝 Feature parser
  • 🏷️ Annotations @skip and @focus
  • 📹 Screen recordings and failure screenshots
  • 👀 Watch mode
  • 🎯 Content-based element finding
  • 👁️ OCR image processing

Perspectives

  • 🎬 Effortlessly record product demos for marketing purposes using the latest UI

Creating new Features

I used this prompt to generate the mock reset step:

Let's use @tdd.mdc to create a new feature.

We need to have a step that pings an endpoint to reset the application for a testable state (clearing test-created data etc.)

The @mock-server.ts  should have some isCleared variable that is visible in an endpoint so that the test runner can verify it with I see

When I open localhost:3000/reset-status
Then I see "stale data"
When I ping localhost:3000/reset
And I reload
Then I see "cleared"