noflo - npm Package Versions

0.4.1 (September 25th 2013)

• NoFlo components can now implement a shutdown method which is called when they're removed from a network
• Graphs can contain additional metadata in the properties key
• NoFlo networks have now a start and a stop method for starting and stopping execution

0.4.0 (July 31st 2013)

Browser support:

• The NoFlo engine has been made available client-side via the Component system
• New BDD tests written with Mocha that can be run on both browser and server

Changes to components:

• All components have been moved to various component libraries

Development tools:

• Grunt scaffold for easily creating NoFlo component packages including cross-platform test automation

File format support:

• NoFlo's internal FBP parser was removed in favor of the fbp package
• The display property of nodes in the JSON format was removed in favor of the more flexible metadata object

Internals:

• Support for renaming nodes in a NoFlo graph via the renameNode method
• Adding IIPs to a graph will now emit a addInitial event instead of an addEdge event
• Graph's removeEdge method allows specifying both ends of the connection to prevent ambiguity
• IIPs can now be removed using the removeInitial method, which fires a removeInitial event instead of removeEdge
• NoFlo Networks now support delayed starting
• The isBrowser method on the main NoFlo interface tells whether NoFlo is running under browser or Node.js
• Support for running under Node.js on Windows

0.3.4 (July 5th 2013)

Internals:

• New LoggingComponent base class for component libraries

0.3.3 (April 9th 2013)

Development:

• Build process was switched from Cake to Grunt
• NoFlo is no longer tested against Node.js 0.6

0.3.2 (April 9th 2013)

NoFlo internals:

• Ports now support optional type information, allowing editors to visualize compatible port types

  @inPorts =
    in: new noflo.ArrayPort 'object'
    times: new noflo.Port 'int'
  @outPorts =
    out: new noflo.Port 'string'
  

• NoFlo ComponentLoader is now able to register new components and graphs and update package.json files accordingly

  loader = new noflo.ComponentLoader __dirname
  loader.registerComponent 'myproject', 'SayHello', './components/SayHello.json', (err) ->
    console.error err if err
  

New libraries:

• noflo-test provides a framework for testing NoFlo components

0.3.1 (February 13th 2013)

NoFlo internals:

• The NoFlo .fbp parser now guards against recursion on inline subgraphs

• NoFlo subgraphs now inherit the directory context for component loading from the NoFlo process that loaded them

• Exported ports in NoFlo graphs are now supported also in NoFlo-generated JSON files

• Nodes in NoFlo graphs can now contain additional metadata to be used for visualization purposes. For example, in FBP format graphs:

  Read(ReadFile:foo) OUT -> IN Display(Output:foo)
  

  will cause both the Read and the Display node to contain a metadata.routes field with an array containing foo. Multiple routes can be specified by separating them with commas

New component libraries:

• noflo-filesystem provides advanced file system components
• noflo-github provides components for interacting with the GitHub service
• noflo-git provides components for Git revision control system
• noflo-oembed provides oEmbed protocol support
• noflo-redis provides Redis database components

0.3.0 (December 19th 2012)

User interface:

• NoFlo's web-based user interface has been moved to a separate noflo-ui repository

• The noflo shell command now uses STDOUT for debug output (when invoked with --debug) instead of STDERR

  • Events from subgraphs are also visible when the noflo command is used with the additional -s switch
  • Contents of packets are shown when the noflo command is used with the additional -v switch
  • Shell debug output is no colorized for easier reading

• DOT language output from NoFlo was made more comprehensive

• NoFlo graphs can now alias their internal ports to more user-friendly names when used as subgraphs. When aliases are used, the other free ports are not exposed via the Graph component. This works in both FBP and JSON formats:

  For FBP format graphs:

  EXPORT=INTERNALPROCESS.PORT:EXTERNALPORT
  

  For JSON format graphs:

  {
    "exports": [
      {
        "private": "INTERNALPROCESS.PORT",
        "public": "EXTERNALPORT"
      }
    ]
  }
  

