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.pipe

v0.0.1

Published

A generic pipe for moving messages from A to B

Downloads

1

Readme

Opifex.pipe

A dynamically reconfigurable pipe

Getting Started:

You can start up an opifex.pipe as follows

opifex 'amqp://guest:guest@localhost:5672//rss-out/#/pipe-in/pipe-out/' pipe

This will send everything on the rss-out exchange to the pipe-in queue, and then the pipe will pipe it out preserving the incoming routing key.

By default every message is routed to the destination exchange, such as the pipe-out exchange in the example above. It is possible, however, to add a transform functionality to the pipe at run time.

[ <pipe id>, <arguments>...,  <function body> ]

Which will add a filter to the pipe which will execute on every incoming message (with the exception of those with the explicit id of the pipe).

Upon startup the pipe will announce it's UUID to the console.

For example, given pipe with id "[email protected]":

[ "[email protected]", "x", "y", "if (x == 'shout') return [ x, y.toUpperCase() ]; return [x,y]"]

Will cause it to filter messages of the form:

[ "shout", "I like cheese!"] -> [ "shout, "I LIKE CHEESE!" ]

and [ "say", "I like cheese!" ] -> [ "say", "I like cheese!" ]

These transformations can be arbitrary, but will send a value for each message even if that value is 'undefined'.