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

opifex.filter.seen

v0.0.1

Published

Pipes messages from source to destination filtering out ones it has seen recently

Downloads

1

Readme

Opifex.filter.seen

Filters messages based on having seen some characteristic of the data before

Getting Started:

The best way to see how to use opifex.filter.seen is with an RSS example:

opifex 'amqp://guest:guest@localhost:5672//rss-out/#/seen/seen-out/saw' filter.seen

Here we're mapping everything on the rss-out exchange to the seen queue, and on which the filter reads. The filter then outputs all of the not yet seen content to the seen-out exchange.

Once running we can then send a command and control message to tell filter.seen how to filter RSS feeds by injecting code over the bus:

[ "put", "/rss-out/filter", "filter",  "method", "article", "return article.guid" ]

The above message is using the WebSocket pontifex bridge. What it means is as follows:

"put" 			-> send the remainder of this message to a named resource path
"/rss-out/filter"	-> send it to the rss-out exchange, routing key filter
				payload is: [ "filter", "method", "article", "return article.guid" ]
"filter"		-> method of the recipient to execute
"method"		-> first parameter of the anonymous function we'll use to filter seen objects
"article"		-> second parameter of the anonymous function we'll use to filter seen objects
"return article.guid"	-> body of the filter function

This create a new anonymous function:

function (method,article {
	return article.guid;
}

Which will be used to identify which rss articles have been seen.