#HydroActive supports deferring upgrade / lifecycle hooks until the component is interacted with, solve load ordering so your dependencies are always upgraded, and manages dependencies on components so they are hydrated exactly when they need to be and no earlier.
Cool to see #MDN exploring a unique #frontend architecture which better meets their needs.
https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/
A lot of the core ideas here are stuff I've been trying to formalize in #HydroActive and #rules_prerender. Islands of reactivity on a mostly static page and driving resource loading by what gets rendered are both key features most FE systems lack.
@hawkticehurst This is very interesting. I don't think I'm sold on an `x-signal` custom element (auto coercion and reliance on `innerHTML` seem sketchy to me), but it's a unique concept to explore for sure.
If it's interesting to you, I'm doing something not too dissimilar with #HydroActive. It's not quite defining state in HTML like you are, but it does focus on reading initial values from pre-rendered HTML with signals as a reactivity mechanism.
Just released v0.1.7 of #HydroActive with the main new feature being support of the "On-Demand Definitions" community protocol I recently proposed. If you're interested to try it out, this is an easy way to give it a shot.
https://github.com/dgp1130/HydroActive/releases/tag/releases%2F0.1.7
https://github.com/webcomponents-cg/community-protocols/pull/67
Just published #HydroActive v0.1.4 with #ShadowDOM support!
https://github.com/dgp1130/HydroActive/releases/tag/releases%2F0.1.4
Now you can call `host.shadow.query('...')` to easily scope a query to the shadow root of an element.
I had been hoping to spend some time this weekend on #HydroActive, but #Akuma is just too much fun right now.
What even is #hydration?
I just published a new video update on #HydroActive exploring exactly what the term means, what problems you encounter when you hydrate with plain #WebComponents and how HydroActive can help with those problems.
I also give an overview of the `defer-hydration` community protocol and how we can use it provide a common hydration interface.
Recorded another video for #HydroActive today! This one will be focused on what exactly #hydration actually means and how HydroActive helps you solve some key problems with it.
I think the audio should come out better this time, so it's hope it works out 🤞.
New release of #HydroActive re-works some of the DOM access APIs and improves overall hydration support with more comprehensive examples.
https://github.com/dgp1130/HydroActive/releases/tag/releases%2F0.1.1
My next milestone is put together another video which walks through the changes and some of the design decisions which went into hydration and the weird nuances it transparently solves for you in ways you would never notice as a user. Very interesting discussion coming! 😁
Published: New #YouTube video on #HydroActive where I:
* (re)introduce what HydroActive is (a webcomponent library for adding hydration and reactivity to primarily server-side rendered content)
* discuss the problems it's attempting to solve
* explain the core design principles behind the project
* demo some basic components and use cases
https://youtu.be/kTDgjF4a_oU?si=_EKTTgt6mzVyCMjg
While this is retreading some old ground from my previous video, the goal here is to kick off a series of (hopefully shorter) videos on specific concepts in HydroActive and how it evolves over time. Stay tuned for more content in the future!
Doug Parker 🕸️
