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

@crustum/dev-tui

v0.1.2

Published

OpenTUI dev process runner — tabbed TUI for running multiple commands simultaneously (dev-tui, port of multiplex)

Readme

@crustum/dev-tui

OpenTUI dev process runner — tabbed TUI for running multiple commands simultaneously with searchable, scrollable output. Port of @crustum/multiplex (Ink/React) to @opentui/core (imperative, Windows-friendly, mouse support), sharing the workspace/log-tui shell know-how.

When you exit, the interleaved output is flushed to your terminal scrollback so you don't lose your logs, up to the --stream-buffer-size limit.

Without an interactive terminal — piped, redirected, or in CI — it runs inline instead: same labelled, interleaved output, printed as it arrives, with no TUI. A terminal too small for the TUI, or one whose stdin won't enter raw mode, falls back the same way (says so on stderr) rather than crashing.

Install

npm install -g @crustum/dev-tui

Or run directly:

npx @crustum/dev-tui 'server,php bin/cake.php server' 'queue,php bin/cake.php queue worker'

Usage

dev-tui [options] <commands...>
# commands as label,command or label@color,command

| Option | Description | |---|---| | -s, --stream | Start in stream mode (P2 TUI; accepted today, runs inline until the TUI lands) | | --tabs | Start in tabs mode (default once the TUI lands) | | -i, --inline | Print output inline instead of rendering the TUI | | --json | Emit newline-delimited JSON events. Implies --inline | | --buffer-size <n> | Max lines per command buffer (default: 2000) | | --stream-buffer-size <n> | Max lines in the stream buffer (default: 10000) | | --timestamps | Display timestamps on each output line | | --no-restart | Disable auto-restart on crash | | --title <name> | Set the terminal tab title | | --dry-run | Print the resolved invocation without starting anything | | --fake | Run synthetic process output instead of spawning (for demos/tests) | | --theme <name> | Chrome theme: dark or light | | --runner <name> | Accepted for bin/cake dev compat (opentui); anything else errors |

Build / test

bun install
bun run build
bun run test      # node:test suites (tsx runner): proc/ + tui/
bun test          # everything bun finds, including the node:test suites above
bun run test:all  # all tests: tsx suites, then TestRenderer integration in src/ui/

Node fallback: node --test --import tsx works for the test script (needs Node >= 26.4).