Added initial support for components written in TypeScript. Requires the typescript module to be installed
NoFlo ComponentLoader can now tell the supported programming languages with the getLanguages method
Components written with setSource now return the original untranspiled source code with getSource also on Node.js

1.2.1

Diff

bergie

published 1.2.1 • 4 years ago

Changelog

Source

1.2.1 (September 16th 2020)

Added better error messages when trying to write to a non-existing outport in a component
Added support for loading subgraph components even if they come from a different version of fbp-graph

1.2.0

Diff

bergie

published 1.2.0 • 4 years ago

Changelog

Source

1.2.0 (August 28th 2020)

Ported NoFlo from CoffeeScript to ES6
Deprecated constructing networks with new noflo.Network. Use noflo.createNetwork instead, with the following options available:
- subscribeGraph: true: Uses LegacyNetwork which modifies network topology based on changes in graph. This can cause some types of errors to be silent.
- subscribeGraph: false: Uses Network: network topology can be changed with network's methods (addNode, removeEdge, etc) and will be also written to the graph. For backwards compatibility reasons, subscribeGraph defaults to true. Adapt your applications to use false instead and start utilizing Network methods for any changes to a running graph.
Added support for a more standard noflo.createNetwork(graph, options, callback) signature, with backwards compatibility for the legacy noflo.createNetwork(graph, callback, options) signature
Removed support for noflo.WirePattern. WirePattern has been deprecated since 1.0, and all code using it should be migrated to the latest Process API
Removed support for changing component icon and description statically (on class level) at run-time (i.e. ComponentName::icon = 'new-icon'). Component icon and description should be set in class constructor or in getComponent instead. Changing icon and description for a specific instance (process) is not affected and is fully supported
Added optional networkCallback option for noflo.asCallback to provide access to the network instance for debugging purposes

1.1.3

Diff

bergie

published 1.1.3 • 7 years ago

Changelog

Source

1.1.3 (April 12th 2018)

Fixed issue with custom component loaders on Node.js

1.1.2

Diff

bergie

published 1.1.2 • 7 years ago

Changelog

Source

1.1.2 (March 24th 2018)

Improved detection of when network finishes to not stop synchronous networks too early

1.1.1

Diff

bergie

published 1.1.1 • 7 years ago

Changelog

Source

1.1.1 (February 19th 2018)

Fixed noflo.asComponent handling of functions that return a NULL

1.1.0

Diff

bergie

published 1.1.0 • 7 years ago

Changelog

Source

1.1.0 (February 19th 2018)

Added noflo.asComponent for easy mapping of JavaScript functions into NoFlo components. Each argument will get its own inport with the name of the argument, and output is handled based on the type of function being wrapped:
- Regular synchronous functions: return value gets sent to out. Thrown errors get sent to error
- Functions returning a Promise: resolved promises get sent to out, rejected promises to error
- Functions taking a Node.js style asynchronous callback: err argument to callback gets sent to error, result gets sent to out

1.0.3

Diff

bergie

published 1.0.3 • 7 years ago

Changelog

Source

1.0.3 (November 24th 2017)

Added support for running arbitrary NoFlo graphs via noflo.asCallback. You can call this function now with either a component name, or a noflo.Graph instance

1.0.2

Diff

bergie

published 1.0.2 • 7 years ago

Changelog

Source

1.0.2 (November 17th 2017)

Fix sub-subgraph identification in network events

1.0.1

Diff

bergie

published 1.0.1 • 7 years ago

Changelog

Source

1.0.1 (November 13th 2017)

Subgraphs re-activate themselves when receiving new packets after they've completed running
Subgraphs now use the JavaScript implementation of Graph component also on Node.js
NoFlo setSource on Node.js no longer transpiles ES6 sources using Babel. All supported Node.js versions should run ES6 without issues

…

noflo - npm Package Versions

1.2.2

.css-1z04cui{margin-bottom:var(--chakra-space-4);font-size:var(--chakra-fontSizes-md);}1.2.2 (September 17th 2020)

1.2.1

1.2.1 (September 16th 2020)

1.2.0

1.2.0 (August 28th 2020)

1.1.3

1.1.3 (April 12th 2018)

1.1.2

1.1.2 (March 24th 2018)

1.1.1

1.1.1 (February 19th 2018)

1.1.0

1.1.0 (February 19th 2018)

1.0.3

1.0.3 (November 24th 2017)

1.0.2

1.0.2 (November 17th 2017)

1.0.1

1.0.1 (November 13th 2017)

1.2.2 (September 17th 2020)