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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@art-suite/art-core-ts-async

v0.2.11

Published

Async and Promise utilities for TypeScript

Downloads

1,429

Readme

@art-suite/art-core-ts-async

Essential async utilities for TypeScript, including robust timeout helpers for Promises.

Why This Module?

It makes common async operations more succinct, clearer, and less error-prone—while providing modern, Promise-based alternatives to legacy APIs like setTimeout. This module helps you write more readable and maintainable async code with a simple, type-safe API.

  • timeout: Create a Promise that resolves after a specified delay, optionally running a function after the timeout.
  • timeoutAt: Create a Promise that resolves at a specific time (Date, timestamp, or date string), optionally running a function after the timeout.

Example Installation and Use (Required)

Install with npm:

npm install @art-suite/art-core-ts-async

Basic usage:

import { timeout, timeoutAt } from "@art-suite/art-core-ts-async";

// Wait for 500ms
await timeout(500);

// Wait for 1 second, then run a function
await timeout(1000, () => console.log("done"));

// Wait until a specific time (e.g., 2 seconds from now)
await timeoutAt(Date.now() + 2000);

// Wait until a specific time, then run a function
await timeoutAt(new Date(Date.now() + 1000), () => "finished"); // resolves to "finished"

Functional Overview

timeout(ms: number, f?: () => unknown): Promise<unknown>

Creates a Promise that resolves after a specified number of milliseconds. Optionally, a function can be provided to be called after the timeout. If so, the Promise will resolve with the result of the function.

  • timeout(1000) → resolves after 1 second
  • timeout(500, () => "done") → resolves after 500ms with value "done"

timeoutAt(triggerAtTime: AllDateTypes, f?: () => unknown): Promise<unknown>

Creates a Promise that resolves at a specific time. The time can be a Date, a number (seconds or milliseconds), or a date-time string. Optionally, a function can be provided to be called after the timeout. If so, the Promise will resolve with the result of the function.

  • timeoutAt(Date.now() + 1000) → resolves after 1 second
  • timeoutAt(new Date(Date.now() + 500), () => 42) → resolves after 500ms with value 42

API Documentation Reference

For detailed information on all exported functions and their parameters, please refer to the TypeScript typings and JSDoc comments within the source code.