xible - npm Package Versions

[0.19.0][] - 2020-07-11

Added

• You can now snap nodes in the editor to a grid. The setting is enabled by default. It can be toggled in the editor in the bottom left corner.

• Searching for a node in the node selector which contains a dash, no longer needs that dash supplied in the search input. For example, the search string 'appendstring' will find the node filesystem.file.append-string.

Fixed

• Support for NodeJS v14. (#85)

[0.18.1][] - 2020-04-13

Fixed

• Installing nodepacks from the registry failed.

[0.18.0][] - 2020-04-13

Added

• A nodepack view has been added which lists all the installed nodepacks and their nodes.

• Support for the command key in the editor on MacOS.

Fixed

• Vault path description in settings was incorrect.

[0.17.2][] - 2020-03-15

Fixed

• Wrapping of node names in the editor now works cross browser, instead of only in Chrome.

• Installing XIBLE on non-MacOS operating systems failed because of an older nested dependency in the filesystem nodepack.

[0.17.1][] - 2020-02-19

Fixed

• Chart labels are no longer overlapped by the chart itself. (#3)

• Removed browser feature check for HTML imports. (#84)

[0.17.0][] - 2019-04-06

Changed

• Starting flows from the 'flows' page triggers the same checks as the start button on the 'editor' page does. Existing instances can therefor be stopped and instance parameters can be provided.

• Improved node selector in editor. Node names are now wrapped for better readability.

[0.16.1][] - 2019-02-01

Fixed

• Various xible node cli commands are functioning again.

• The cli command xible node get <data> now properly fetches only the specified data field when that particular bit of data is stored in the vault.

[0.16.0][] - 2019-01-30

Added

• Some of the nodes that came with XIBLE by default have been moved to their own respective nodepacks. (#79)

• Several nodepacks are now installed by default when installing a fresh copy of XIBLE. (#78)

• When logging in on the registry using the xiblepm user login command, the user gets confirmed which user is now logged on, including the registry url. The same goes for adding a new account using xiblepm user add.

• The xiblepm nodepack publish command now informs the user of the published version, after completion. (#44)

• The UI now allows users to search and install flows from the registry. This feature can be found in the 'Flows' section of your XIBLE installation. (#20)

Changed

• The xible config list command now returns a human readable key-value list. The key nesting is identified by dots, much like json paths and how xible config set and xible config get already worked. A xible config json command has been added which sticks to the previous behaviour and simply prints the actual JSON (formatted) config. (#23)

Fixed

• Improved selection handling in the editor.

[0.15.0][] - 2018-10-27

Added

• The timing object for flow instances now also contains the createDate, initDate and startDate properties. These contain a Date.now() property for their respective dates. This allows you to track exactly when a flow instance was started.

• On the 'flows' view, you can now select a flow to view the details of that flow. This includes state, parameters, resource graphs and more.

• Use xiblepm nodepack init to create a default node structure. This is useful for starting the development of a new node within a nodepack. (#81)

• Unsupported browsers can now find exactly which features the browser is missing in a 'details' window.

• string.length node to find the length of all input strings combined.

• TypeDefs can be related to javascript constructors, so that it is now possible for XIBLE to filter input values based on the typeDef in the extends chain. The typeDef of a value can be set by assigning a typeDef to the constructor of that value using Node.setTypeDef(Constr, type). As a result, node inputs and outputs can now be connected as long as either side is in the extends chain of the other side. If an output is lower in the extends chain than the input, the values will be filtered to match at least the extends level of the input.

• Added a input.filter-type node to return values from a specific type only.

• The log in the editor can now be cleared using the "clear" button.

Changed

• Improved error handling. Throwing an error can now be intercepted by dedicated xible nodes (formerly xible.node.onerror). Using node.error(err, state) instead of simply throwing remains a valid use as it provides more details as to where the error originated. The xible.node.error and xible.node.onerror nodes have been renamed to xible.flow.instance.error and xible.flow.instance.on-error respectively. (#80)

• Errors thrown within a flow instance now show up in the editor. (#12)

Fixed

• When publishing a nodepack (which already exists), the package.json name attribute is now stripped of preceeding 'xible-np-' or 'xible-nodepack-' strings before matching it against the registry to see if the publisher is the same. Prior to this, the registry would return a http 403 which would show up as 'Unsuccessful statuscode returned' in the cli.

• When initially navigating to the flows overview and after that head over to the editor, the flows would show up empty. This is now fixed. (#77)

[0.14.0][] - 2018-07-29

Added

• It is now possible to specify the input string directly for the string.split node.

• Hovering a global input or output on a node in the editor, now visualizes the connections as if they were directly connected. (#39)

• Added the object.include-keys and object.exclude-keys nodes. These can be used to strip unwanted keys from objects.

• Added the input.filter-duplicates, input.length, input.for-each and input.map nodes.

• Added the compare.truthy and compare.falsy nodes to verify how objects evaluate in a boolean context.

• The string.template node now supports passing object keys as variables for string expansion.

• Added the input.object.filter-duplicates and input.object.group nodes. These allow duplication filtering and grouping based on an object key.

• Added the string.join node, which allows you to join multiple strings together. A separator can be introduced between the strings.

• Support for script type="module" in node editor contents. Note that these script elements are untouched when they are processed by the browser. Script elements that do not contain the type="module" directive will be evaluated like ever before, with the document argument attached to the shadow root and this referring to the node itself.

Changed

• XIBLE now throws an error if it is already running according to the PID file. Similarly, CLI commands which require that XIBLE is running will throw an error if that is not the case.

• The input.group node has been replaced by the input.concat node.

Fixed

• When viewing a node in help/describe mode, it now properly zooms/scales in Firefox. (#82)