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

pw-cucumber-triage-agent

v0.1.0

Published

AI-assisted, rule-based Playwright + Cucumber failure triage CLI with business-friendly reporting.

Downloads

368

Readme

PW Cucumber Triage Agent

AI-assisted, rule-based CLI for triaging Playwright + Cucumber failures.

Quick Start

Requirements: Node 18+

npm install
npm run start -- --cucumberJson path/to/cucumber.json --html triage-report.html --out triage-eval.json

Typical Usage

Basic run:

npm run start -- --cucumberJson path/to/cucumber.json

Full run with optional context:

npm run start -- \
  --cucumberJson artifacts/cucumber-report.json \
  --console artifacts/console.log \
  --artifacts artifacts/ \
  --repo my-repo \
  --branch main \
  --commit abc123 \
  --workflowUrl "https://github.com/org/repo/actions/runs/123" \
  --env staging \
  --html artifacts/triage-report.html \
  --out artifacts/triage-eval.json

Output

  • category and confidence per failed scenario
  • suggested fixes
  • terminal summary/detail tables
  • Jira drafts (draft-only)
  • HTML report (--html)
  • eval JSON (--out)

Use In Other Projects

Recommended:

npm install --save-dev pw-cucumber-triage-agent

Add script in consumer package.json:

{
  "scripts": {
    "triage:e2e": "pw-triage --cucumberJson artifacts/cucumber-report.json --html artifacts/triage-report.html --out artifacts/triage-eval.json"
  }
}

Alternatives:

  • npx pw-cucumber-triage-agent --cucumberJson path/to/cucumber.json --html triage-report.html
  • npx pw-triage --cucumberJson path/to/cucumber.json --html triage-report.html
  • global install: npm install -g pw-cucumber-triage-agent

CI Snippets

GitHub Actions:

- name: Run failure triage
  if: always()
  run: |
    npx pw-triage \
      --cucumberJson artifacts/cucumber-report.json \
      --console artifacts/console.log \
      --artifacts artifacts/ \
      --repo "${{ github.repository }}" \
      --branch "${{ github.ref_name }}" \
      --commit "${{ github.sha }}" \
      --workflowUrl "https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}" \
      --html artifacts/triage-report.html \
      --out artifacts/triage-eval.json

Jenkins:

sh '''
  npx pw-triage \
    --cucumberJson artifacts/cucumber-report.json \
    --console artifacts/console.log \
    --artifacts artifacts/ \
    --repo "$JOB_NAME" \
    --branch "$BRANCH_NAME" \
    --commit "$GIT_COMMIT" \
    --workflowUrl "$BUILD_URL" \
    --html artifacts/triage-report.html \
    --out artifacts/triage-eval.json
'''

CLI Options

| Option | Description | |---|---| | --cucumberJson <path> | Path to Cucumber JSON report (required) | | --console <path> | Console log text file | | --artifacts <dir> | Artifacts folder (screenshots/traces/videos) | | --maxFailures <n> | Stop after N failures (default 500) | | --repo <name> | Repository name | | --workflowUrl <url> | CI run URL | | --commit <sha> | Commit SHA | | --branch <name> | Branch name | | --pr <num> | Pull request number | | --env <name> | Environment name | | --baseUrl <url> | Base URL | | --jiraProject <key> | Jira project key (default E2E) | | --jiraType <type> | Jira issue type (default Bug) | | --approve | Approval intent flag (still draft-only) | | --out <path> | Write eval JSON | | --html <path> | Write HTML report |

Troubleshooting

  • required option '--cucumberJson <path>' not specified
    Use: --cucumberJson artifacts/cucumber-report.json
  • Cucumber JSON not found
    Verify path and quote paths with spaces.
  • pw-triage: command not found
    Run with npx pw-triage ... or install as dev dependency first.
  • No failed scenarios found in cucumber JSON
    Confirm you passed the correct cucumber JSON output file.

Notes

  • CLI-first package (no programmatic import API yet)
  • Jira submission is draft-only in this version

License

Apache-2.0