xible - npm Package Versions

[0.8.0][] - 2017-09-10

Added

• Introduction of type definitions for inputs and outputs. This allows types to extend other types and provide custom colors for those types. (#17)

• Added object.* nodes to replace the document.* nodes.

Changed

• document.* nodes are now deprecated in favor object.*.

• Registry actions such as xiblepm nodepack install use the proper OS dependent 'tmp' directory. (#33)

Removed

• log.console node is now removed, after it was deprecated in favor of console.log. (#27)

[0.7.0][] - 2017-08-20

Added

• Flows can be started/stopped and deleted using the cli. See the xible cli documentation for more information. (#18)

• The xible command line interface supports the 'config' context just like xiblepm. (#22)

• console.log, console.error and console.clear nodes are now included in XIBLE. log.console is deprecated and will be removed in a future release. (#27)

Changed

• xiblepm flow remove is deprecated in favor of xible flow delete.

• The command line interface tools xible & xiblepm are now stored in ./bin.

• The document.assign node only callbacks once when multiple documents are hooked up to the 'document' input.

• Callbacks from nodes in response to output.on('trigger') resulting from a input.getValues() call can now only be called back once. An error is thrown if called multiple times.

• Direct mode can now be enabled/disabled through the settings. It is disabled by default. (#26)

Fixed

• Resizing the editor to only narrowly fit the cpu/mem/delay charts no longer toggles the scrollbar in- and out of view. (#11)

• Publishing flows to the registry no longer includes the vault data (#25)

[0.6.0][] - 2017-06-09

Added

• Node inputs now have a string value assignsOutputType that allows the given output to be assigned the same type as the input. See the node structure documentation for more information.

• The default zoomstate of a flow in the editor can be changed through the settings. The value is stored in the configuration file as editor.viewstate.zoomstateonopen.

• The maximum amount of statuses visible on any node in the editor can be changed through the settings. The value is stored in the configuration file as editor.nodes.statuses.max. (#13)

• A flow saves some performance metrics in the timing object. This object is only available on flows in the main thread.

Changed

• xible-wrapper is now fetched from npm. It used to be distributed within the xible package itself.

• All xiblepm commands deliver the user-auth-token header to the registry, if the user is logged in. Previously, the user token was only sent for publish commands.

[0.5.0][] - 2017-06-03

Added

• All of the command line xiblepm flow context functions now work. This means that you can install flows from the registry, and publish flows to the registry. See the xiblepm documentation for more information.

Fixed

• Setting an output to global in the editor correctly updates the corresponding inputs within a newly created flow. (#15)

[0.4.1][] - 2017-05-14

Fixed

• Installing nodepacks through the editor or via xiblepm nodepack install now works on Windows. (#14)

[0.4.0][] - 2017-04-30

Added

• Flows can be initialized at different levels, allowing for a faster on-demand start. See Settings/Flows in your XIBLE installation for more details.

• The editor contains a link to the XIBLE docs.

• Command-line xible service options to run XIBLE through systemctl/systemd.

• LICENSE.md file.

Changed

• eslint/airbnb is now the default code style. For the time being, editor/ is ignored from the linter.

• The runnable state of a flow is better synchronized with the editor. If a flow is not runnable, the deploy and start buttons are unavailable. Intermediate state changes reflect directly in the editor.

• The status of a flow is now contained in a single state parameter, instead of relying on indivual parameters for starting, started, stopped, etc.

Fixed

• xiblepm nodepack install returns the correct exit code if nodepack.install() fails.

[0.3.1][] - 2017-04-19

Fixed

• Config module failed to create new config.json upon fresh installation.