@jakelazaroff @thomasreggi

No #HTMLImports for us, I guess... 🥺

@westbrook @davatron5000 @stubbornella This proposal reminds me a lot of my #HtmlFragments investigation a lot while back (albeit with a very different use case in mind).

https://blog.dwac.dev/posts/html-fragments/

I wonder if there is a potential path for this proposal which is less "Vue in the browser" and more "a primitive SFC format which frameworks can compile to". I wonder if this could solve multiple problems:

1. #SSR small fragments of #HTML after page load.
2. Vertical slice of separation of concerns for a component.
3. Import module format (like #HtmlImports or #HtmlModules).
4. Lazy loading a component and its styles without requiring CSS-in-JS.

Kind of a smorgasbord of requirements but I can see value in the right primitive here.

A Simpler HTML-over-the-Wire - Devel without a Cause

Is it possible to build an HTML-over-the-wire application with only native web technologies? See how far can we go with zero custom tooling, and how the web specification can change to support it.