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

onepipeline-ui

v0.23.2

Published

The DAG Observatory: the browser view of onepipeline runs, built and ready to serve.

Readme

onepipeline-ui

The DAG Observatory: the browser view of onepipeline runs. This package carries the built frontend — a static bundle under dist/ — and no binary. The read API it talks to ships separately as onepipeline-api-cli.

npm install onepipeline-ui

The read API of the same release already carries this bundle: onepipeline-api serve --runs-root ./runs --ui serves it at / beside the API, with nothing to install beyond the command. This package is the bundle on its own, for serving it from somewhere else — any static file server with the read API behind the same origin at /api and /healthz, or the API itself pointed at it:

npx onepipeline-api-cli serve --runs-root ./runs   # the API, on 127.0.0.1:8765
npx serve node_modules/onepipeline-ui/dist          # the view, from a static server
npx onepipeline-api-cli serve --runs-root ./runs --ui --ui-dist node_modules/onepipeline-ui/dist

The app declares no schema, event name, or API path of its own: every payload it reads is validated against the contract in docs/contract.md.