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-party

v2.0.0

Published

Run multiple http servers that share a port file and does automatic failover if the server listening on the port crashes

Downloads

9

Readme

http-party

Similar in scope to level-party but for http. Allows you to run multiple http servers that share a port file and does automatic failover if the server listening on the port crashes.

npm install http-party

build status dat

Usage

var party = require('http-party');

party('./PORT', // './PORT' is the port file the servers will use to coordinate.
  function onserver(server) {
    server.on('request', function(request, response) {
      response.end('hello world from '+pid);
    })
  },
  function ready(err, port) {
    console.log('Someone is listening on', port);
  }
);

The PORT file defaults to ./PORT. Try running the above example in a folder and spawn multiple processes.

cd some-dir
node example.js &
node example.js &
node example.js &
node example.js &
node example.js

The processes should print the same port. Try curling to that port

curl http://127.0.0.1:PORT

This should print the pid of a process. Try killing that process.

kill PID

If you curl the same url again one of the other processes will be listening instead! You can always cat the PORT file to figure out which port is being used. Also since we use a regular file instead of unix sockets this should also work on windows!

If you already have a server just pass than instead of the onserver function

var server = http.createServer(function(req, res) {
  res.end('hello world\n')
})

server.on('listening', function() {
  console.log('Server has started')
})

party('./PORT', server, function(err, port) {
  console.log('Someone is listening on', port);
})

License

MIT