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

@bobfromarcher/portkill

v1.0.1

Published

Find and kill whatever is holding a TCP port - cross-platform (Windows/macOS/Linux). Zero dependencies.

Readme

portkill

npm CI license zero deps

Finds whatever process is holding a TCP port and kills it. Works on Windows, macOS and Linux. It is the quick fix for Error: listen EADDRINUSE: address already in use :::3000. No dependencies, no AI.

Install

npm install -g @bobfromarcher/portkill
# or once:
npx @bobfromarcher/portkill 3000

Usage

portkill <port> [options]
portkill --list

| Option | Description | | --- | --- | | --list, -l | List every listening port and its owning process | | --force, -f | Kill without the confirmation prompt | | --json | Output JSON instead of killing | | -h, --help | Show help | | -v, --version | Show version |

Examples

portkill 3000           # find the process on :3000 and confirm before killing
portkill 8080 --force   # kill it immediately, no prompt
portkill --list         # everything that is listening, sorted by port
portkill 5432 --json    # report the owner, do not kill

How it works

portkill shells out to the tools your OS already ships: netstat -ano and tasklist on Windows, lsof and ps on macOS and Linux. It parses their output and maps the port to a process. The parsing is pure and unit tested against captured fixtures from each platform, so behavior is the same everywhere. No native modules, nothing to compile.

Development

git clone https://github.com/bobfromarcher/portkill
cd portkill
node test/test.js

CI runs the suite on Node 18, 20 and 22 across Linux, macOS and Windows.

License

MIT, bobfromarcher.