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

@cs125/wait-until

v0.0.3

Published

Simple library to wait until a condition has been satisfied.

Downloads

14,322

Readme

wait-until Build status npm package

This simple Node.js module provides a way to check for a condition every so often, then run a callback after the condition is met or the allotted time expires.

This is good if you need to wait for specific state changes in code that you don't have direct control over, like a headless web browser.

Usage

var waitUntil = require('wait-until');

waitUntil(interval, times, function condition() {
    return (someCondition ? true : false);
}, function done(result) {
    // result is true on success or false if the condition was never met
});

The condition function will be called up to times times, starting after interval milliseconds. Once it returns true (or a truthy value), the done callback will be called with result equal to true (or whatever value the condition function returned).

If the condition is never met within the specified timeframe, done will be called with result equal to false (or whatever falsy value the condition function returned the last time it was called).

Fluent interface

Don't want to remember the order of arguments? Then use the fluent interface:

var waitUntil = require('wait-until');

waitUntil()
    .interval(500)
    .times(10)
    .condition(function() {
        return (someCondition ? true : false);
    })
    .done(function(result) {
        // do stuff
    });

Async conditions

If the condition function accepts an argument, then it is assumed to be a callback function which will be called with the result of the test:

var waitUntil = require('wait-until');

waitUntil()
    .interval(500)
    .times(10)
    .condition(function(cb) {
        process.nextTick(function() {
            cb(someCondition ? true : false);
        });
    })
    .done(function(result) {
        // do stuff
    });

Other notes

You can specify .times(Infinity) if you like, but it's probably better to set and enforce a reasonable timeout.