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

termless

v0.9.1

Published

Headless terminals: test, record, replay, and run sessions.

Downloads

223

Readme

termless

Headless terminals: test, record, replay, and run sessions.

termless is the umbrella package for the termless stack — an effect-style umbrella with arity-scoped subpaths, not a single flat namespace. Backend arity is visible in the import path: ., ./fmt, ./rec, and ./contract have no engine. ./backends is the only home of plurality.

If you never import termless/backends, you never have more than one engine.

The engine itself is vterm.js — a pure-TypeScript, zero-dependency terminal emulator targeting full VT/ECMA-48/xterm coverage, graded at arm's length by its own conformance rig.

Subpaths

| Subpath | Contains | Engine? | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | :-----: | | termless | createTerminal + the common path: screenshots, key mapping, diffing | no | | termless/contract | The Terminal read contract, TerminalBackend, region view types | no | | termless/fmt | The .tty / .ttyz recording format — types + read/write surface | no | | termless/rec | Recording, its codecs, journal-replay, and replay/view | no | | termless/backends | The backend registry — backend(), backends(), isReady, buildBackend() | yes | | termless/test | Reserved. Vitest matchers, fixtures, and snapshot assertions. Ships from @termless/test today. | no | | termless/session | Reserved. The sealed live-session API (session.readable/writable/recording). Unbuilt — see docs/reference/formats/tty.md. | no |

Quick start

import { createTerminal } from "termless"
import { backend } from "termless/backends"

const term = createTerminal({ backend: await backend("vterm"), cols: 80, rows: 24 })
term.feed("hello")
term.screen.getText() // "hello"
await term.close()

Working directly against a specific engine's own package (@termless/vterm, @termless/xtermjs, …) skips termless/backends entirely — that is the single-engine path, and it never imports plurality:

import { createTerminal } from "termless"
import { createVtermBackend } from "@termless/vterm"

const term = createTerminal({ backend: createVtermBackend(), cols: 80, rows: 24 })

Why an umbrella

Scoped @termless/* packages (@termless/core, @termless/vterm, @termless/xtermjs, …) remain the satellite packages — native/WASM backends stay scoped so their install weight (Rust builds, WASM blobs) is opt-in, not bundled into every install. termless is the single-semver front door: one version, one changelog, the subpaths above as its whole public surface. Native backends are the deliberate exception to "single semver" — their install cost is why they stay out.

Learn more

  • termless.dev — full documentation, guides, and the cross-terminal conformance corpus.
  • vterm.js — the engine: coverage, differential tests against the classic VT corpus, and the deliberate-divergence ledger.