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

deniable-emitter

v0.0.2

Published

Deniable Event Emitter

Downloads

2

Readme

Deniable Emitter

Deniable Event Emitter for asynchronous verification

Contents

  • Installation
  • Usage
  • API
    • new DeniableEmitter()
    • de.on()
    • de.once()
    • de.emit()
    • de.off()
  • Contributing guidelines

Installation

npm install --save deniable-emitter

Usage


// Importing the module
import { DeniableEmitter } from 'deniable-emitter';

// TODO: better example

API

constructor


// Importing the module
import { DeniableEmitter } from 'deniable-emitter';

// Initialize a new emitter
const emitter = new DeniableEmitter();

// TODO: explain inheritance isn't thought of

de.on()

function handler( name, ...args ) {
  const callback = args.pop(); // (err,value)=>{}
  
  // Finish by returning a value
  return 'Resolving value';
  
  // Finish by calling the callback
  callback();
  
  // Finish with an error
  callback('Some error');
  
  // Or return a promise
  return new Promise(function( resolve, reject ) {
    // ... your code ...
  });
}

// Make the handler listen for any events
emitter.on('*', handler);
// < emitter

// Make the handler listen for foo events
emitter.on('foo', handler);
// < emitter

// TODO: better explanation

de.once()

// TODO

de.emit()


// Always returns undefined & tries callback
emitter.emit('foo', function( err, response ) {
  console.log(response); // > "Resolving value";
});
// < undefined

// TODO: better explanation

de.off()


// Removes handler from the foo event
emitter.off('foo', handler);
// < emitter

// TODO: better explanation

Contributing guidelines

Bugs

Take a peek at the issues page to ensure your issue isn't already known and/or being worked on. If it's not, please create a new issue with a detailed description of what happend & how to reproduce the unexpected behavior.

If you decide to take on the challenge of fixing a known (or unknown) issue, you can do so by sending in a pull request from your own fork of the project. Once it has been tested and approved, it will be merged into the master branch of the repository.

Feature requests

If you can't find a feature you like in the repository, please go to the issues page to search for the feature you would like to see. If you still can't find it, you can request a new feature by creating a new issue with the feature-request, providing a detailed description of the feature, how it would work & preferably what issue it would solve.

New code for feature requests follows the same path as code for bug fixes.