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

http-port-guard

v1.0.0

Published

Wrap an HTTP server 'start' function in asynchronous checks for port availability.

Downloads

2

Readme

Node.js HTTP Port Guard

Wrap a server "start" function in asynchronous checks for port availability. Fail if the port is already in use prior to function execution or if the port does not become utilized after execution.

The only reliable way to determine if a server process has started successfully is to poll the port it has been assigned. If this port is already in use*, the child process will fail to start, but the current process will consider the operation a success. This invalidates the kill function created by this module and will likely lead to errors during test cleanup.

* This condition will most commonly be caused by a zombie server instance erroneously created in some prior test run.

API

This module exposes a single function that accepts two arguments: the desired port and a function that is expected to bind to that port (the actual binding may take place in another process). This function should return a kill callback function that kills the server

var portGuard = require('http-port-guard');

portGuard(8000, function() {
  var app = startMyApp();

  return app.destroy;
}).then(function(kill) {
  console.log('Application is now available on port 8000!');

  console.log('Now destroying application.');
  kill();
});

If the second argument is an object, it will be interpreted as an "options" object, and the following properties will be honored:

  • host - {string} - Host name of the server to poll. Defaults to 'localhost'
  • retryPeriod - {string} - number of milliseconds to wait between port polling operations; defaults to 100
  • retryCount - {string} - number of polling failures to tolerate before considering the operation a failure; defaults to 100
  • Promise - {Function} - Promise A/+ constructor; defaults to globally-defined Promise

The function resutns a Promise that is rejected if the port is already in use or if requests to the specified port fail after startup. It is resolved with the kill callback function provided by startFn.

License

Copyright (c) 2015 Mike Pennisi
Licensed under the MIT license.