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

23
10

1.4.3

Diff

Changelog

Source

1.4.3 (December 10th 2020)

  • Improved inport and outport options TypeScript definitions
bergie
published 1.4.2 •

Changelog

Source

1.4.2 (December 10th 2020)

  • Made Component and Network option TypeScript definitions easier to extend when subclassing
bergie
published 1.4.1 •

Changelog

Source

1.4.1 (December 10th 2020)

  • The asPromise function (promisified version of noflo.asCallback) now ships with the correct type definition
bergie
published 1.4.0 •

Changelog

Source

1.4.0 (December 10th 2020)

  • Asynchronous NoFlo methods (like createNetwork and network.start) now return Promises. Callbacks are still supported as a compatibility layer.
  • Component setUp and tearDown can now return a Promise instead of calling the supplied callback
  • Component processing function can now return a Promise instead of calling sendDone or done (if the Promise resolves to a value, it will be sent out)
  • NoFlo now ships with TypeScript type definitions
  • The src/lib folder contains NoFlo as JavaScript Modules. lib is the CommonJS version
  • The CommonJS version of NoFlo is now shipped as modern ES2020 instead of babelized ES5. Use Babel in your project if you need compatibility with old JS runtimes
bergie
published 1.3.0 •

Changelog

Source

1.3.0 (November 23rd 2020)

  • NoFlo createNetwork and asCallback now accept a flowtrace option to pass a Flowtrace instance for retroactive debugging. Example:
const { Flowtrace } = require('flowtrace');
const tracer = new Flowtrace();
noflo.createNetwork(myGraph, {
  flowtrace: tracer,
}, (err, network) => {
  // ...
  console.log(tracer.toJSON());
});
  • NoFlo createNetwork now accepts componentLoader and baseDir via options. Passing them via Graph properties is deprecated
  • NoFlo createNetwork now defaults to the non-legacy "network drives graph" mode
  • NoFlo createNetwork now only supports the graph, options, callback signature, no options given in some other order
  • noflo.Network interface has been removed. Use createNetwork to instantiate networks
  • CoffeeScript is no longer bundled with NoFlo. Install the CoffeeScript compiler in your project if you need to be able to load CoffeeScript components
bergie
published 1.2.7 •

Changelog

Source

1.2.7 (November 13th 2020)

  • Added safeties against trying to load a falsy graph in asCallback
  • Added safeties against trying to load unnamed components
bergie
published 1.2.6 •

Changelog

Source

1.2.6 (September 24th 2020)

  • Fixed an issue with getSource on Node.js
bergie
published 1.2.5 •

Changelog

Source

1.2.5 (September 24th 2020)

  • Fixed an issue with deployment automation
bergie
published 1.2.4 •

Changelog

Source

1.2.4 (September 24th 2020)

  • ComponentLoader getSource now returns also component specs when available
bergie
published 1.2.3 •

Changelog

Source

1.2.3 (September 17th 2020)

  • TypeScript components loaded on Node.js now target modern ES6
23
10
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