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

gordon

v0.0.4

Published

a natural language event-emitter interface.

Downloads

2

Readme

gordon

a natural language event-emitter interface.

NPM

usage

Gordon's interface is based on the traditional event emitter, but with a few twists to support the ideas of natural language. Event names work like normal, but pennyworth templates can be associated with event names for a more natural experience.

When .emit() is called with a natural language string, gordon will find the most appropriate registered event and use its most appropriate template to parse the emitted text. The event will then be fired with the event data being the compiled template.

initializing a new emitter

var Gordon = require('gordon');
var emitter = new Gordon();

adding an event listener

For unregistered events, you can use .when() to attach an event handler to a trigger template.

emitter.when('my name is $subject.', function (data) {
  console.log('hello there, %s', data.subject);
});

registering an event

To register an event is to associate a certain trigger template or list of templates with an event. This allows you to hook onto a group of templates that will provide you with the same data.

On every call, you can register a single template or a list of templates. Follow up calls will not re-allocate the template list but rather append to it.

emitter.register('introduction', [
  '[... hi, hey, hello], $subject.',
  'how are you, $subject?'
]);

attaching to an event

This works exactly the same as with a regular event emitter.

emitter.on('introduction', function (data) {
  console.log('hello there, %s.', data.subject);
});

emitting an event (using a trigger)

Call emit with a trigger, which is the input data to a pennyworth template.

emitter.emit('hey, Gordon.');