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

@dbwebb/tui

v1.5.0

Published

A Node.js library for building interactive terminal UIs with a class-based command dispatcher.

Downloads

248

Readme

Terminal UI (TUI)

pipeline status npm version

A Node.js library for building interactive terminal UIs with a dynamic, class-based command dispatcher.

If you are a developer and want to understand or enhance the library itself, then read DEVELOPMENT.md.

Read on to learn how to install and use the library to create your own TUI.

Install

npm install @dbwebb/tui

Quick start

Create a tui.js in your project:

import { CommandRegistry, TuiShell, BaseCommand } from '@dbwebb/tui';

class ServerCommands extends BaseCommand {
  static descriptions = {
    status: 'status   Show server status',
    restart: 'restart  Restart the server',
  };

  async status() { return 'Server is running.'; }
  async restart() { return 'Server restarted.'; }
}

const registry = new CommandRegistry();
registry.register('server', new ServerCommands());

new TuiShell(registry, {
  welcomeMessage: "Welcome to My App!",
}).start();

Run it:

node tui.js

At the prompt:

> server status
> server restart
> help
> exit

Command groups

Each group is a class that extends BaseCommand. Methods become dispatchable actions.

import { BaseCommand } from '@dbwebb/tui';

export class MyCommands extends BaseCommand {
  static descriptions = {
    greet: 'greet <name>   Say hello',
  };

  async greet(name) {
    return `Hello, ${name}!`;
  }
}

Register it:

registry.register('my', new MyCommands());

Then call it:

> my greet world
Hello, world!

Rules for command methods:

  • Must be async
  • Return a string (or undefined for no output)
  • Names starting with _ are private and will never be dispatched

API

new CommandRegistry()

Holds registered command groups.

  • registry.register(name, instance) — register a command group
  • registry.dispatch(tokens) — resolve and call a command, returns { ok, message }; exceptions thrown by command methods are caught and returned as { ok: false, message }

new TuiShell(registry, options?)

Interactive readline REPL.

  • shell.start() — start the prompt loop
  • shell.ask(query) — from within a dispatched command, ask a follow-up question on the same interface (interactive mode only); see Multi-question dialogs with ask()
  • Built-in commands: help / h, exit / e, quit / q
  • Tab-completion for group names and actions

Options:

  • welcomeMessage (string) — optional message shown on startup in interactive mode (not shown in --file mode)
  • defaultGroup (string) — optional default command group; allows omitting the group name when typing commands

A standard hint line (Type "help" to see available commands or "exit" to quit.) is always printed on startup in interactive mode.

Example with defaultGroup:

const registry = new CommandRegistry();
registry.register('server', new ServerCommands());

new TuiShell(registry, { defaultGroup: 'server' }).start();

With defaultGroup set, status dispatches as server status. Typing the full server status still works. Tab completion also suggests the default group's actions alongside registered group names.

File mode

Run commands from a file instead of interactively:

node tui.js --file commands.txt

The file contains one command per line. Blank lines and lines starting with # are ignored.

# commands.txt
server status
server restart

The program executes each command in order and then exits.

Stdin pipe mode

Commands can also be piped via stdin — no --file flag needed:

echo "server status" | node tui.js
cat commands.txt | node tui.js

When stdin is not a TTY, TuiShell automatically reads from stdin using the same output format as --file mode: bold echo, plain output, blank line between blocks.

Multi-question dialogs with ask()

A dispatched command that needs to collect several answers in a row (e.g. a form) can call shell.ask(query) instead of pulling in a separate prompt library:

class LedgerCommands extends BaseCommand {
  constructor(shell) {
    super();
    this.shell = shell;
  }

  async entry() {
    const account = await this.shell.ask('Account: ');
    const amount = await this.shell.ask('Amount: ');
    return `Entry: ${account} ${amount}`;
  }
}

const shell = new TuiShell(registry);
registry.register('ledger', new LedgerCommands(shell));
shell.start();

ask() reuses the shell's own readline interface, so it doesn't race with the main prompt loop over stdin. It only works in interactive mode, after start() has been called — it rejects in --file or stdin-pipe mode.

BaseCommand

Base class for all command groups.

  • instance.publicMethods() — list of dispatchable method names
  • instance.help() — auto-generated help string from static descriptions