- Now using the community version of NoFlo UI by default
- Options are now passed to the preStart callback when used as a library
- Fixed graph properties when auto-saving
- Updated to the new Promise-based NoFlo 1.4 APIs
- Updated to the new built-in Flowtrace functionality in NoFlo 1.3.0
- Compatibility with the TypeScript version of fbp-graph
- Added support for WebRTC protocol as an alternative to WebSockets
- Graphs created by fbp-spec for test execution purposes no longer get auto-saved
- Specs sent by IDE via
setSourceare no also auto-saved
- Graph names are used without namespace when auto-saving
- Added auto-saving support for components written in TypeScript
- Modified SSL warnings to be written to STDOUT instead of STDERR to improve operation with fbp-spec
- Switched to the NoFlo 1.2 "network drives graph" mode for more accurate error handling
- Added support for discovering the noflo-nodejs runtime via mDNS
Bugfixes:
- noflo-nodejs library mode also subscribes to runtime now, so that
autoSavemode works
New features:
- noflo-nodejs is now much easier to embed in existing Node.js applications as a library
- Added
--auto-saveoption to enable saving edited graphs and components to disk automatically
New features:
- Added
--openoption to control whether to open the runtime in user's IDE when started. Defaults totrue.
New features:
- Changed configuration file
flowhub.jsonto be automatically saved from command-line arguments, persisting settings like runtime ID and secret between runs - Added support for encrypted WebSockets with
--tls-keyand--tls-certoptions - When Flowtracing is enabled with the
--traceoption, uncaught exceptions also trigger the trace to be saved - Uncaught exceptions are now printed in a more readable format, with a truncated stack trace
- The runtime registry URL can now be configured with the
--registryoption - Runtime registry pinging can be disabled with
--registry-ping=0 - If running on a desktop machine, the runtime will be automatically opened in user's default browser
- Added compatibility with FBP Protocol version 0.7
Removal of deprecated features:
- Removed deprecated
noflo-nodejs-inittool - Removed deprecated
--registeroption. Your runtime can be registered with Flowhub by opening it there
Internal changes:
- Ported noflo-nodejs from CoffeeScript to ES6
- Compatibility with NoFlo 1.x
Deprecations
noflo-nodejs --registeris deprecated, in favor offlowhub-registry-registeror accessing the live URL. Support will be removed in 0.9.x.
Breaking changes
- Registration with Flowhub is no longer done by default. Must be enabled using
--register true
Additions
- All options/features are now available on
noflo-nodejs, sonoflo-nodejs-initcan be skipped - Support pinging Flowhub registry using option
--ping trueor envvarNOFLO_RUNTIME_PING=true - Support specifying runtime id using
NOFLO_RUNTIME_IDenvvar - Support passing runtime
idin live URLs - Now gives a warning when no
secretis passed, since will not be able to connect over WebSocket (no permissions) - Supports Flowhub "Edit as Project" feature, by passing component namespace via FBP protocol
Bugfixes:
- Fixed --version being called --0.8.x
- Fixed --permissions not having effect on commandline
- Updated to NoFlo 0.8.x
- Updated to NoFlo 0.7.x
- Support for Flowtrace when using
--traceoption. - For long-running programs, flowtrace dumps can be triggered via
SIGUSR2Unix signal
- Implements FBP protocol version 0.5. Use of a runtime
secretis now enforced - Support for
--debug,--verboseand--capture-exceptionflags to tune logging behavior. - Support for
--hostand--portoptions, with defaults. Port also respects PORT envvar. - Support for multiple levels of
permissionsbased on provided secret and configured - Support for a
--batchmode, where process exists when graph stops. Intended to replace thenofloexecutable - Several FBP protocol fixes from noflo-runtime-base 0.5.x. Should now work with fbp-spec
- Registration with Flowhub registry is optional, just warning
- ...