January 22nd, 2016

We are proud to announce LaxarJS v1.2.0

The overall goal of this release is to allow for better live inspection during LaxarJS application development. To this end, the tooling API of LaxarJS core was extended.

This release introduces the following new features:

  • New tooling support for page inspection (#247, #248).

  • Extensive manual on visibility events. This powerful advanced feature allows widgets to act based on their visibility to the user, and to control visibility of nested widgets, without direct API-based interaction (#244).

Apart from this, several fixes and tweaks were introduced, mainly aiming towards better testability (#243, #242, #241, #240).

Interactive Page Inspection

To showcase the new LaxarJS tooling capabilities, the laxar-developer-tools-widget (released as v2.0.0) was extended with powerful graphical inspection capabilities. It now visualizes activities, widgets and compositions of the current page as well as their connections through standard event patterns (actions, flags and resources). This new visualization has also been used to illustrate the LaxarJS shop-demo tutorial:

You can even try it out in the online shop-demo. Use the Developer Tools button in the bottom right corner, then open the page tab.

While nesting relationships are detected automatically, a little meta data must be added to widget descriptors, as documented in the laxar-developer-tools-widget usage information. All standard LaxarJS widgets have been extended with the new meta information, and may serve as a reference.

Note that tooling APIs is always considered unstable, in contrast to the other APIs which follow semver. If a breaking change should be introduced however, you may always expect dependent components (laxar-mocks, laxar-developer-tools-widget) to be available in a compatible version.


The companion widget testing library laxar-mocks was promoted to v1.0.0 and contains the following changes:

  • fixed issues with resolution of promises and promise chains (#18, #19, #20, #21)

  • improved documentation (#17)

Using the laxar-mocks library is now the recommended way to create widget tests. The old built-in testbed will be discontinued with LaxarJS v2.0.0. The standard widgets have already been upgraded to using laxar-mocks.

The companion library laxar-patterns was also upgraded to v1.2.0 and contains the following changes:

  • Support for laxar-mocks was added. This allows laxar-patterns to be used in widgets that do not use AngularJS, without sacrificing testability.