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

eaddrinuse

v1.1.0

Published

Kill whatever is squatting on your dev port. Zero dependencies.

Readme

eaddrinuse

Error: listen EADDRINUSE: address already in use :::3000

A phantom process from a project you abandoned in March is still holding the socket. It has no window. It has no tab. It has only the port.

npx eaddrinuse

Port's yours again.

Install

Nothing to install. Run it:

npx eaddrinuse

Or keep it around:

npm i -g eaddrinuse

Usage

eaddrinuse              # kill whatever holds 3000
eaddrinuse 5173         # kill that port instead
eaddrinuse 3000 8080    # kill several
eaddrinuse --list       # show the squatters, kill nothing
eaddrinuse --all        # sweep 3000, 3001, 4200, 5000, 5173, 8000, 8080

Options

| Flag | What it does | | --- | --- | | -l, --list | Report only. Kills nothing. | | -a, --all | Check the usual dev ports. | | -f, --force | Skip SIGTERM, go straight to SIGKILL. | | -q, --quiet | Print only failures. Good for scripts. | | -v, --version | Print version. | | -h, --help | Usage. |

Exit code is 0 when everything cleared and 1 when something survived, so it composes:

eaddrinuse -q && npm run dev

How it behaves

SIGTERM first, so the process gets a chance to clean up its own sockets and temp files. If it's still alive 220ms later, SIGKILL. Pass --force to skip straight to the second step.

On Windows it uses taskkill /T to take the process tree, because your dev server is usually a child of something else.

Ports match exactly. Asking for 3000 will not touch 30001.

It refuses to signal PID 0, PID 1, or itself.

Platform support

| Platform | Lookup | Kill | | --- | --- | --- | | macOS | lsof | SIGTERM then SIGKILL | | Linux | lsof, falls back to ss, then fuser | SIGTERM then SIGKILL | | Windows | netstat -ano | taskkill /PID /T |

Requires Node 14 or newer.

Dependencies

None. Zero. The whole thing is one file and the Node standard library.

Every package you install to solve a ten second problem is a package you now have to trust forever. This one reads netstat and calls process.kill. You can read all of it in a few minutes, and you should.

Colors

Respects NO_COLOR. Also goes plain when stdout is not a TTY, so piped output stays clean.

License

MIT


eaddrinuse.fun · t.me/eaddrinuse · @eaddrinuse_fun