Previously would return the wrong expression for export {} statements that were directly adjacent to another object expression.

Merge the var and ref replacement and the import export traversal into single passes.

The key is here to make the node functions parametrized, so that depending on the underlying AST system different nodes can be created by the same transform.

Since babel.js has a bunch of circular imports it has weird importing specific code that checks if modules have been already initialized. We introduce a method called bulletProofNamespace() which helps us to adjust these error checking codes such that they work in split bundles.

Previously some weirdly formatted es modules from esm servers would not be categorized correctly.

Issue that happens if a local variable in a module has the same name as its exported alias, which the transformed code previously would cause to be overridden. This only works with the babel transform for now.

partitioned breakpoints also have breakpoints, but it does not really make sense to display the breakpoint control for them.

Partitioned policies are synthesized, and any override by definition, will revoke the splitting. Therefore it does not make sense to extend the existing master via `applyConfiguration()`

Saves up to 40% in performance. The initial application is skipped in favor of just directly passing the style props to the morph constructor.

Conflicting properties such as width, height, extent or textString, value and textAndAttributes are prioritized and weeded out during synthesization in order to avoid confusing behavior.

Previously the check would give incorrect results when nested breakpoints where being applied. A nested breakpoint is a breakpoint defined by a master that was *itself* reached by a breakpoint.

…flag

Replaces old and not very well working control flows with a more sophisticated approach to determining sizing behavior of a styled morph within the context of various layouts.
According to the identified sizing behavior, the extent is applied in varying fashions. Also previously accidental re-execution of layouts would happen due to policies applying themselves, which lead to inefficient layout applications overall. This is now prevented with a meta flag.

Previously some layout applications, including text layout, would cause extent, height or width properies in style policies to no longer apply, although not warranted.

Previous code would always loop for a very large array of CSS rules. The new approach just remembers where the rule is stored and directly deletes it, avoiding the search entirely.