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

@orangebeard-io/codeceptjs-listener

v1.0.1

Published

A CodeceptJS Mocha reporter for Orangebeard.io

Readme

Installation

Install the npm package

npm install @orangebeard-io/codeceptjs-listener --save-dev

Configuration

1. Orangebeard connection

Create orangebeard.json in your project root (or any parent directory):

{
  "endpoint": "https://your-instance.orangebeard.app",
  "token": "your-api-token",
  "project": "your-project-name",
  "testset": "Your Test Set Name",
  "description": "CodeceptJS test run",
  "attributes": [
    {
      "key": "env",
      "value": "ci"
    }
  ]
}

You can also provide connection values with environment variables:

  • ORANGEBEARD_ENDPOINT
  • ORANGEBEARD_TOKEN
  • ORANGEBEARD_PROJECT
  • ORANGEBEARD_TESTSET

2. Configure the reporter in CodeceptJS

Set the Mocha reporter in codecept.conf.js or codecept.conf.ts:

exports.config = {
  // ...your existing config...
  mocha: {
    reporter: '@orangebeard-io/codeceptjs-listener',
    reporterOptions: {
      // Optional: override orangebeard.json settings
      // endpoint: 'https://...',
      // token: '...',
      // project: '...',
      // testset: '...',
    },
  },
};

3. Screenshots (optional)

The reporter attaches failure screenshots produced by CodeceptJS screenshotOnFail.

exports.config = {
  // ...
  plugins: {
    screenshotOnFail: {
      enabled: true,
    },
  },
};

Running

Run tests as usual:

npx codeceptjs run

Results are streamed to Orangebeard in real time.

What gets reported

The reporter will:

  • Map CodeceptJS Features to Orangebeard suites.
  • Map Scenarios to Orangebeard tests.
  • Report I.* actions as real-time steps.
  • Group hook activity under Before / After parent steps.
  • Group I.say(...) sections as parent comment steps.
  • Parse tags into Orangebeard test attributes.
  • Attach failure screenshots to the related test.
  • Send error details and stack traces as logs.
  • Log I.executeScript(...) source as markdown step logs.
  • For HTTP request steps (sendGetRequest, sendPostRequest, etc.), keep only URL in step titles and log payload/headers as markdown.

License

Apache-2.0 — see LICENSE.