I like what I'm seeing in Web Component technology, but it's not fully there for me yet. Suppose your base Design System is web components. Most Microfrontend

I like what I'm seeing in Web Component technology, but it's not fully there for me yet. Suppose your base Design System is web components. Most Microfrontend (MFE) teams will still pick up an off-the-shelf React, Vue, Angular, etc. But VDOM and web components don't always play nicely. If you have Parent-Child web components, specifically 1 parent with N-immediate children, React can't resolve this gracefully. Every render past the first breaks with Stencil. That's a pretty significant issue, because (very) common components like Select dropdowns are modeled as 1 parent with N immediate children. So you can't any longer stay in React's declarative model. The workaround (last comment in issue) has you writing imperative code to fix the problem. It has that "using D3 in React" vibe to it. It works, but it's not nearly as elegant as if you had, say, a React-based Design System (but then, of course, all your MFE teams must use React). https://github.com/ionic-team/stencil/issues/2259 https://github.com/ionic-team/stencil/issues/2259 Users have also reported the same analogous issue exists for using Web Components in Vue too, so it's not even a React-specific shortcoming. https://github.com/ionic-team/stencil/issues/2259#issuecomment-661086558 https://github.com/ionic-team/stencil/issues/2259#issuecomme...