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

@unotest/viewer

v0.52.1

Published

Localhost HTTP+WS viewer for unotest. Target-agnostic host: runner packages (@unotest/web, @unotest/mobile, …) are à-la-carte plugins auto-detected at boot and selectable via the TEST TARGET switcher. NestJS server + React+MobX frontend. Reads run-artifac

Readme

@unotest/viewer

Local browser UI for @unotest/web test runs.

Installed automatically as part of @unotest/web — no manual setup needed.

Usage

npx @unotest/web viewer

Opens a local IDE-style UI in your default browser: a scenario / collection / run-history tree, run-from-UI with live results over WebSocket, a foldable block view of each scenario (one section per step(...) block) with per-step status, a step debugger (breakpoints + live DOM inspection), screenshots and failure artifacts, and a docked terminal.

A scenario file with several test_* functions is a node in the tree, with one row per test. Each test has its own run, status and history. The file's run lists its tests, and Run again on a test runs that test only. The file's dot is red when a test failed. It is grey (skipped) only when every test skipped, and violet (failed on purpose) only when every test that ran was expected to fail; otherwise it is green. Home and collection summaries count tests, not files.

Set UNOTEST_VIEWER_NO_OPEN=1 to start the server without auto-opening the browser.

Set UNOTEST_VIEWER_TERMINAL=off on a host that cannot give the docked terminal a PTY (the native node-pty addon is not installed there). The viewer then has no terminal at all — no panel, no button, no terminal socket — for every session. Unset, the terminal is on, and a machine missing the addon says so when the panel starts. A box sets it for its viewers.

Ecosystem

| Package | Role | |---|---| | @unotest/web | CLI / MCP server / runner | | @unotest/viewer | this package — local results browser | | @unotest/protocol | shared types | | @unotest/dsl | scenario parser + validator engine |