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

duckline

v0.1.2

Published

Run a list of async tasks **sequentially** and collect results.

Readme

Duckline

Run a list of async tasks sequentially and collect results.

Install

If you publish this package later, consumers can do:

npm i duckline

For local development in this repo:

npm i
npm run build

Build outputs:

  • dist/index.cjs.js (CommonJS, ES5)
  • dist/index.esm.js (ESM, ES5)
  • dist/index.d.ts (TypeScript declarations)

API

import Duckline, { type DockResult } from "duckline";

type DucklineOptions<T> = {
  tasks: Array<(() => Promise<T>) | Promise<T>>;
  throwErrors?: boolean;
  consumer?: (task: DockResult<T>) => void;
};
  • new Duckline({ tasks, throwErrors, consumer }): create a runner.
  • duck.run(): executes tasks sequentially.
  • duck.results: array of successful task results (in order).

Examples

Example 1: run tasks and collect successful results

import Duckline from "duckline";

const sleep = (ms: number) => new Promise<void>((r) => setTimeout(r, ms));

const duck = new Duckline<number>({
  tasks: [
    async () => {
      await sleep(50);
      return 1;
    },
    Promise.resolve(2),
    async () => 3,
  ],
});

await duck.run();
console.log(duck.results); // [1, 2, 3]

Example 2: handle failures without throwing + observe each task

import Duckline, { type DockResult } from "duckline";

const duck = new Duckline<string>({
  tasks: [
    async () => "ok-1",
    async () => {
      throw new Error("boom");
    },
    Promise.resolve("ok-2"),
  ],
  throwErrors: false,
  consumer: (result: DockResult<string>) => {
    if (result.ok) {
      console.log("consumer ok:", result.data);
    } else {
      console.log("consumer failed:", result.error);
    }
  },
});

await duck.run();
console.log("successful results:", duck.results); // ["ok-1", "ok-2"]

Example 3: stop on first failure (throwErrors: true)

import Duckline from "duckline";

const duck = new Duckline<string>({
  tasks: [
    async () => "ok",
    async () => {
      throw new Error("stop here");
    },
    async () => "never reached",
  ],
  throwErrors: true,
});

await duck.run(); // throws Error("stop here")