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

@theokit/agents-pty

v0.2.1

Published

The PTY interactive backend for @theokit/agents — a separate package so a web application does not compile a terminal it will never open.

Downloads

673

Readme

@theokit/agents-pty

The PTY interactive backend for @theokit/agents.

npm install @theokit/agents-pty
import { PtyInteractiveBackend } from '@theokit/agents-pty'

Why it is a separate install

@theokit/sdk-pty carries a native install step — it downloads a prebuild, or falls back to compiling C++. While it was a hard dependency of @theokit/agents, every application paid that cost, including the web apps that never open a terminal: installing @theokit/agents alone took 6.7 s with it and 1.4 s without, and in a scaffolded app that was most of the gap in time to first green run.

So it moved here. An application that drives a terminal declares this package; one that does not never compiles it. See usetheokit/theokit#460.

Migrating from @theokit/agents/pty

The subpath is gone. Install this package and change the import — the surface is identical, six symbols, unchanged:

-import { PtyInteractiveBackend } from '@theokit/agents/pty'
+import { PtyInteractiveBackend } from '@theokit/agents-pty'

Nothing else changes. This package re-exports @theokit/sdk-pty whole and adds no wrapper, which is also why you should not import @theokit/sdk-pty directly: an application takes its primitives from the @theokit/* layer, and this package is that layer for the PTY backend.

Licence

Apache-2.0