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

@robit-one/reporter

v0.1.23

Published

Test reporter adapters for [robit.one](https://robit.one) — automatically post test results to your Robit dashboard from vitest, Playwright, or Deno.

Readme

@robit-one/reporter

Test reporter adapters for robit.one — automatically post test results to your Robit dashboard from vitest, Playwright, or Deno.

Part of the robit.one monorepo.

Installation

npm install @robit-one/reporter

Usage

Vitest

In vitest.config.ts:

import { defineConfig } from 'vitest/config'
import { RobitReporter } from '@robit-one/reporter/vitest'

export default defineConfig({
  test: {
    reporters: [
      'default',
      new RobitReporter({
        token: process.env.ROBIT_TOKEN,
        suite: 'unit',
      }),
    ],
  },
})

Playwright

In playwright.config.ts:

import { defineConfig } from '@playwright/test'

export default defineConfig({
  reporter: [
    ['list'],
    ['@robit-one/reporter/playwright', {
      token: process.env.ROBIT_TOKEN,
      suite: 'e2e',
    }],
  ],
})

Deno

The Deno integration is a runner script that wraps deno test, captures results, and posts them to Robit. Install from JSR and invoke it in place of deno test:

deno run -A jsr:@robit-one/reporter/run --suite=unit -- src/

Pass the token inline or via environment variable:

# inline flag
deno run -A jsr:@robit-one/reporter/run --suite=unit --token=rbt_xxx -- src/

# or via env var (useful in CI)
ROBIT_TOKEN=rbt_xxx deno run -A jsr:@robit-one/reporter/run --suite=unit -- src/

The runner automatically collects coverage via deno coverage --lcov and posts it alongside your results. All arguments after -- are forwarded to deno test.

Configuration

| Option | Type | Default | Description | |--------|------|---------|-------------| | token | string | required | Your Robit project token | | suite | string | required | Test suite name (e.g. 'unit', 'e2e', 'integration') | | runner | 'vitest' \| 'playwright' \| 'deno' \| 'unknown' | auto-set by adapter | Override the runner type sent to Robit | | environment | string | auto-detected | Environment name (ci, staging, etc.) | | branch | string | auto-detected | Git branch name | | baseUrl | string | https://app.robit.one | Custom Robit instance URL | | enabled | boolean | true | Set to false to disable reporting without removing config | | meta | Record<string, unknown> | undefined | Custom metadata attached to the run | | timeoutMs | number | 10000 | Fetch timeout in milliseconds |

Environment detection

Branch, environment, and commit info are auto-detected from CI environment variables with git fallbacks.

Branch is read from (in order): config.branchGITHUB_REF_NAMEBITBUCKET_BRANCHCI_COMMIT_BRANCHgit rev-parse --abbrev-ref HEAD

Environment is read from: config.environmentNODE_ENVAPP_ENVENVIRONMENT

Commit SHA is read from: GITHUB_SHABITBUCKET_COMMITCI_COMMIT_SHAgit rev-parse HEAD

Supported CI providers: GitHub Actions, Bitbucket Pipelines, GitLab CI.