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

@10xdevs/term

v0.1.0

Published

Full local terminal in the browser, connected to your machine's shell via WebSocket and [node-pty](https://github.com/microsoft/node-pty).

Downloads

44

Readme

Local Shell Example

Full local terminal in the browser, connected to your machine's shell via WebSocket and node-pty.

Run as a package

After publishing, run the optimized production server directly with Bun:

bunx @10xdevs/term
bunx @10xdevs/term --port 8080

The default port is 4242. The package builds once on first run when no production build is present, then starts the small custom HTTP + WebSocket server (not the Next development server).

Setup

From the monorepo root:

pnpm install
zig build
pnpm --filter local dev

Opens at local-example.wterm.localhost via portless.

How It Works

  • server.ts starts an HTTP + WebSocket server alongside Next.js
  • On WebSocket connection, a PTY process is spawned with your default shell
  • The browser sends keystrokes over WebSocket; the server relays PTY output back
  • Terminal resizing is forwarded to the PTY via a custom escape sequence

Key Files

| File | Description | |---|---| | server.ts | Custom server with WebSocket ↔ PTY bridge | | app/page.tsx | Terminal page with auto-resize and WebSocket connection | | app/layout.tsx | Root layout with metadata |