@marko/runtime-tags@6.3.11

Patch Changes

• #3441 eed9e39 Thanks @DylanPiercey! - Preserve the original server rendering error when a stream aborts while flushing an asynchronous placeholder.

• #3438 a86e699 Thanks @DylanPiercey! - Fix a dynamic tag name built with ?? (such as <const/Tag = input.tag ?? Fallback/> used as <${Tag}/>) being statically collapsed to the right-hand operand in the DOM output, so the left operand was ignored and the wrong tag rendered.

• #3439 2827414 Thanks @DylanPiercey! - Fix Marko 6 files in a mixed (interop) project being misclassified as Class API, and failing to compile, when their only distinguishing feature is the Tags-only <show> core tag. <show> is now recognized as a Tags API marker during feature detection.

• #3436 4a27f46 Thanks @DylanPiercey! - Fix native tag attributes whose names collide with Object.prototype members (such as toString, valueOf, hasOwnProperty, or constructor) being silently dropped from the output or raising a spurious is not a valid attribute error.

• #3443 88cfa70 Thanks @DylanPiercey! - Simplify grouping parameter-based serialization reasons during compilation.

• #3440 e95cf17 Thanks @DylanPiercey! - Fix resumed nested branches attaching to the wrong parent when one marker closes multiple branches.

• #3442 650ed36 Thanks @DylanPiercey! - Fix a top-level return in a <script> tag short-circuiting the effects of following sibling <script>/<lifecycle> tags in the same section (they compile into a single shared effect). A script whose body has a top-level return is now kept as an isolated call so the return stays local.

• #3438 8ed981a Thanks @DylanPiercey! - Fix a lone spread that resolves to null, undefined, or false on a controllable element (such as <input ...maybeNull>) crashing the render with a TypeError instead of producing an attribute-less element. Both the server and client attribute helpers now guard the controllable path against a nullish spread.