element-behaviors

Similar but different, I really dig the nice spatial/3d webcomponent https://Lume.io 's ECS / behavior system. Standalone library, works for anything. https://github.com/lume/element-behaviors Here, the presence of an attribute signals behavior. With element-behaviors, has= attribute is used to say what behavior classes to apply. Different paths but doesn't seem super dissimilar end result. I feel like web-directive giving a simple callback leaves a lot to the developer, where-as element-behaviors API surface tries to parallel WebComponents, which is familiar & has lots of nice understandable lifecycle builtin.

I'd like to know your view about element behaviors That's not my repo, is a friend's repo

FWIW, Solid has been for some time under consideration for gradually untangling state in this project. Another library I’ve explored is element-behaviors[1], a Solid/custom element-based Entity Component System, which I think could be a good model for the project. Regardless of what tech I pull in, I’m sure I’ll be sharing insights eventually! 1: https://github.com/lume/element-behaviors