I'll still be looking for Web Component news big and small, and interesting projects that make use of WC so feel free to tweet or DM with anything you've been working on. Thanks!
Almost there π SWTL will be able to SSR custom elements. The customElementRenderer is pluggable, so it supports @buildWithLit , but could probably support @enhance_dev `CustomElement`s as well, or other custom element renderers
I think this is great news. The core components will remain free and open source, but there's now a business model that will ensure the project gets the investment it needs and deserves to continue to be developed and maintained into the future! Happy to be a backer.
@patrickjs I suppose you could do something similar with a server side web component - but is the attraction of RSC that this would also work as a client side component too?
I've been playing with streaming Declarative Shadow DOM recently and it enables some pretty unique behaviour - e.g. https://t.co/TpcPHQJnFH - a completely JS free, backend agnostic way to deliver your page shell instantly and progressively load in slotted content as it's received
@patrickjs Well Firefox doesn't quite have support yet, and Safari has a higher threshold (~512bytes) before triggering streaming, but it does work after reaching that theshold.
Did you know you can stream HTML out of order without any JavaScript at all?
A put a little blog post together explaining how: https://t.co/jB4UtL0dUE
See a demo: https://t.co/NvrfvSM4e6
Supported in Chrome and Safari, and in Firefox in a month or two.
Great news! If Shoelace so far has been @claviska working on it as a side project, imagine what it will be like with his full time attention! π ππ
Time to talk about the future of Shoelace.
It's been more than two years since the beta release of Shoelace 2.0, which was the first version of the project to ship Web Componentsβ¦
π cont'd
Time to talk about the future of Shoelace.
It's been more than two years since the beta release of Shoelace 2.0, which was the first version of the project to ship Web Componentsβ¦
π cont'd
Hey.. so I found a way to author Declarative ShadowDOM just once for a given element and then reuse that DSD any number of times without having to rewrite it, without any build tools, and without any JavaScript.
I've been playing with streaming Declarative Shadow DOM recently and it enables some pretty unique behaviour - e.g. https://t.co/TpcPHQJnFH - a completely JS free, backend agnostic way to deliver your page shell instantly and progressively load in slotted content as it's received
Stating the obvious maybe, but the tendency for some discussions concerning contrasting opinions on Web Dev Twitter to devolve into arguments, sometimes personal, is very off putting for a lot of people, whether or not you're personally involved.
Lots of interesting food for thought here on component based architecture. To paraphrase, when all you have is a hammer everything looks like a nail. Looking forward to seeing ideas in this space breaking out of the current JS centric framework approach!