A components framework based on <template>

[yuval-a]

I recently released a framework I’ve been working on - that implements a lot of what is described in this proposal (which I only encountered just now)

https://github.com/yuval-a/Sprout

Mine has a “development environment” and a “compiler script”
But the “compiled version” does use elements to encapsulate components logic.

The framework rely on what it calls “State Attributes” - attributes on elements inside the component template with values starting with a $ - the runtime creates a binding between the attribute node values of a “rendered” component elements and the values in a State object thus enabling “state management” and “reactivity”

A “rendered” element is a custom element, and the runtime logic is a “ReactiveElement” class that extends HTMLElement classes - adding and handling those features.