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

get-ports

v1.0.3

Published

gets multiple open ports

Downloads

39,833

Readme

get-ports

stable

Finds multiple open ports after your specified base ports, and below the max range.

Unlike getport or get-port, this is useful for situations where you need multiple servers to run on open ports.

If not all ports could be found, the error callback is triggered.

Install

npm install get-ports --save

Example

The resulting ports array is parallel to your input (base) ports.

For example, if port 8000 and 9966 are already in use:

var getPorts = require('get-ports')

getPorts([ 8000, 9966 ], function (err, ports) {
  if (err) throw new Error('could not open servers')
  
  console.log(ports)
  //=> [ 8001, 9967 ]
})

Usage

NPM

getPorts(basePorts, [maxPort], callback)

For the given array of basePorts, tries to find the next available port from each one. This keeps track of available ports to ensure there are no conflicts in the final result.

If the finite number maxPort is specified, the portfinding will fail when it reaches that maximum port. Defaults to 60000.

The callback is called with (err, ports), where err will be an Error if any of the portfindings failed (i.e. no open ports within range). If successful, err will be null and ports will be an array, parallel to basePorts, with the found port numbers.

License

MIT, see LICENSE.md for details.