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

@ugurkellecioglu/fkp

v0.1.1

Published

Fast kill port — kill processes on one or more ports, cross-platform. Optional --tcp / --udp filters.

Readme

fkp — fast kill port

Kill processes listening on one or more ports. Cross-platform (macOS, Linux, Windows). Zero dependencies.

npx @ugurkellecioglu/fkp 3000
npx @ugurkellecioglu/fkp 3000 8080 5173
npx @ugurkellecioglu/fkp --tcp 3000    # leave clients alone, only kill the listener
npx @ugurkellecioglu/fkp --udp 53      # kill UDP bindings (DNS, game servers, etc.)

Why another kill-port tool?

Compared to the two popular alternatives:

  • kp runs lsof -i:PORT | xargs killall, which matches by process name. kp 3000 will kill every node (or python, etc.) process on your machine, not just the one on port 3000. Single port only.
  • kill-port targets PIDs correctly, but as an existence check it runs lsof -i -P — which enumerates every network socket on the system. On a busy dev box that alone takes multiple seconds before it even starts killing.

fkp does neither. It runs one targeted lsof -ti:<ports> and one kill -9 with all PIDs, no shell, no deps.

Flags

| Flag | Behavior | |---|---| | (none) | Fastest. Kills every process with a socket on the port(s) — listeners and any connected clients. | | --tcp | Only kills TCP listeners. Safe mode — won't touch processes (e.g. Chrome, curl, psql) that happen to have an open connection to the port. | | --udp | Only kills UDP sockets bound to the port. | | --tcp --udp | Union of both filtered queries. |

The default prioritizes speed. Pass --tcp when you want "kill the server, leave my client open" semantics.

Benchmark

macOS, 5 runs, wall-clock including Node startup:

| Scenario | fkp (default) | fkp --tcp | kp | kill-port | |---|---|---|---|---| | 1 port | 263 ms | 263 ms | 288 ms | 6495 ms | | 3 ports | 266 ms | 264 ms | ~480 ms (N invocations) | ~5700 ms |

fkp stays flat across port count — one lsof and one kill call regardless of how many ports. kp grows linearly (one Node startup per port). kill-port is bottlenecked on the system-wide lsof -i -P scan.

How it works

  • macOS / Linux: lsof -ti:3000,8080,5173kill -9 <pids>. With --tcp: lsof -ti tcp:<ports> -sTCP:LISTEN. With --udp: lsof -ti udp:<ports>.
  • Windows: one netstat -ano parse → taskkill /F /PID x /PID y /PID z. Flags filter the protocol/state in the parser.
  • Uses execFile (no shell) for speed and safety.
  • Exits 0 whether or not a process was found.

Install

npm i -g @ugurkellecioglu/fkp
# then
fkp 3000

# or one-off
npx @ugurkellecioglu/fkp 3000

License

MIT