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

filter-event

v0.2.0

Published

Mercury.js / vdom compatible event for taking a firehose of events and listening to specific ones.

Downloads

2

Readme

filter-event

mercury / vdom compatible event for taking a firehose of events and reducing to the ones you want.

Scenario

I was working on an app where I need to capture just the focus events (focusin, focusout) for a given input, then modify state. When using value-event/event, I can broadcast and receive the event, but this has 2 problems:

  1. Since the original event object and DOM element are de-coupled, it is not possible to know the type of event fired. I just know that there was AN event.
  2. A large number of events are being fired. Most of them are not important to me.

Solution

Added value-event/filter event. This works exactly like value-event/eventexcept that it takes a whitelist of event names that it will allow to pass. This allows event targeting without bringing any part of the event or DOM forward into the handler or channel.

Usage

var sendFilteredEvent  = require('value-event/filter.js');

var state = { 
  active: false
};
var active_handler = function(active) {
  state.active = active;
};
var text_handlers = [

  sendFilteredEvent(active_handler, true , {
    event_types: ['focusin']
  }), 

  sendFilteredEvent(active_handler, false, {
    event_types: ['focusout']
  })
];

Now the VDOM part

h('input', {
  'ev-event': text_handlers,
  name: 'dogs',
  type: 'text'
});