xible - npm Package Versions

[0.29.3][] - 2024-09-26

Fixed

• Bumped version on 'http' nodepack which XIBLE ships with by default.

• Bumped versions on several express related NPM dependencies to fix security vulnerabilities.

[0.29.2][] - 2024-07-20

Fixed

• Rolled back strip-ansi package to version 6 for CommonJS require() compatibility.

[0.29.1][] - 2024-07-20

Changed

• Bumped versions on several nodepacks which XIBLE ships with by default.

• Bumped versions on several NPM dependencies.

Fixed

• The publish-flow button was visible and clickable even though the setting to allow publishing flows was disabled.

[0.29.0][] - 2024-04-08

Added

• Introduced /api/flows/<flow-name>/instances/<flow-instance-id> endpoint to get statuses of a specific flow instance.

Fixed

• Better handling on broken worker IPC's when trying to stop the worker from the main process.

[0.28.0][] - 2024-03-11

Added

• Support for different base href's. This allows XIBLE to be hosted from subpaths behind a reverse proxy for example. Set the BASE_HREF environment variable accordingly to ensure XIBLE correctly handles the base path.

[0.27.0][] - 2024-02-26

Added

• Support for different stores. This makes it possible to store flows, flow-states, and the vault outside the filesystem. The first supported store besides FileStore is PgStore for PostgreSQL. You can use the store by providing --flow-store-type=PgStore and --connection-string=<connection-string> parameters when starting XIBLE. (#94)

Changed

• Upgrade Cypress for E2E testing.

• Updated minumum Node.JS version to 20.

Fixed

• The pattern validation for the name of a new flow in the browser was not escaped properly.

[0.26.0][] - 2021-05-19

Added

• It is now possible to xiblepm flow install <user>/<flow> instead of xiblepm flow install <flow> --publish-user-name=<user>. xiblepm flow search returns a list in the same format.

• Whenever a nodepack is under development and the package.json name attribute does not start with 'xible-np-' or 'xible-nodepack-', a warning is thrown, indicating that the nodepack cannot be published to the registry.

• The CLI command xiblepm flow delete <flow-name> has been added to delete a flow which is published to the registry. The documentation has been updated.

• The UI has an option to publish flows from the 'Flows' page. This acts similarly as the command line xiblepm flow publish <flow-name>.

• It is now possible to navigate the node selector within the editor using the up and down keys to select different nodes, and the space key to insert a node.

Changed

• The .xiblerc.json file location is now configurable in the config.json and as a result through the xible config command.

Fixed

• Calling node.getData() on a node that has no dataStructure, would throw.

[0.25.0][] - 2021-05-16

Changed

• Flows are now stored per user. This means that the registry can hold multiple flows by the same name, but published by different users. All functionality has been updated to reflect this change. This includes the UI and the cli commands such as xiblepm flow install.

[0.24.0][] - 2021-05-12

Added

• Within the structure.json of a node, developers can now configure the input data fields using the dataStructure object, instead of creating a separate editor/index.htm. This improves development time for new nodes by a fair bit. If an editor/index.htm is present, it will overrule any configured dataStructure within the structure.json. (#95)

• A new convenience method node.getData(dataName, state) to fetch all data for a data field, including related inputs if so configured. This behaves similarly as a combination of fetching data through NODE.data.x and NODE.getInputByName(x).getValues(). node.getData() is the new preferred method of fetching data. (#95)

Changed

• nodeIo.isConnected() actually returns a boolean now, instead of the amount of connectors.

[0.23.2][] - 2021-05-05

Fixed

• Describe/help for a node, in the flow editor, was no longer visible. When a node was in focus, and the 'h' key was pressed, the help page would not show up. Similarly when clicking on the help button for that node.