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

path-event

v8.1.0

Published

The base object of the ending asterisk path strategy

Downloads

47

Readme

PathEvent Build Status Coverage Status

The PathEvent class, which inherits from y-lock, contains the logic behind the ending asterisk path strategy. Think of the event flow as an assembly line: when each listener is done with the event, it forwards it to the next one, until one of it decides that the event is fully handled and stops the flow.

Let's suppose our path is /what/an/example/this/is. With this example, the following events will be emitted, one after another:

/what/an/example/this/is
/what/an/example/this/*
/what/an/example/*
/what/an/*
/what/*
/*

As you can see, all flows start with the original path. The flow continues until the /* event is reached. Prefixes are allowed, e.g if you were using hsm and a POST request was what originated the event, the flow would be the following:

POST /what/an/example/this/is
/what/an/example/this/is
POST /what/an/example/this/*
/what/an/example/this/*
POST /what/an/example/*
/what/an/example/*
POST /what/an/*
/what/an/*
POST /what/*
/what/*
POST /*
/*

Each event object inherits from event.common which is the original PathEvent instance. event.args contains the rest of the path, e.g an/example/this/is. event.argv(n) returns an array of length n with each decoded component of the path. Take a look at the following example:


target.on('/animals/dogs/*',function*(e){
  var breed = e.argv(1)[0];

  yield e.take();
  if(breed == 'chihuahua'){

    e.give();  // Ignore chihuahuas
    yield e.take();   // If everyone else ignores it,
                      // take it back

    console.log('nobody likes this one!');
    return;
  }

  console.log('got a dog!');

});

target.on('/animals/*',function(e){
  var colour = e.argv(3)[2];

  yield e.take();
  if(colour == 'black'){
    e.give();  // I can't see black animals
    return;
  }

  console.log('got an animal!');

});

Consider these three events:

  • /animals/dogs/husky/black
  • /animals/dogs/chihuahua/white
  • /animals/dogs/chihuahua/black

The console output of those three events would be, respectively:

  • got a dog!
  • got an animal!
  • nobody likes this one!