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

portwiz

v1.0.0

Published

Fix port conflicts instantly and run your dev server without interruptions

Downloads

91

Readme

🚀 portwiz

Fix port conflicts instantly and run your dev server without interruptions.

npx portwiz 3000

😩 The Problem

Every developer has seen this:

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

Then you:

  • Search for the process using the port
  • Run lsof / netstat
  • Kill processes manually
  • Repeat again tomorrow 😑

👉 It breaks your flow.


⚡ The Solution

portwiz handles everything in one command:

npx portwiz 3000
  • Detects what’s using the port
  • Shows the process clearly
  • Frees it instantly

No guesswork. No manual steps.


📦 Installation

# Run instantly (recommended)
npx portwiz 3000

# Or install globally
npm install -g portwiz

Requirements: Node.js 18+


🧪 Usage


🔧 Free a port

portwiz 3000
ℹ Checking port 3000...
⚠ Port 3000 is in use

  PID:     1234
  Process: node

? Kill this process to free port 3000? (y/N) y
✔ Port 3000 is now free

⚡ Force mode

Skip confirmation:

portwiz 3000 --force

🔀 Smart switch

Find the next available port instead of killing:

portwiz 3000 --switch
ℹ Port 3000 is in use by node (PID 1234)
✔ Port 3001 is available

🔥 Dev mode (run + fix in one command)

portwiz dev 3000 -- npm run dev
⚠ Port 3000 is in use by node (PID 1234)
? Kill node (PID 1234)? (y/N) y
✔ Port 3000 is now free

ℹ Starting: npm run dev

👉 Automatically sets the PORT environment variable.


🧠 Doctor mode

Scan common development ports:

portwiz doctor
ℹ Scanning development ports...

  PORT    STATUS    PROCESS
  3000    in use    node (PID 1234)
  3001    free      -
  4200    free      -
  5000    in use    python3 (PID 5678)
  5173    free      -
  8080    in use    java (PID 9012)

⚠ 3 ports are in use

? Free all 3 busy ports? (y/N) y
✔ All ports are now free

Custom ports:

portwiz doctor --ports 4000,4001,4002

📖 Commands

| Command | Description | | ----------------------------- | ------------------------- | | portwiz <port> | Detect and free a port | | portwiz <port> --switch | Find next available port | | portwiz dev <port> -- <cmd> | Free port and run command | | portwiz doctor | Scan common dev ports |


⚙️ Options

| Flag | Short | Description | | ---------------- | ----- | -------------------------------------- | | --force | -f | Kill without confirmation | | --switch | -s | Find next free port instead of killing | | --ports <list> | — | Custom ports (doctor mode) | | --version | -V | Show version | | --help | -h | Show help |


🌍 Cross-platform

Works out of the box on all major platforms:

| Platform | Detection | Kill | | -------- | ---------------------- | ------------------- | | Windows | netstat + tasklist | taskkill | | macOS | lsof | SIGTERM / SIGKILL | | Linux | lsof / ss | SIGTERM / SIGKILL |


🎯 Use Cases

  • React / Vite / Next.js dev servers
  • Node.js / Express apps
  • Full-stack local development
  • Docker port conflicts
  • Multi-service environments

💡 Why portwiz?

  • ⚡ Zero setup
  • 🧠 Smart defaults
  • 🔥 Dev-friendly workflow
  • ⏱ Saves time every day

🚀 One-line Pitch

Stop fixing ports. Start building.


📄 License

MIT