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

withwait

v0.1.1

Published

Ensure operations involving sleeping always complete, even if an exception occurs during execution

Readme

Withwait

Ensure operations involving sleeping always complete, even if an exception occurs during execution.

Motivation

When testing flaky code, failure to wait for timeouts to resolve before moving onto the next test can cause crashes and confusing test failures. Obviously, it'd be best to fix the flakiness, but if you're testing someone else's work (eg when auto-marking COMP1531), that may not be an option.

If you want to have a certain operation always take a consistent amount of time, eg to prevent timing attacks on login systems, this could be used to delay sending a response to a request with incorrect credentials.

Installation

npm install withwait (optionally --save-dev if you're just using it for testing).

Usage

import { wait } from 'withwait';

const result = await wait(() => {
    // Do some operation
}, 1000);

// At this point, at least 1000 ms is guaranteed to have passed

Even if an error is thrown, the time will still pass.

import { wait } from 'withwait';

try {
    await wait(() => {
        throw Error('Uh oh!');
    }, 1000);
    // The error wasn't silenced, so after 1000ms it'll be thrown again and
    // jump to the `catch` block.
} catch (e) {
    // 1000 ms has passed
    console.log('Error was caught:', e);
}

There is also a synchronous version of the function. It blocks the event loop, so you probably shouldn't use it unless you really need to, but it does work.

import { waitSync } from 'withwait';

const result = waitSync(() => {}, 1000);