Snuggs

P.S. To be clear I still feel @TehShrike's work **SHOULD** be merged in. After all we are simply devs who just want to use this library and nothing more. I...

@ljharb FWIW I know you mentioned earlier awaiting node progress. However to your point in the comment above would it be ok to do an extension lookup `||` array matching...

> You also have to patch document.createElement so that the 2nd argument can be an options argument with {is: 'foo-element'}. - @ChadKillingsworth TRUE! However, then you do not get the...

@fippo this can turn into a ton of technical debt very fast as i'm sure you already know. Also not sure what happens from breaking typical node conventions of traversing...

FWIW @domenic @foolip @annevk have used it **thoroughly** the past year. Currently using in production. Cute content negotiation trick we do with the lib (besides typical Encoding negotiation) is using...

> (I'm probably wrong on ), but l don't know where that is defined as HTML doesn't define that attribute. - @annevk :thinking: https://html.spec.whatwg.org/multipage/semantics.html#attr-meta-name

Oh wow `` does work on https://checker.html5.org I didn't expect that. Hadn't checked.

Indeed @TakayoshiKochi we created a super simple `` iteration utilizing the `DOMParser`. Methinks this is how polyfills are _(not doing a good job of)_ handling HTMLImports. > I'd encourage anyone...

> Ignoring the fact your code doesn't work ... 1. @Yay295 the code works fine. Was a snippet from the pr that was [*clearly* referenced in the previous comment](https://github.com/devpunks/snuggsi/blob/453febfb30e6db5103362ea36b9fa8b58be683ee/examples/import-html/index.html). Spared...

@rianby64 Have to understand that from our tracking/observation of the insane multitude of issues related to `imports` and `includes`. I feel there's a lack of understanding of what the respective...