NoFlo internals:

• All code was migrated from 4 spaces to 2 space indentation as recommended by CoffeeScript style guide. Our CI environment safeguards this via CoffeeLint
• Events emitted by ArrayPorts now contain the socket number as a second parameter
• Initial Information Packet sending was delayed by process.nextTick to ensure possible subgraphs are ready
• The debug flag was removed from NoFlo Network class, and the networks were made EventEmitters for more flexible monitoring
• The isSubgraph method tells whether a Component is a subgraph or a regular code component
• Subgraphs loaded directly by ComponentLoader no longer expose their graph port
• The addX methods of Graph now return the object that was added to the graph
• NoFlo networks now emit start and end events
• Component instances have the ID of the node available at the nodeId property
• Empty strings and other falsy values are now allowed as contents of Initial Information Packets

Changes to core components:

• ReadGroup now sends the group to a group outport, and original packet to out port
• GetObjectKey can now send packets that don't contain the specified key to a missed port instead of dropping them
• SetPropertyValue provides the group hierarchy received via its in port when sending packets out
• Kick can now optionally send out the packet it received via its data port when receiving a disconnect on the in port. Its out port is now an ArrayPort
• Concat only clears its buffers on disconnect when all inports have connected at least once
• SplitStr accepts both regular expressions (starting and ending with a /) and strings for splitting
• ReadDir and Stat are now AsyncComponents that can be throttled

New core components:

• MakeDir creates a directory at a given path
• DirName sends the directory name for a given file path
• CopyFile copies the file behind the path received via the source port to the path received via the destination port
• FilterPacket allows filtering packets by regular expressions sent to the regexp port. Non-matching packets are sent to the missed port
• FirstGroup allows you to limit group hierarchies of packets to a single level
• LastPacket sends the last packet it received when getting a disconnect to the inport
• MergeGroups collects grouped packets from its inports, and sends them out together once each inport has sent data with the same grouping
• SimplifyObject simplifies the object structures outputted by the CollectGroups component
• CountSum sums together numbers received from different inports and sends the total out
• SplitInSequence sends each packet to only one of its outports, going through them in sequence
• CollectUntilIdle collects packets it receives, waits a given time if there are new packets, and if not, sends them out

New component libraries:

• noflo-liquid provides Liquid Templating functionality
• noflo-markdown provides Markdown conversion
• noflo-diffbot provides access to the Diffbot screen-scraping service

0.2.0 (November 13th 2012)

The main change in 0.2 series was component packaging support and the fact that most component with external dependencies were moved to their own NPM packages:

• Message Queue components were moved to noflo-mq
• HTML parsing components were moved to noflo-html
• XML parsing components were moved to noflo-html
• YAML parsing components were moved to noflo-html
• Web Server components were moved to noflo-webserver
• CouchDB components were moved to noflo-couchdb
• BaseCamp API components were moved to noflo-basecamp
• Restful Metrics components were moved to noflo-restfulmetrics

To use the components, install the corresponding NPM package and change the component's name in your graph to include the package namespace. For example, yaml/ParseYaml for the ParseYaml component in the noflo-yaml package

User interface:

• The noflo command-line tool now has a new list command for listing components available for a given directory, for example: $ noflo list .

NoFlo internals:

• New ComponentLoader to support loading components and subgraphs to installed NPM modules
• NoFlo's own codebase was moved to direct requires making the NPM installation simpler
• daemon dependency was removed from NoFlo's command-line tools

Changes to core components:

• Merge only disconnects once all of its inports have disconnected
• Concat only disconnects once all of its inports have disconnected
• CompileString's in port is now an ArrayPort
• GroupByObjectKey also supports boolean values for the matched keys
• ReadDir disconnects after reading a directory

New core components:

• Drop allows explicitly dropping packets in a graph. The component performs no operations on the data it receives