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

event-emitte-ts

v1.3.5

Published

Readme

EventEmitter in TypeScript

npm i --save es-event-emitter or git clone https://github.com/Zlobin/es-event-emitter.git cd es-event-emitter && npm i && webpack

Benchmark

Run npm start.

const EM = new EventEmitter();

EM
  .on('foo', () => 'response')
  .emit('foo');

Dependencies

There are no dependencies. You need only npm installed and just run npm i to grab the development dependencies.

Examples

var EM = require('es-event-emitter');
html include:
<script src="<PATH/TO/LIBRARY>/dist/bundle.js">
Or ES2015 import:
import EM from 'es-event-emitter';
// ...
Creating an instance.
var EM = new EventEmitter();
An usual example.
EM.on('foo', function() {
  // some code...
});

EM.emit('foo');
It will be triggered only once and then callbacks will be removed.
EM.once('foo', function() {
  // some code...
});

EM.emit('foo');
// Nothing happend.
EM.emit('foo');
Callback with parameters.
EM.once('foo', function(bar, baz) {
  // some code...
});

EM.emit('foo', 'var 1 for bar', 'var 2 for baz');
Callback's call can be ordered by "weight" parameter.
EM.on('foo', function() {
  console.log('3');
}, null, 1);

EM.on('foo', function() {
  console.log('1');
}, null, 3);

EM.on('foo', function() {
  console.log('2');
}, null, 2);

EM.emit('foo');
// 3
// 2
// 1
Chaining.
EM.on('foo', function() {
  // some code...
});

EM
  .emit('foo')
  .emit('foo')
  .off('foo');
Set maxNumberOfListeners as a parameter when creating new instance.
const EM = new EventEmitter(1);

EM.on('foo', function() {
  // some code...
});
// Note: it will show notification in console.
EM.on('foo', function() {
  // some other code...
});

Testing

Tests are performed using mocha and expect library npm test.

Building the documentation

You can use JSDoc comments found within the source code.

Todo

  1. Add event's namespace:
EM.on('foo.*', function() {
  // some code...
});
  1. Add events through comma:
EM.on('foo,bar,baz', function() {
  // some code...
});
  1. Add method "onAny" for listening each event:
EM.onAny(function() {
  // some code...
});