@konnorrogers

@keithamus doesn't need to worry, too much... the Edge team is super invested in bringing a version of this to life for use!! 🚀

It's very exciting: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/CSSModules/v1Explainer.md

#cssModules #htmlModules #jsonModules #ohMy

@keithamus @ryantownsend @developers

I'd be down for a Level 1 that was only collapsing this into HTML: https://codesandbox.io/p/sandbox/n6q2t5?file=%2Ffetch-html.js

We can get into the magic of templates and arguments and whatnot later...

Then a standard issue HTML-first page could be rendered a la:

<template src="/header.html"></template>
<template src="/nav.html"></template>
<template src="/side-nav.html"></template>

<!-- CONTENT -->

<template src="/footer.html"></template>

🤯

#htmlModules #htmlMacros #webComponents

@mayank “HTML modules” as a macro is such a cool idea. I agree 100% that it’s a place we should focus in on things like this. The #webComponentsCG sees this as a big next step towards clarifying #declarativeCustomElements API. Converting your blog to an explainer would be a great next step.

Disclaimer: in a recent meeting with implementors we agreed that Cross Root Aria and Scoped Custom Element Registries are of higher priority. Having solid plans for #HTMLModules when they get done will be 🔥

Through the conversation, I wondered whether the misunderstanding that a #customElement directly correlates to a #frameworkComponent was eased or expanded with the theoretical advent of an HTML Module. Much of what we were seeing as #htmlModules seemed more directly related to what we see in #frameworkComponents, which seems like an interesting path to investigate.

With #domPart and HTML Modules, it it possible to recreate what we know now as a #JSFramework in just HTML!?! 🤯

@westbrook @davatron5000 @stubbornella I suspect this might overlap with existing #HtmlModules work.

Also one more idea similar to 1.:

5. Could we use this format to do the initial render of a component? By which I mean that #Angular compiles components to #JavaScript which looks like:

```
function renderComponent() {
if (initialRender) {
createComponentDom();
} else {
updateExistingDom();
}
}
```

This always bugged me as inefficient, because the first branch is only ever executed once per component instance. If we compiled components to this SFC format, could we just do the first render at compile time, generate the HTML directly and drop that `createComponentDom` function?

I'm not knowledgeable enough to say that definitely makes sense, but I think it's an interesting idea at least.

Not sure if other frameworks could benefit from similar optimizations, I suspect #React would not, but I'm less clear on non-#VDom frameworks.