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

kill-port-process

v4.0.2

Published

Easily kill hanging processes on ports - on any platform!

Readme

Kill-port-process

npm version Test CodeQL

Cross-platform module to stop one (or more) process(es) running on a port (or a list of ports).

Install

$ npm install kill-port-process
# or
$ yarn add kill-port-process

Usage

Programmatically

const { killPortProcess } = require('kill-port-process');

(async () => {
  // long running process running on a given port(s), e.g. a http-server
  // takes a number, number[], string or string[]
  // single port
  await killPortProcess(1234);

  // multiple ports
  await killPortProcess([1234, 6789]);

  // with options
  await killPortProcess(1234, { signal: 'SIGTERM' });
})();

Options

  • signal (optional): used to determine the command used to kill the provided port(s). Valid values are:
    • SIGKILL (default)
    • SIGTERM
  • silent (optional): suppresses the output of the command regardless of the result. takes a boolean, default is false.

CLI

Install the module globally:

npm install kill-port-process -g

You can use the CLI calling it with kill-port <port>.

It takes a single port or a list of ports separated by a space. Valid flags are -p and --port but are both optional.

$ kill-port 1234
# or multiple ports, separated by space(s)
$ kill-port 1234 2345
# or
$ kill-port -p 1234
# or
$ kill-port --port 1234

Flags

  • --graceful kill the process gracefully.
    • Unix: Sends a -15 signal to kill (SIGTERM) rather than -9 (SIGKILL)
    • Win: Currently no use
  • --silent suppresses the output of the command regardless of the result. takes a boolean, default is false.

"Buy Me A Coffee"