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

terminal-shell

v0.1.1

Published

Dependency-free browser terminal and worker protocol for line-oriented WASM engines

Readme

terminal-shell

CI npm version license

A small, dependency-free browser terminal for colossal-cave-wasm, oregon-fortran-wasm, and Basicade.

It provides the terminal UI and the protocol used to connect it to a game or interpreter. Browser-specific behavior lives here so the launchers don't have to duplicate it.

Install

npm install terminal-shell

Usage

Create a shell by providing the elements it controls and callbacks for the engine:

import { createTerminalShell } from "terminal-shell";

const shell = createTerminalShell({
  screen,
  output,
  inputLine,
  cursor,
  field,
  container,
  insetTarget,

  onLine(line) {
    // Pass the line to the engine.
  },

  onFirstOutput() {
    // Engine produced its first output.
  },
});

The shell handles input, IME composition, command echoing, scrolling, focus, and the mobile keyboard.

The main methods are:

  • appendOutput(text)
  • beginInput()
  • reset(banner)
  • focusInput({ force })
  • isWaitingForInput()

See src/index.js for the full API and available options.

Runner protocol

terminal-shell/protocol defines the messages exchanged between the page and engine worker:

  • INIT — load the engine
  • START — start a program
  • READY, STARTED, STDOUT, REQUEST_INPUT, ERROR, EXIT

terminal-shell/runner-worker provides the worker for Emscripten-built engines. Interpreters can implement their own worker while using the same protocol.

The protocol also provides the shared input buffer used to pass one submitted line to the engine.

Demo

demo/ is a minimal integration using an echo engine:

npm run dev

Run npm run dev, then open the printed URL (it redirects straight to the demo) and try typing a command. The server runs at the repository root because the demo imports from ../src/.

Development

npm run all

This runs formatting, linting, type checking, and tests.