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

promissary

v0.2.0

Published

A tiny library for manually resolving promises

Readme

Promisssary

A library for manually resolving promises.

Why?

I needed callbacks, but I didn't want to end up in a callback hell. I like Promises and this is what I wanted.

new SomeTask(<params>).run().then(val => (...));
// or
const val = await new SomeTask(<params>).run();

Q: ES6 Promises work. Why would anybody want to resolve them manually?

A: When using requestAnimationFrame, setTimeout or such you just don't have enough control to put everything in the Promise constructor. Well, you can of course, but I ended up with a messy code. So I built a wrapper around Promises to resolve them manually for this extra bit of flexibility.

Usage

import Promissary from 'promissary';

For the love of god, please define a promissary as private. You don't want anybody outside of your task to resolve it, do you?

class SomeTask {
  private finished: Promissary<boolean>;
  ...
}

Initialize it in a public method or a constructor

  constructor() {
    ...
    this.finished = new Promissary<boolean>();
    ...
  }

Do the actual asynchronous part in a private method and resolve.

  private doTheWork() {
    ...
    // however you're gonna check if it is done
    if (this.done()) {
      this.finished.resolve(true);
    }

    // as an example of why you might want to need to resolve the promise manually
    requestAnimationFrame(doTheWork.bind(this));
  }

Make a public method returning the promise

  public run() {
    this.doTheWork();
    return this.finished.promise;
  }

Now you can execute your asynchronous task with then or await.

Typescript

It's written in typescript and the type definitions are included. Tbh, I don't think it's a good idea to use this in vanilla javascript. At least the typescript compiler does enforce private functions.