Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
ultron
Advanced tools
Readme
Ultron is a high-intelligence robot. It gathers intelligence so it can start improving upon his rudimentary design. It will learn your event emitting patterns and find ways to exterminate them. Allowing you to remove only the event emitters that you assigned and not the ones that your users or developers assigned. This can prevent race conditions, memory leaks and even file descriptor leaks from ever happening as you won't remove clean up processes.
The module is designed to be used in browsers using browserify and in Node.js. You can install the module through the public npm registry by running the following command in CLI:
npm install --save ultron
In all examples we assume that you've required the library as following:
'use strict';
var Ultron = require('ultron');
Now that we've required the library we can construct our first Ultron
instance.
The constructor requires one argument which should be the EventEmitter
instance that we need to operate upon. This can be the EventEmitter
module
that ships with Node.js or EventEmitter3
or anything else as long as it
follow the same API and internal structure as these 2. So with that in mind we
can create the instance:
//
// For the sake of this example we're going to construct an empty EventEmitter
//
var EventEmitter = require('events').EventEmitter; // or require('eventmitter3');
var events = new EventEmitter();
var ultron = new Ultron(events);
You can now use the following API's from the Ultron instance:
Register a new event listener for the given event. It follows the exact same API
as EventEmitter.on
but it will return itself instead of returning the
EventEmitter instance. If you are using EventEmitter3 it also supports the
context param:
ultron.on('event-name', handler, { custom: 'function context' });
Just like you would expect, it can also be chained together.
ultron
.on('event-name', handler)
.on('another event', handler);
Exactly the same as the Ultron.on but it only allows the execution once.
Just like you would expect, it can also be chained together.
ultron
.once('event-name', handler, { custom: 'this value' })
.once('another event', handler);
This is where all the magic happens and the safe removal starts. This function accepts different argument styles:
removeAllListeners()
API.
and ,
to create a
list of events that need to be cleared.ultron.remove('foo, bar baz'); // Removes foo, bar and baz.
ultron.remove('foo', 'bar', 'baz'); // Removes foo, bar and baz.
ultron.remove(); // Removes everything.
If you just want to remove a single event listener using a function reference
you can still use the EventEmitter's removeListener(event, fn)
API:
function foo() {}
ultron.on('foo', foo);
events.removeListener('foo', foo);
MIT
FAQs
Ultron is high-intelligence robot. It gathers intel so it can start improving upon his rudimentary design
The npm package ultron receives a total of 1,422,892 weekly downloads. As such, ultron popularity was classified as popular.
We found that ultron demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers 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
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.