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

noflo-lift

v0.0.12

Published

Lift Packets for Processing in NoFlo

Downloads

14

Readme

Lift Packets for Processing in NoFlo Build Status

In a NoFlo program, how the program processes data is more important than the data structure. It is evident in that most NoFlo programs expect a rather flat data structure of a series of packets enclosed in one or two levels of groups.

When your program expects a more complex data structure, it is useful to be able to extract a subset of the structure, do some work, and plug it right back into where it was extracted from. noflo-lift allows you to literally "lift" a subset of the data structure by providing a pattern object for further processing on just that one piece. It then accepts some data structure that noflo-lift would then insert back in place.

In Ports

noflo-lift accepts data via these ports:

IN

Any valid NoFlo data structure

PATTERN

A pattern is a path-like array denoting the group structure to extract. For instance, in XML schematics, if you have an incoming data structure:

<GroupA>
  <GroupB>
    <GroupC>
      <Data1/>
      <Data2/>
    </GroupC>
    <Data3/>
    <Data4/>
  </GroupB>
  <GroupD>
    <Data5/>
    <Data6/>
  </GroupD>
</GroupA>

And you want to extract just GroupC for processing, you would pass in, in JSON:

[ "GroupA", "GroupB", "GroupC" ]

RETURN

The processed data structure must be returned to this port to continue its journal through the OUT port. See the PROCESS out port for details.

CACHESIZE

noflo-lift does not have a cache limit as it expects you to finish processing on all opened requests. You may optionally set a cache size if you deal with asynchronous operations that may fail.

Out Ports

noflo-lift emits data via these ports:

OUT

The data structure that has been processed and plugged back in is emitted to this port.

PROCESS

The extracted data structure is emitted here. It is grouped at the top-level by a token, which must group the processed data structure on return to the RETURN in port.