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

@juliendu11/japa-ui-reporter

v0.0.9

Published

[![NPM](https://nodei.co/npm/@juliendu11/japa-ui-reporter.png?compact=true)](https://npmjs.org/package/@juliendu11/japa-ui-reporter)

Downloads

899

Readme

NPM

Japa UI reporter

Frustrated by the various default reporting tools, I created my own.

This one allows you to open a dashboard in your browser with live reports of your tests, similar to vitest --ui

When the tests start, a page will open in your browser for live results. Then a report generated in end in ./test_results in your project. It's same page as the live one but in static

Installation

npm install -D @juliendu11/japa-ui-reporter

Usage

:warning: Note: I use it with Adonis JS; it's designed to be used with version 6.

// tests/bootstrap.ts
import UIReporter from '@juliendu11/japa-ui-reporter'

import type {Config} from '@japa/runner/types'

export const reporters: Config['reporters'] = {
    activated: ['ui'],
    list: [UIReporter.ui()],
}

Options

UIReporter.ui({
    ui: { // Optional, default: {port: 3000}
        port: number
    },
    reporter: { // Optional, default: {port: 9999}
        port: number
    },
    killPortsInUse: true,  // Optional, default: true
    livePreview: false,  // Optional, default: true
    ...BaseReporterOptions // Optional
})

How it works

The reporter starts a server that hosts the dashboard and listens for test events from TCP. When a test event occurs, it sends the data to the dashboard via WebSocket, which updates the user interface accordingly.

Then, at the end of the test run, the server creates a static HTML file, similar to the live version, containing the test results. You will find the report in ./test_results at the root of your project.

More information here

Problem

Not receiving END instructions

I had this problem in my Adonis 6 project before even installing this reporter (the same issue occurred with Spec), even though it worked fine initially.

I found a solution: in the runnerHooks, within the teardown hook, you need to explicitly tell the runner to call end(). This fixes the problem for all reporters.

// tests/bootstrap.ts
export const runnerHooks: Required<Pick<Config, 'setup' | 'teardown'>> = {
    setup: [],
    teardown: [
        (e) => {  // FIX
            e.end()
        },
    ],
}