
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@qoopido/emitter
Advanced tools
Ultra-flexible & dead simple event emitter supporting RegExp-based event subscription and global listeners
Ultra-flexible & dead simple event emitter supporting RegExp-based event subscription and global listeners.
$ npm install --save @qoopido/emitter # npm
$ yarn add @qoopido/emitter # yarn
The only thing left to do after installation via NPM or yarn is to require the module:
$ import Emitter from '@qoopido/emitter'; // esm
$ const Emitter = require('@qoopido/emitter'); // cjs
Afterwards you can either create an instance or extend Emitter with your own class and use its methods as described below.
Listeners (also referred to as callbacks) must be of type Function which will always receive an instance of type Event as their first parameter. If the event was emitted with further parameters these will be passed to the listener as separate arguments.
The passed Event instance offers access to the event name as well as its context and, in addition, offers a cancel method to stop further processing of an event.
The emitter offers a total of three methods to subscribe to events: on, once and limit.
// register an event listener
emitter.on({String|RegExp|(String|RegExp)[]} identifier, {Function} callback, {Boolean=} prepend, {Number=} limit);
// register a once only event listener
emitter.once({String|RegExp|(String|RegExp)[]} identifier, {Function} callback, {Boolean=} prepend);
// register an event listener that gets called a limited number of times
emitter.limit({String|RegExp|(String|RegExp)[]} identifier, {Number} limit, {Function} callback);
identifier can either be a specific event name as String, a pattern of event names as RegExp or an array of both which gives you almost endless flexibitlity.
The only method to know is the off method:
emitter.off({String|RegExp|(String|RegExp)[]} identifier, {Function=} callback);
identifier can, again, either be a specific event name as String, a pattern of event names as RegExp or an array of both. Just keep in mind that unsubscribing from a specific event name will never unsubscribe a RegExp-listener and vice versa.
Any instance of Emitter has its own emit method:
emitter.emit({String} name, ...details);
If you need to retrieve any existing listener for a specific event simply use
emitter.listener({String} name);
Calling listener will always return an array which may be empty.
Any method beside listener returns the current instance to offer a chainable interface.
It is possible to not only subscribe to events emitted by a known instance of Emitter but also to subscribe to events emitted by any existing and/or future instance. This behaviour allows, e.g., to subscribe to events globally for logging purposes and the likes.
var Emitter = require('@qoopido/emitter');
// register a broadcast listener
Emitter.on({String|RegExp|(String|RegExp)[]} identifier, {Function} callback, {Boolean=} prepend, {Number=} limit);
// register a once only broadcast listener
Emitter.once({String|RegExp|(String|RegExp)[]} identifier, {Function} callback, {Boolean=} prepend);
// register a broadcast listener that gets called a limited number of times
Emitter.limit({String|RegExp|(String|RegExp)[]} identifier, {Number} limit, {Function} callback);
// unregsiter a broadcast listener
Emitter.off({String|RegExp|(String|RegExp)[]} identifier, {Function=} callback);
// retrieve boradcast listeners for a specific event
Emitter.listener({String} name);
FAQs
Ultra-flexible & dead simple event emitter supporting RegExp-based event subscription and global listeners
We found that @qoopido/emitter demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.