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

on-up

v0.0.1-2

Published

calls back on up or after time is up

Downloads

15

Readme

on-up

NPM

Calls back on up or after time is up.

Why

When doing Continuous Integration, for example with Travis, one has to guess how long a server will take to start, sleep more than necessary and hope it's enough.

No longer necessary.

How

Waits for a server to come up with a rsponse to a request. A callback is invoked with the response and / or metadata. There is a timeout and various other configuration settings.

Use

See wait-up for simple command-line use. The bin.js example of how I use the library. Usually, it provides everything necessary.

Options

In case you want more, here are the defaults to override:

req:
  uri: "/" #localhost port 80 prepended if / is the first char
  timeout: 1000 # how long request will wait before timing-out / repeat
spacings: 240 # time in-between retries
patience: 42000 # the ultimate patience (i.e. max duration wait)
dots: false # true allows side-effects (i.e. write dots to stdout)

See request options. for what req takes. Of-course, the numbers are in milliseconds.

License

MIT