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

trytryagain

v1.2.0

Published

Keep trying until it works. Actually a very reliable testing strategy.

Downloads

486

Readme

If at first you don't succeed, try try again

if at first you don't succeed, try try again

Retrying assertions is a very reliable strategy for testing applications, whether you're testing in the browser, on mobile, or testing networked applications. Anywhere timing is variable.

var retry = require('trytryagain');

describe('my application', function () {
  it('has the right title', function () {

    return retry(function () {

      return browser.title().then(function (title) {
        return expect(title).to.equal('My App');
      });

    });

  });
});

NPM: trytryagain

npm install trytryagain

retry

var promise = retry(function, [options]);
var promise = retry([options], function);
  • function is a function that will be called repeatedly until it doesn't throw an exception, or return a promise that is rejected.
  • options.timeout millisecond to retry until giving up. default 1000.
  • options.interval retry interval in milliseconds. default 10.

Returns a promise. If the function eventually returns a value then this promise will be fulfilled with that value. If the function continually throws or rejects, then this function will be rejected with the error.

retry.ensuring

retry.ensuring is kind of the oppposite of retry, it keeps trying the assertion as long as it doesn't fail, and fails immediately if it fails. This is useful in situation where you want to ensure that something doesn't happen, but you want to check long enough to be sure.

var promise = retry.ensuring(function, [options]);
var promise = retry.ensuring([options], function);
  • function is a function that will be called repeatedly until it does throw an exception, or until duration milliseconds has passed.
  • options.duration milliseconds to retry before declaring success. default 1000.
  • options.interval retry interval in milliseconds. default 10.