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

once-promise

v2.0.0

Published

Promisify events.

Downloads

22

Readme

once-promise

Create promises for events.

CircleCI

Test Coverage Maintainability

Contents

  1. Breaking changes
  2. Usage examples
  3. JavaScript example
  4. TypeScript example
  5. Docs

Breaking changes

There are some incompatibilities between version 1.x and 2.x

  • The once() method is no longer the default export. See the examples for more information.
  • When providing multiple event names the array may no longer contain promises.

Usage examples

Await a single event

await once(process, 'exit')

This will await the "exit" event of the nodejs process.

Await multiple events

await once(readable, ['error', 'end'])

In this example we are awaiting the "error" or "end" event of a readable stream.

If the stream emits the "end" event, the promise will get resolved. If an "error" gets emitted first, the promise gets rejected with the error.

JavaScript example

const { once } = require('once-promise').default
const { EventEmitter } = require('events')

async function example () {
  const emitter = new EventEmitter()

  setTimeout(() => {
    emitter.emit('continue')
  }, 5000)

  console.log('start')

  // Create and await a promise for the "continue" event.
  // It should take 5s until the promise gets resolved.
  await once(emitter, 'continue')

  console.log('end :D')
}

example()

TypeScript example

import EventEmitter from 'events'
import { once } from 'once-promise'

async function example () {
  const emitter = new EventEmitter()


  setTimeout(() => {
    emitter.emit('continue')
  }, 5000)

  console.log('start')

  // Create and await a promise for the "continue" event.
  // It should take 5s until the promise gets resolved.
  await once(emitter, 'continue')

  console.log('end :D')
}

example()

Docs

once(emitter, event, arrayMode)

  1. emitter <internal.EventEmitter> - This can be any EventEmitter (e.g. the process object, a stream,...)
  2. event <string|string[]> - Either one eventname or an array containing the names of multiple events. If an array is passed, the returned promise will resolve to the first promise/event that gets resolved.
  3. arrayMode? <true> - If you pass true as last parameter, the promise will resolve to an array containing all arguments provided by the (fastest) event. This can be useful if an event emits multiple values.

Note: When you are listening for an "error" event and the event gets emittet, the promise gets rejected instead of resolved.