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/kitty

v0.11.0

Published

Kitty backend for termless — uses kitty's VT parser via subprocess bridge (GPL-3.0 dependency, not distributed)

Readme

@termless/kitty

Kitty backend for termless — uses kitty's actual VT parser via a Python subprocess bridge.

Feature support: Kitty results on terminfo.dev combine application and parser-backend results; no separate page isolates this library.

Install from npm; a git install resolves the TypeScript source and runs only under Bun.

How it works

Unlike other native backends that compile a Rust crate into a .node binary, the kitty backend runs kitty's own Python-embedded C code via kitty +runpy. This is necessary because kitty's VT parser is deeply coupled to CPython (all data structures use PyObject_HEAD, callbacks use the Python C API, etc.).

The architecture:

  1. build/bridge.py — A Python script that creates a headless kitty Screen, accepts JSON commands via stdin, and returns terminal state snapshots via stdout
  2. src/backend.ts — TypeScript wrapper that accumulates commands and replays them in a kitty +runpy subprocess when a query is needed

Each mutation (feed, resize, reset) is logged. When you query the terminal state (getCell, getCursor, etc.), the entire command log is replayed in a fresh subprocess and the resulting snapshot is cached until the next mutation.

The paste-encoding extension observes Kitty's terminal-state Screen.paste bytes, including native bracketed framing, rather than the application's sanitizing Window.paste action.

The existing osc-metadata getter getUnhandledSequences() copies native parser rejection codes in feed order. It uses Kitty's diagnostic parser variant and recognizes only the pinned 0.49.2 error wording; unmatched messages or other versions decide nothing. OSC codes retain their number; CSI diagnostics retain only reported modifiers and final byte, without reconstructing omitted parameters. These rejections are separate from host-delivery callbacks.

The osc-metadata getter getCwd() reads only native OSC 7 state: the last completed BEL- or ST-terminated payload wins, and split or incomplete sequences retain the previous value. Payloads stay literal, without URI, percent or backslash decoding; invalid UTF-8 becomes U+FFFD. Initial state, empty OSC 7, reset and re-init return null. Kitty 0.49.2 left cwd unchanged for OSC 633 P;Cwd= when measured alongside a working OSC 7 control; native stderr reported Ignoring OSC 633, use by Windows Terminal for VSCode actions.

License

This package's source code (bridge script + TypeScript wrapper) is MIT licensed.

At runtime it invokes the separately installed kitty binary, which is GPL-3.0 licensed. A build-time C emitter measures pinned Kitty headers; its source and generated JSON metadata are shipped, but its executable is not.

Prerequisites

Install kitty:

brew install --cask kitty   # macOS
# or visit https://sw.kovidgoyal.net/kitty

For a source checkout, install Nix, then verify the committed native layout metadata and Kitty installation:

cd packages/kitty
bash build/build.sh

The script rebuilds .#kitty-native-mode-layout and compares its JSON layout and receipt before checking Kitty. Native reverseVideo and syncOutput reads require the attested runtime; see backend limits.

Usage

import { createKittyBackend } from "@termless/kitty"
import { createTerminal } from "@termless/core"

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

Performance

  • ~35ms per mutation (subprocess startup + replay + snapshot)
  • <1ms per query (served from cached snapshot)
  • Suitable for testing; not for real-time use