Changelog

[0.0.44] — 2026-04-10

Fragment-returning components not registering correctly — when a component's render() returns a Fragment (e.g. to include a <head> block alongside the main element), data-newstack was being set on the Fragment vnode itself which gets dropped. setComponentMarker now resolves through Fragments, arrays, and <head> vnodes to stamp the attribute on the first real DOM element, so the component is found correctly by componentElements.
Event handlers not attached after Fragment re-renders — updateComponent was passing the Fragment vnode to patchElement, whose vnodeChildren would be [head-vnode, div-vnode] instead of the div's actual children. resolveToElementVNode now unwraps to the real element vnode so vnodeChildren aligns with DOM children and onclick handlers are wired correctly.

Full Changelog: newstack-v0.0.43...newstack-v0.0.44