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

portslay

v1.0.0

Published

Find and kill processes on any port. Interactive, zero dependencies, cross-platform. npx portslay 3000

Readme

portslay

Find and kill the process on any port. Interactive, zero dependencies, works everywhere.

npm version npm downloads CI license

Error: listen EADDRINUSE: address already in use :::3000 — we've all been there.

npx portslay 3000

Done. ✔ killed node (pid 31196) on port 3000.

Interactive mode

Run it with no arguments to get a live picker of everything listening on your machine:

npx portslay
 portslay v1.0.0  ·  ↑↓ move · space select · enter kill · type to filter · esc quit

    PORT  PROCESS     PID  ADDRESS
 ○  3000  node      31196  0.0.0.0:3000
 ◉  5173  node      18244  127.0.0.1:5173
 ○  5433  postgres   7024  127.0.0.1:5433
 ◉  8080  java      22011  0.0.0.0:8080

Arrow keys to move, space to multi-select, enter to kill. Just start typing (node, 80, …) to filter.

Usage

npx portslay                # interactive picker
npx portslay 3000           # kill whatever listens on port 3000
npx portslay 3000 5173 8080 # several at once
npx portslay 3000-3010      # a whole range
npx portslay --list         # just show listening ports
npx portslay --list --json  # machine-readable

| Flag | Description | | --- | --- | | -l, --list | list listening TCP ports and exit | | -f, --force | SIGKILL immediately (default: SIGTERM, auto-escalates if the process ignores it) | | -j, --json | JSON output for scripts | | -v, --version | print version | | -h, --help | help |

Or install it for good: npm i -g portslay.

Why this one?

  • Zero dependencies. npx portslay cold-starts in a blink — nothing to download but one small file.
  • Interactive. See what is squatting on your ports before you kill it. Multi-select, filter, kill in bulk.
  • Graceful by default. Sends SIGTERM first so processes can clean up, escalates to SIGKILL only if ignored. --force skips the pleasantries.
  • Truly cross-platform. Native netstat/taskkill on Windows, lsof on macOS, lsof/ss on Linux. No compiled binaries, no WSL tricks.
  • Scriptable. --json and meaningful exit codes (0 freed, 1 something survived, 2 bad input).

Requirements

Node.js ≥ 18. That's it.

License

MIT © Cryptoteep