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

portend

v1.0.0

Published

Treat emitted events as promises

Downloads

4

Readme

Portend

Build Status Coverage Status

Portend is a utility for expecting a particular event to be emitted a specific number of times.

It can be useful for writing tests in which a known number of events are expected to be emitted, and the test must wait before proceeding.

Usage

Portend requires that it be called with an EventEmitter-like object (something with an on function) and an event name. By default, it will expect the event to be fired once, but this can be overridden with the third parameter.

Generic Scenario

const portend = require('portend');

// Wait for my.event to be emitted twice from the emitter
portend(emitter, 'my.event', 2).then(events => {
	// events will ['test', 'test 2']
});

emitter.emit('my.event', 'test');
emitter.emit('my.event', 'test 2');

Shortcuts

There are a few shortcuts for setting up the expected number of emits. once, twice, and thrice can be used to expect 1, 2 and 3 emits respectively.

const portend = require('portend');

// Wait for my.event to be emitted once
portend.once(emitter, 'my.event').then(events => {
	// events will be ['test']
});

emitter.emit('my.event', 'test');