Post

Extremely cursed: if you abuse Vue internals hard enough, you can build a component that "morphs" as either a Vapor component or a vdom component depending on the rendering style of the parent 🤪 Vue.js Playground

that's cool. maybe we can use this way to make universal compoents? 😝

well that was kinda the idea I had in mind with this little "experiment" 🤪 I'm a bit concerned about compat with component libs, and the cost of interop doing vdom -> vapor -> vdom 🤔 but that thing is *really* hacky. there are other ways to do it using undocumented exports from "vue" as well 😋

Maybe one way is to offer a compiler mode that generates both Vapor and vDom versions of the render code. But we still need to think about tree shaking.

I got lost in ADHD. So I stayed up late and found this post. It's quite rewarding 🤪. Oh, I remember your "loss closing tags" pull request. We haven't merged it yet, but thanks for your work!