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

@dagger.io/mocha

v0.1.0

Published

MochaJS OpenTelemetry auto instrumentation

Readme

@dagger.io/mocha

Auto-instrumentation for Mocha tests with OpenTelemetry. It creates spans for:

  • each suite that runs
  • each test that runs (including pass/fail/pending status and duration)

Telemetry bootstrap, exporter, and context management are handled by @dagger.io/telemetry. This package only hooks Mocha and emits tracing data.

Requirements

  • Node.js 20+
  • Mocha 9–11 (peer dependency)

Install

  • Using npm:
    • npm install --save-dev @dagger.io/mocha
  • Using yarn:
    • yarn add -D @dagger.io/mocha
  • Using pnpm:
    • pnpm add -D @dagger.io/mocha

The telemetry client (@dagger.io/telemetry) is a direct dependency and will be installed automatically.

Usage

This library is designed to work by preloading a register file via NODE_OPTIONS.

  • CommonJS (Node’s --require):
    • NODE_OPTIONS="$NODE_OPTIONS --require @dagger.io/mocha/register" npx mocha
  • ESM (Node’s --import):
    • NODE_OPTIONS="$NODE_OPTIONS --import @dagger.io/mocha/register" npx mocha

You can also add it to your package.json test script:

  • CommonJS:
    • "test": "NODE_OPTIONS='--require @dagger.io/mocha/register' mocha"
  • ESM:
    • "test": "NODE_OPTIONS='--import @dagger.io/mocha/register' mocha"

This will:

  • start the telemetry SDK before Mocha runs
  • create spans for suites/tests as Mocha emits events
  • attempt to gracefully shutdown and flush telemetry when the run ends

What gets instrumented

Suite and test are instrumented.

  • Suite span: mocha.suite
    • Status is set to ERROR if a test or a children suite is failed.
  • Test span: mocha.test
    • Status is set to:
      • OK for passed tests
      • ERROR for failed tests (with recorded exception)

All spans are emitted under tracer name dagger.io/mocha.

Developer guide

  1. Build:
  • bun install
  • bun run build
  1. Run the sample test:
  • cd tests/hello_world/register_esm
  • npm install (installs local @dagger.io/mocha via file dependency)
  • Run the script or mocha inside a dagger session:
    • NODE_OPTIONS="$NODE_OPTIONS --import @dagger.io/mocha/register" dagger run npx mocha

You should see your spans appears in the TUI and on dagger cloud.

License

Apache-2.0