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

@plmbr/webterm

v1.1.0

Published

webterm is a web terminal backed by node-pty server

Readme

webterm

A Web Terminal based on xterm.js and node-pty.

The frontend is built with React + TypeScript + Vite, and the backend is a TypeScript Node.js server using Express and ws for the PTY websocket.

Project structure

.
├── index.html              # Vite entry HTML
├── src/                    # React + TypeScript frontend
│   ├── main.tsx
│   ├── App.tsx
│   ├── Terminal.tsx
│   └── styles.css
├── server/                 # TypeScript backend (Express + ws + node-pty)
│   └── server.ts
├── vite.config.ts          # Vite config (proxies /pty websocket to backend in dev)
├── tsconfig*.json          # TypeScript configs (app / node / server)
└── package.json

Development

npm install
npm run dev

This launches two processes in parallel:

  • the backend (tsx watch server/server.ts --port 3001)
  • the Vite dev server on http://localhost:5173

Vite proxies the /pty websocket (and /health) through to the backend, so you can develop the frontend with hot module reloading while the PTY server keeps running.

Production build

npm run build
npm start
  • npm run build builds the React app into dist/client/ and compiles the TypeScript server into dist/server/.
  • npm start runs the compiled server, which serves the built client and exposes the PTY websocket at /pty.

The server listens on port 3000 by default. Override with --port:

npm start -- --port 4000
# or
node dist/server/server.js --port 4000

Running via npx

After publishing, the webterm bin points at the compiled server:

npx @plmbr/webterm --port 4000