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

@noor.ahamed/kill-port

v1.0.3

Published

Cross-platform CLI to kill process(es) listening on a TCP port

Readme

kill-port

Cross-platform CLI to kill process(es) listening on a TCP port. Works on Windows, macOS, and Linux.

Install

npm i -g "@noor.ahamed/kill-port"

Usage

kill-port <port> [options]

Examples

kill-port --list               # List all TCP listeners
kill-port --list --filter node # List only rows whose name/port/PID matches "node"
kill-port --list --filter "/3\d{3}/"  # List only rows matching regex (e.g. ports 3xxx)
kill-port 3000                 # Kill process on port 3000 (with confirm)
kill-port 3000 8080 443        # Kill processes on multiple ports
kill-port 3000 -f              # Kill without confirmation
kill-port 3000 --dry-run       # Show what would be killed
kill-port 3000 --json          # Machine-readable output
kill-port 3000 --timeout 5000  # Wait up to 5s for port to free

Options

| Option | Short | Description | | -------------------- | ----- | ----------------------------------------------------------------------- | | --list | -l | List all TCP listeners (no port or kill) | | --filter <pattern> | | With --list: show only rows matching pattern (substring or /regex/) | | --force | -f | Skip confirmation prompt | | --dry-run | -d | Show what would be killed without killing | | --verbose | -v | Print debug info | | --json | | Output machine-readable JSON | | --timeout <ms> | | Wait up to this many ms for port to free after kill (default: 3000) |

Exit codes

  • 0 – Success (port was free, or processes were killed)
  • 1 – Invalid port, or one or more processes could not be killed

Programmatic use

const { findListeners, killListeners, isPortFree } = require("@noor.ahamed/kill-port");

const listeners = await findListeners(3000);
if (listeners.length > 0) {
  const result = await killListeners(listeners, { port: 3000 });
  console.log("Killed:", result.killed, "Errors:", result.errors);
}
const free = await isPortFree(3000, 5000);

Troubleshooting

lsof not found (macOS / Linux)

On minimal Linux images lsof may not be installed. Install it (e.g. apt install lsof or yum install lsof). The tool will try ss and then netstat as fallbacks.

Permission denied

Listing or killing processes on certain ports may require elevated privileges. On Windows, run the terminal as Administrator if needed. On macOS/Linux, use sudo if necessary (e.g. sudo kill-port 80).

Port already in use after kill

Use --timeout to wait longer for the port to be released (e.g. kill-port 3000 --timeout 10000).

Uninstall

npm uninstall -g @noor.ahamed/kill-port

Limitations and safety

  • Do not kill system or protected processes without understanding the impact. Some PIDs may require an elevated shell (Administrator / root).
  • On Windows, killing a process tree (/T) may close child processes.
  • Output parsing depends on localized commands (netstat, lsof, ss); non-English locales may need testing.