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

@naouts/portkill

v1.0.0

Published

Kill the process running on a given port — works on Windows, Linux, and macOS

Downloads

31

Readme

portkill

npm version npm downloads License: MIT Node.js Platform

Kill the process running on a given port — instantly, from any terminal.


Why

You're running a dev server, you close it wrong, and now port 3000 is stuck.
You paste into Google, copy-paste some lsof command, grep the PID, then kill it.

portkill does all of that in one command.


Usage

No install needed:

npx @naouts/portkill 3000

Or install globally:

npm install -g @naouts/portkill
portkill 3000

Output

→ Scanning port 3000...
  Found: node (PID 18423)
✔ Killed node (PID 18423)

Options

| Flag | Description | |------|-------------| | <port> | Port number to kill (1–65535) | | -h, --help | Show help | | -v, --version | Print version |


Platform support

| OS | Method used | |----|-------------| | Windows | netstat -ano + tasklist + taskkill /F | | macOS | lsof -ti + ps + kill -9 | | Linux | lsof -ti + ps + kill -9 |


Examples

# Kill whatever is on port 8080
npx @naouts/portkill 8080

# Kill a stuck Vite dev server
npx @naouts/portkill 5173

# Kill a Next.js server
npx @naouts/portkill 3000

If multiple processes share the port, all of them are killed.


Install globally

npm install -g @naouts/portkill

Then use anywhere:

portkill 3000

Permissions

On Linux/macOS, killing processes owned by another user requires sudo:

sudo portkill 80

On Windows, run your terminal as Administrator if you get an access denied error.


Requirements

  • Node.js 14 or later
  • No external dependencies — only Node.js built-ins

License

MIT © naouts