2026-10-20 00:40 UTC
Replies (4)
-
@templarian@fosstodon.org 2026-10-20 01:29
@nolan@toot.cafe been using web components and Claude as I share features across a few projects. The only benefit maybe is lowering the dependencies. Outside of maybe modularity, but as you've said some other frameworks already handle that pretty well for vibe coded apps (and are progressing fast with new features). I do feel like no one really talks about Web Components anymore or has for a bit.
-
@knowler@sunny.garden 2026-10-20 02:03
@nolan@toot.cafe There’s a number of web components folks involved in MWG (myself included), so I don’t think it’s intentional that custom elements might be snubbed in the output. We could probably do a better job of mentioning good opportunities to use them as well as providing stronger guidance in favour of using them. Some of the newer guidance categories (e.g. `guides/ui-components`) are a good fit for doing just that. (Opinion: completely my own) In case you don’t know, the fuller source for the project is here: https://github.com/GoogleChrome/modern-web-guidance-src
-
@revin@toot.cafe 2026-10-20 02:10
@nolan@toot.cafe I’m a huge fan of web components as a way of getting separation of concerns between the data on a page versus the structure of its UI. Being able to do stuff like querySelectorAll to enumerate and filter the data on the page makes the browser dev tools console into a live editing environment/ REPL type thing
-
@tomayac@toot.cafe 2026-10-20 06:27
@nolan@toot.cafe I find it's trivial to get agents to write Web Components. I literally just have "use vanilla JavaScript and Web Components" in my `CLAUDE.md` and that's it. There's excellent training material out there (thanks to people like you ❤️), so agents are really good at writing them. You have to know they exist, though, which is why pure vibe coders likely won't get them by default.