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 🙏

© 2024 – Pkg Stats / Ryan Hefner

eventide

v0.2.0

Published

events mixin

Downloads

3

Readme

Eventide Build Status

Namespaced events as a mixin

Installation

npm install eventide

Usage

Using your favourite way of mixing in objects, add eventide to an object. For example, using _.extend:

function Person() {}
_.extend(Person.prototype, eventide, {
	eat: function(food) {
		this.emit('eaten:' + food);
	}
});

var matt = new Person;
matt.on('eaten', function(food) {
	console.log('mmm, ' + food);
});
matt.eat('peanut butter'); // => "mmm, peanut butter"

Or with Livescript's implements:

class Person implements eventide
	...

API

.on(event, handler)

Registers handler to handle event.

.off([event, [handler]])

Removes event handlers. If event is given, removes all handlers for event. If both event and handler are given, removes that particular event handler.

.once(event, handler)

Like on, but removes the handler when the event has fired.

.onAny(handler)

Triggers when any event is emitted. The first argument is the event name.

.offAny([handler])

Remove a particular handler for onAny, or all handlers.

What's wrong with EventEmitter (2)?

Node's built-in EventEmitter and EventEmitter2 are great and all, but both require subclassing to use with your own objects. Eventide is a plain object, and its functions perform their own setup. Just mix in to whatever.

Licence

MIT. © 2014 Matt Brennan.