Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

noflo

Package Overview
Dependencies
Maintainers
1
Versions
91
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

noflo - npm Package Versions

1
10

0.7.0

Diff

Changelog

Source

0.7.0 (March 31st 2016)

  • Switched component discovery and caching from read-installed to FBP manifest. fbp.json files can be generated using noflo-cache-preheat. This also changes behavior related to components or graphs in custom locations. The fbp-manifest tool only finds them from the default components/ and graphs/ subdirectories of the project base directory.
  • Component Loader listComponents can now return errors as first callback argument
  • Control ports don't receive bracket IPs, only data
  • NoFlo's InternalSocket now always handles information packets as IP Objects, with conversion to/from legacy packet events done automatically. Use socket.on('ip', function (ip) {}) to receive IP object
bergie
published 0.6.1 •

Changelog

Source

0.6.1 (March 30th 2016)

  • NoFlo's IP Objects are now available via noflo.IP
bergie
published 0.6.0 •

Changelog

Source

0.6.0 (March 29th 2016)

  • Removed the noflo executable in favor of noflo-nodejs
  • NoFlo createNetwork and loadFile methods can return errors as the first callback argument
  • New IP Objects feature allowing bundling and handling of groups and packet data together
  • New option to enable cloning of packets when sending to multiple outbound connections
  • New Process API which replaces WirePattern and makes NoFlo component programming closer to Classical FBP
  • Graph-level request isolation via IP.scope property
  • Removed the deprecated LoggingComponent baseclass
bergie
published 0.5.22 •

bergie
published 0.5.21 •

Changelog

Source

0.5.21 (December 3rd 2015)

  • Made NoFlo component cache keep Component Loader paths also relative
bergie
published 0.5.20 •

Changelog

Source

0.5.20 (December 2nd 2015)

  • NoFlo network instances now default to debug mode, meaning that errors thrown by components are available via the process-error event
  • If there are no listeners for the network process-error events or socket error event, then they are thrown
  • This change of behavior fixes issues with stale state in WirePattern networks caused by downstream exceptions
  • Debug mode can be disabled with network.setDebug(false)
bergie
published 0.5.19 •

bergie
published 0.5.18 •

Changelog

Source

0.5.18 (November 30th 2015)

  • Make NoFlo component cache paths relative to project root
bergie
published 0.5.17 •

Changelog

Source

0.5.17 (November 27th 2015)

  • Added a new noflo-cache-preheat tool that can be used for improving start-up times in Node.js projects with large lists of dependencies. Can be used as a postinstall script
bergie
published 0.5.16 •

Changelog

Source

0.5.16 (November 27th 2015)

  • Update the read-installed package to support scoped dependencies
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc