2,608 karma · joined December 12, 2012
[ my public key: https://keybase.io/wildpeaks; my proof: https://keybase.io/wildpeaks/sigs/yQmAnhmw5ODzOpfBpYvX1T7owc-Fwoe6TpMkU8-94Ho ]
It's a reasonable compromise given the original purpose of custom elements, but in practice it ends up more maintainable to be inspired by its structures without using real custom elements despite I was initially excited that jsdom supports custom elements nowadays.
By remaining expensive proprietary tools, they lost the new generations of developers who learned 3D with Blender and Houdini Apprentice and who will naturally continue to use them once they become professionals, so the customer base will keep shrinking.
But in browser, for now only the more limited JSDoc-style types can be shipped as-is indeed.
Server-side you can use jsdom to polyfill document, it supports Web Components too.
May your glühwein be hot and your cats purring :)
For example, this is why the way someone treats service workers is a good indicator of someone's character.
I haven't been participating as much lately because life got in the way but I'm still thankful this community exists, it remains one of the very few places I can have high level discussions with fellow inquiring minds.
Wow, 13 years already :)
You probably even saw some of them around, they have a very distinctive yellow cover.
Typescript can even add Intellisense to "customElements.get" by augmenting CustomElementRegistry: https://gist.github.com/cecilemuller/72fbb3bc3a77d82c8a969cd...
Although I'm more surprised a repo that appears to be merely a week old already has 245 stars.
I highly recommend the `erasableSyntaxOnly` option in tsconfig because TS is most useful as a linter and smarter Intellisense that doesn't influence runtime code: