noflo - npm Package Versions

0.5.15 (November 26th 2015)

• Support for scoped NPM packages

0.5.14 (September 25th 2015)

• EcmaScript 6 support in Component Loader
• Node.js 4.x compatibility (setSource requires components/ directory to exist in base directory to work)

0.5.13 (April 22nd 2015)

• Custom componentloader support when cache mode is enabled
• Optional support for coffee-cache when using --cache

0.5.12 (April 19th 2015)

• Add support for io.js
• Add componentName property for components telling the component name
• Socket events now include edge metadata
• Node.js: component list can be cached for faster start-up time. Cache file is stored in $BASEDIR/.noflo.json

0.5.11 (October 23rd 2014)

• On Node.js ComponentLoader setSource now loads components virtually from <baseDir>/components to support relative module loading
• Subgraphs don't get unattached ports implicitly exported any longer. Register in/outports in the graph to make them available from the outside
• Added safeties for restarted networks to WirePattern

0.5.10 (October 23rd 2014)

• Port names are now validated to only contain lowercase alphanumeric characters or underscores
• ComponentLoader.load method now calls its callback with the Node.js style error, instance signature to allow catching component loading issues
• Graph merging support via the graph journal
• getSource now returns correct type for graphs
• Subgraph networks are started when the main network starts, instead of automatically on their own timing. As a fallback they will also start when any of their ports receives a connect
• Networks can now be stopped and restarted at will using the stop and start methods
• The running state of a NoFlo network can be now queried with the isRunning method
• NoFlo networks support FBP protocol debugging via the setDebug and getDebug methods
• Ports.add is now chainable
• The start port was removed from subgraphs

These changes mean that in situations where a subgraph is used standalone without a network around it, you need to call component.start() manually. This is typical especially in unit tests.

0.5.9 (August 5th 2014)

• Hotfix reverting backwards-incompatible changes in subgraph loading, see #229.

0.5.8 (August 4th 2014)

• Fixed several issues in connections and data synchronization
• Updated read-installed to the latest version
• Updated JSON Schema for NoFlo graph definition format
• Low-level functions to add and remove graph inports at run-time, see #242
• Fixes for default port values and IIPs in subgraphs.
• Added dropInput option for WirePattern to drop premature data while parameters not yet received. See #239
• Addressable ports support in WirePattern. See details.

0.5.7 (July 23rd 2014)

• Ports now default to not required. Set the port option required: true the port needs to be connected in order for the component to work
• MultiError pattern is enabled by default when using WirePattern and supports forwardGroups option for error packets.
• WirePattern components now deal more consistently with groups and disconnect events

0.5.6 (June 23rd 2014)

• Custom icon support for subgraphs via the icon key in graph properties
• Parameter support for WirePattern components, allowing them to have configuration parameters that need to be set only once. Example:

component = new noflo.Component
component.inPorts.add 'path',
  datatype: 'string'
  required: true
component.inPorts.add 'delay',
  datatype: 'int'
  required: false
component.inPorts.add 'line',
  datatype: 'string'
component.inPorts.add 'repeat',
  datatype: 'int'
component.outPorts.add 'out',
  datatype: 'object'
component.outPorts.add 'error',
  datatype: 'object'

noflo.helpers.WirePattern component,
  in: ['line', 'repeat']
  out: 'out'
  params: ['path', 'delay']
  async: true
, (data, groups, out, callback) ->
  path = component.params.path
  delay = if component.params.delay then component.params.delay else 0
  doSomeThing path, delay, data.line, data.repeat, (err, res) ->
    return callback err if err
    out.send res
    callback()