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 🙏

© 2024 – Pkg Stats / Ryan Hefner

port-status

v1.0.3

Published

Detect port availability.

Downloads

11

Readme

port-status

Detect port availability.

Why?

  • Fast and convenient, easy to set up.
  • Namespaces builds in a human-friendly manner.
  • Encourages cache-safe URLs.
  • Uses a solid convention, build/<branch>/<version>.
  • Gracefully handles edge cases for git branches.

Install

npm install port-status --save

Usage

Get it into your program.

const portStatus = require('port-status');

Get a promise for the status of a port, as a lowercase string.

// On OS X without sudo, this will log 'Status: denied'.
// If you use sudo and it is free, then 'Status: ok'.
portStatus(
    80,           // port you want to check
    '127.0.0.1'   // optional hostname to try to bind on
)
.then((status) => {
    console.log('Status:', status);
});

Port status passes all arguments to Node's net.Server#listen(), so you can also use an object, for example.

portStatus({
    port     : 80,
    hostname : '127.0.0.1'
})
.then((status) => {
    console.log('Status:', status);
});

Make your .then() handler conditional, by using convenience methods that reject their promises if the port status is not exactly what you want.

// This will only log something if the port is already in use. Otherwise, the
// promise will reject, and you could use .catch() to print something.
portStatus(
    80,
    '127.0.0.1'
)
.ifBusy()
.then((status) => {
    console.log('Status:', status);
})

Contributing

See our contributing guidelines for more details.

  1. Fork it.
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request.

License

MPL-2.0

Go make something, dang it.