
Security News
Axios Maintainer Confirms Social Engineering Attack Behind npm Compromise
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
eventyoshi
Advanced tools
Allows several event emitters to be listened and emitted through a single one.
Allows several event emitters to be handled and emitting to a single one.

const EventEmitter = require('events').EventEmitter;
const EventYoshi = require('eventyoshi');
let ee1 = new EventEmitter();
let ee2 = new EventEmitter();
let yoshi = new EventYoshi()
.add(ee1)
.add(ee2);
yoshi.on('foo', () => {
console.log('foo!');
});
ee1.emit('foo'); // foo!
ee2.emit('foo'); // foo!
Why would you use this instead of doing something like
ee1.on('foo', listener);
ee2.on('foo', listener);
Well, you could do that, or you could let EventYoshi handle all the logic for you flawlessly and without modifying the underlying child event emitters. EventYoshi can be treated as another EventEmitter. You can pass it around without having to tell whoever you passed it to what emitters you're listening to and which you aren't listening to anymore.
Same goes for events you might listen to or remove later. As you add more event emitters to event yoshi, it will add listeners that you were already listening for to the emitter you added.
let yoshi = new EventYoshi();
yoshi.on('a', () => {
console.log('a emitted');
});
let ee = new EventEmitter();
yoshi.add(ee);
ee.emit('a'); // a emitted
And as you remove emitters, all listeners that were added through event yoshi are removed.
yoshi.remove(ee);
ee.emit('a'); // nothing emitted on yoshi
EventYoshi also supports the once method. It supports listening to newListener such that it is emitted only when listeners are added to your EventYoshi instance and not when they are added to child emitters.
Adds an event emitter to an event yoshi.
Remove an event emitter from an event yoshi.
Proxies all calls from to yoshi[fn] to its children.
yoshi.add(writeStream);
yoshi.proxy('write', 'end');
yoshi.write(data); // this will call writeStream.write() with data
yoshi.end(); // will call writeStream.end()
When the proxy'd functions are called, they return the values returned from called functions in an array. If the array's length is only 1, returns only the first value.
When events are emitted, yoshi.child will contain the child emitter the event came from.
yoshi.on('event', () => {
console.log('Event came from: ', yoshi.child);
});
string - Event.Function - Listener.Emitted when a listener is added to a child event emitter. Does not emit listeners added by EventYoshi.
string - Event.Function - Listener.Emitted when a listener is removed from a child event emitter. Does not emit listeners added by EventYoshi.
npm install eventyoshi
Tests are written with mocha
npm test
FAQs
Allows several event emitters to be listened and emitted through a single one.
The npm package eventyoshi receives a total of 274 weekly downloads. As such, eventyoshi popularity was classified as not popular.
We found that eventyoshi 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
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.

Security News
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.