Simple and modern async event emitter

It's only ~200 bytes minified and gzipped. I'm not fanatic about keeping the size at this level though.

Emitting events asynchronously is important for production code where you want the least amount of synchronous operations.

$ npm install emittery

const Emittery = require('emittery');
const emitter = new Emittery();

emitter.on('🦄', data => {
	console.log(data);
	// '🌈'
});

emitter.emit('🦄', '🌈');

The above only works in Node.js 8 or newer. For older Node.js versions you can use require('emittery/legacy').

Subscribe to an event.

Returns an unsubscribe method.

Using the same listener multiple times for the same event will result in only one method call per emitted event.

Unsubscribe to an event.

If you don't pass in a listener, it will remove all listeners for that event.

Subscribe to an event only once. It will be unsubscribed after the first event.

Returns a promise for the event data when eventName is emitted.

emitter.once('🦄').then(data => {
	console.log(data);
	//=> '🌈'
});

emitter.emit('🦄', '🌈');

Trigger an event asynchronously, optionally with some data. Listeners are called in the order they were added, but execute concurrently.

Returns a promise for when all the event listeners are done. Done meaning executed if synchronous or resolved when an async/promise-returning function. You usually wouldn't want to wait for this, but you could for example catch possible errors. If any of the listeners throw/reject, the returned promise will be rejected with the error, but the other listeners will not be affected.

Same as above, but it waits for each listener to resolve before triggering the next one. This can be useful if your events depend on each other. Although ideally they should not. Prefer emit() whenever possible.

If any of the listeners throw/reject, the returned promise will be rejected with the error and the remaining listeners will not be called.

Subscribe to be notified about any event.

Returns a method to unsubscribe.

Unsubscribe an onAny listener.

If you don't pass in a listener, it will remove all onAny listeners.

Clear all event listeners on the instance.

The number of listeners for the eventName or all events if not specified.

There are many things to not like about EventEmitter: its huge API surface, synchronous event emitting, magic error event, flawed memory leak detection. Emittery has none of that.

Mostly backwards compatibility reasons. The Node.js team can't break the whole ecosystem.

It also allows silly code like this:

let unicorn = false;

emitter.on('🦄', () => {
	unicorn = true;
});

emitter.emit('🦄');

console.log(unicorn);
//=> true

But I would argue doing that shows a deeper lack of Node.js and async comprehension and is not something we should optimize for. The benefit of async emitting is much greater.

No, just use destructuring:

emitter.on('🦄', ([foo, bar]) => {
	console.log(foo, bar);
});

emitter.emit('🦄', [foo, bar]);

• p-event - Promisify an event by waiting for it to be emitted

MIT © Sindre Sorhus