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

@flakemetry/sdk

v0.2.2

Published

OpenTelemetry test instrumentation and ingest client

Readme

@flakemetry/sdk

OpenTelemetry test instrumentation for Flakemetry. Records a test run, computes stable test identities, and exports the run as real OTLP spans.

Most users do not depend on this directly — the @flakemetry/playwright-reporter builds on it. Use this package to write a reporter for another test runner.

Install

pnpm add -D @flakemetry/sdk

Usage

import { exportRunOverOtlp, TestRunRecorder } from '@flakemetry/sdk'

const recorder = new TestRunRecorder({
  project: 'acme/web',
  commitSha: process.env.GITHUB_SHA!,
  branch: 'main',
  ciProvider: 'github_actions',
  trigger: 'push',
})

recorder.startRun(new Date())
recorder.record({
  filePath: 'e2e/login.spec.ts',
  suite: 'auth',
  title: 'logs in',
  status: 'fail',
  attempt: 1,
  startedAt: new Date(),
  durationMs: 1800,
  error: { message: 'Timeout 30000ms exceeded' },
})
recorder.finishRun('failed', new Date())

await exportRunOverOtlp(recorder, 'ci-run-42', {
  endpoint: process.env.FLAKEMETRY_ENDPOINT!,
  token: process.env.FLAKEMETRY_TOKEN!,
})

The whole run ships as one OTLP/HTTP request (test.run parent span with a test.case child per attempt) to POST /v1/traces.

What it gives you

  • Span builders following the test semantic conventionstest.runtest.case, retry linkage, exception events, artifact references.
  • Stable test identitycomputeFingerprint normalizes paths and hashes parameters so a test keeps its history across refactors.
  • Fail-open deliveryIngestClient never throws into your test process; failed runs can buffer to disk and replay on the next run via flushBuffered().
  • SamplingshouldDeliverRun keeps every run containing a failure or flake and samples the rest.

License

MIT © Andrii Kohut