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

w8r

v4.0.1

Published

w8r

Readme

w8r

Greenkeeper badge Build Status Poll to see if a service is running, and once it is, fork a new node process

Huh?

(net|http).createServer()#listen is async. Sometimes you want to do something but only after the a server has started. You can just hope it starts in time, or you can use this.

Also useful for docker-compose -- if you have dependent containers, docker will wait for the container to be ready, but it doesn't know if the service is ready yet. This makes sure your app won't start until the service it depends on is available.

Usage

npm install --save w8r

const w8r = require('w8r')
const serverlist = [{host: 'redis', port: 6379}, '/var/run/mysql']
w8r(50, serverlist, 'start-server.js', (err, child) => {
  // both services are up and running!
  // and child is your child process you started!
})

API

  • w8r(checkInterval:number, serverList:array, procfile:string, procargs?:array(string), procopts?:object, cb:function) Spawn a net client to check to see if the server at the provided host:port is available every checkInterval ms and then fork a new node process.

  • checkInterval:number - amount of delay, in ms, before trying again

  • profile:string - the path to the entry point for the child process

  • procargs:array(string) (optional) - arguments to your command

  • procopts:object (optional) - options for the child_process.fork command

The serverList array can contain two separate object types:

  • paths to unix domain sockets (e.g.: /var/run/mysql)
  • objects containing a port and host key (e.g.: {port: 6379, host: 'redis'})

Licence

Copyright © 2016 Scripto, LLC. Apache-2.0 Licensed.