Web Component tips by @lamplightdev. Writing a short & sweet summary of the week's #webcomponents news https://xitter.cf/t.co/PeIQLfuLWJ @lamplightdev@mastodon.social
UK
Joined August 2020
- Tweets225
- Following605
- Followers793
- Likes401
Very much looking forward to playing with this!
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.
This quoted post is unavailable.
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?
Yeah, styling can be an issue, although I think there are discussions around enabling some kind of slot behaviour with light dom
Did you know you can stream HTML out of order without any JavaScript at all?
A put a little blog post together explaining how: lamplightdev.com/blog/2024/0…
See a demo: ooo.lamplightdev.workers.dev…
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! 🚀 👟🚀
Web Component Bytes retweeted
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
Here's an example of (streaming) DSD with and without the polyfill - it's tiny and works well xitter.cf/wcbytes/status/1541546…
I've been playing with streaming Declarative Shadow DOM recently and it enables some pretty unique behaviour - e.g. enamel.pages.dev/ - 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!
Where Web Components Went Wrong (And How We Can Turn It Around)
space.matthewphillips.info/p…
Web Component Bytes retweeted
Where Web Components Went Wrong (And How We Can Turn It Around)
space.matthewphillips.info/p…
The body content and the subsequent 3 sections are artificially delayed on the server to demonstrate that you can instantly render the page shell and then render the rest of the content as it becomes available