home.social

#webcomponent — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #webcomponent, aggregated by home.social.

  1. @ariel's new #javascript microframework/library Elena looks amazing and you should absolutely consider if you're looking for a scaffolding shortcut for your next #webComponent project. Here's my take on it:

    🔗 danq.me/elenajs

  2. The hoops you jump through to battle FOUC when <dark-mode-toggle> is a #webcomponent with custom dark/light states... but all this async JS magic may need some time to initialize, so there's also a content attribute for the initial state, but that may in turn be overridden by user choice (and therefore one of the custom states) 🥴

    #css #webdev

  3. 🚨 New version of my mastodon-comments webcomponent available! 🚨

    This webcomponent integrates a mastodon thread into a website to be used as a discussion thread.

    The last version of the component introduces a dialog to allow the user selecting their mastodon instance to reply from.

    👉 github.com/dpecos/mastodon-com

    #mastodon #comments #webcomponent

  4. spark_framework 1.0.0-alpha.2 is now on pub.dev/packages/spark_framewo!

    lots of improvement.
    ✅ New way to write interactive component
    ✅ Fixed the reactive attribute of the component.
    ✅ Support for Cookie
    ✅ Automatic support for nonce when CSP header is present

    To see how we write component now checkout:
    spark.kleak.dev/docs/components

    #dart #dartlang #web #webdev #webcomponent #spark

  5. 🚚 New cem release! The standards-based #WebComponent multitool just released v0.9.0 including support for #JavaScript class mixins, numerous bug fixes, and an overhauled and much more readable docs site.

    Give it a try today in your web components project and let me know what you think!

    bennypowers.dev/cem/

    github.com/bennypowers/cem/releases/tag/v0.9.0

  6. This weekend, I was inspired by the once-common, now-absent "Turbo" button of computers past. So I implemented a #webComponent that reproduces the experience of pressing one and watching the little LED turn off and on.

    Wanna see?

    🔗 beige-buttons.danq.dev

  7. <color‑input> — современный веб‑компонент Адама Аргайла для выбора цвета, который поддерживает широкий цветовой охват (sRGB, Display P3, Rec2020) и конвертирует между sRGB, HSL, HWB, LAB, LCH, OKLCH и OKLAB. Построенный на Color.js, Preact Signals и Shadow DOM, он настраивается через CSS parts и поставляется в виде tree‑shakeable ES-модулей. Кастомный элемент автоматически регистрируется при импорте и работает в браузерах с Popover API. #webcomponent #color

    color-input.netlify.app/

  8. It's Twofer Friday! 🥳

    1) @11ty website redesign: patrickgrey.co.uk/ 💅

    2) I'm launching v1 of my small #webComponent library: Naked Web Components! They are focussed on function with minimal styling.

    Read all about it here: patrickgrey.co.uk/projects/nak and find the code here: codeberg.org/patrickgrey/naked.

    I never expected to create a component called <naked-sticky-overflow>... 😬

    I'd love to know if they are useful for anyone 🥰

  9. Trying out moving Joist over to Codeberg. If you are over there give it a star and a watch!

    codeberg.org/deebloo/joist

    #webdev #webcomponent #javascript

  10. Why do all #webcomponent examples use innerHtml = when innerHtml is inherently insecure?

  11. Because of the generic nature of the terms, I'm having trouble searching for something that should have a page in the Nuxt docs somewhere:

    I want to use an existing Web Component (developed by a third party) in a Nuxt app. It is having trouble with the SSR and I can't figure out how to work around it so that the web component is named in the template area but is only initialized in the browser.

    Or, alternately, what I can tell the developer to do differently to make it work. It says it can't find "HTMLElement".

    #nuxt #webcomponent

  12. Wanted to try out this <syntax-highlight> #WebComponent for myself andreruffert.github.io/syntax-

    The result is super clean and a fair chunk smaller than what's typically used. Even works with contenteditable!
    codepen.io/daviddarnes/pen/bNV

  13. You know what I love? clicking on the "copy" button on #github and having it do literally nothing

    see, this button used to be a
    #webcomponent, and it would just work in all cases, but that was unacceptable because you can't hire people to write web components


    So now it's a fabulous, very functional, very just
    #javascript #react component, and I'm happy because even though it doesn't work, it looks great on a State Of survey.

  14. Are Web Components & Cybersecurity A Better Combo?

    I'm not trying to dunk on popular #UI #frameworks – I'm sure they're totally fine for #cybersecurity stuff, probably get loads of reviews and #audits.

    But from my angle: Web Components are *native* to the #browser. Doesn't that just inherently reduce the risk of **#SupplyChainAttacks** (you know, like a rogue `npm install` on a bad network) for your #AppSecurity?

    Or am I overthinking it, and the #framework choice is less important than the #browser, #OS, or #device running it? What are your thoughts, #DevCommunity?

    ---

    Quick context: I've got a #ReactJS #messagingApp (repo here: github.com/positive-intentions) and a separate #UIFramework (repo here: github.com/positive-intentions) built with #Lit (which uses Web Components). I'm genuinely wondering if there's a compelling #cybersecurity reason to refactor the chat app to use my #WebComponent UI framework. Might be a whole new level of #SecurityByDesign for #FrontEndDev.

    FYI, same question's on Reddit here: reddit.com/r/ExperiencedDevs/c, got some good #insights, but want to make sure nothing's getting overlooked! Let's discuss #InfoSec #WebDev #JavaScript #OpenSource #TechQuestion.

  15. Are Web Components & Cybersecurity A Better Combo?

    I'm not trying to dunk on popular #UI #frameworks – I'm sure they're totally fine for #cybersecurity stuff, probably get loads of reviews and #audits.

    But from my angle: Web Components are *native* to the #browser. Doesn't that just inherently reduce the risk of **#SupplyChainAttacks** (you know, like a rogue `npm install` on a bad network) for your #AppSecurity?

    Or am I overthinking it, and the #framework choice is less important than the #browser, #OS, or #device running it? What are your thoughts, #DevCommunity?

    ---

    Quick context: I've got a #ReactJS #messagingApp (repo here: github.com/positive-intentions) and a separate #UIFramework (repo here: github.com/positive-intentions) built with #Lit (which uses Web Components). I'm genuinely wondering if there's a compelling #cybersecurity reason to refactor the chat app to use my #WebComponent UI framework. Might be a whole new level of #SecurityByDesign for #FrontEndDev.

    FYI, same question's on Reddit here: reddit.com/r/ExperiencedDevs/c, got some good #insights, but want to make sure nothing's getting overlooked! Let's discuss #InfoSec #WebDev #JavaScript #OpenSource #TechQuestion.

  16. Are Web Components & Cybersecurity A Better Combo?

    I'm not trying to dunk on popular #UI #frameworks – I'm sure they're totally fine for #cybersecurity stuff, probably get loads of reviews and #audits.

    But from my angle: Web Components are *native* to the #browser. Doesn't that just inherently reduce the risk of **#SupplyChainAttacks** (you know, like a rogue `npm install` on a bad network) for your #AppSecurity?

    Or am I overthinking it, and the #framework choice is less important than the #browser, #OS, or #device running it? What are your thoughts, #DevCommunity?

    ---

    Quick context: I've got a #ReactJS #messagingApp (repo here: github.com/positive-intentions) and a separate #UIFramework (repo here: github.com/positive-intentions) built with #Lit (which uses Web Components). I'm genuinely wondering if there's a compelling #cybersecurity reason to refactor the chat app to use my #WebComponent UI framework. Might be a whole new level of #SecurityByDesign for #FrontEndDev.

    FYI, same question's on Reddit here: reddit.com/r/ExperiencedDevs/c, got some good #insights, but want to make sure nothing's getting overlooked! Let's discuss #InfoSec #WebDev #JavaScript #OpenSource #TechQuestion.

  17. Are Web Components & Cybersecurity A Better Combo?

    I'm not trying to dunk on popular #UI #frameworks – I'm sure they're totally fine for #cybersecurity stuff, probably get loads of reviews and #audits.

    But from my angle: Web Components are *native* to the #browser. Doesn't that just inherently reduce the risk of **#SupplyChainAttacks** (you know, like a rogue `npm install` on a bad network) for your #AppSecurity?

    Or am I overthinking it, and the #framework choice is less important than the #browser, #OS, or #device running it? What are your thoughts, #DevCommunity?

    ---

    Quick context: I've got a #ReactJS #messagingApp (repo here: github.com/positive-intentions) and a separate #UIFramework (repo here: github.com/positive-intentions) built with #Lit (which uses Web Components). I'm genuinely wondering if there's a compelling #cybersecurity reason to refactor the chat app to use my #WebComponent UI framework. Might be a whole new level of #SecurityByDesign for #FrontEndDev.

    FYI, same question's on Reddit here: reddit.com/r/ExperiencedDevs/c, got some good #insights, but want to make sure nothing's getting overlooked! Let's discuss #InfoSec #WebDev #JavaScript #OpenSource #TechQuestion.

  18. Are Web Components & Cybersecurity A Better Combo?

    I'm not trying to dunk on popular #UI #frameworks – I'm sure they're totally fine for #cybersecurity stuff, probably get loads of reviews and #audits.

    But from my angle: Web Components are *native* to the #browser. Doesn't that just inherently reduce the risk of **#SupplyChainAttacks** (you know, like a rogue `npm install` on a bad network) for your #AppSecurity?

    Or am I overthinking it, and the #framework choice is less important than the #browser, #OS, or #device running it? What are your thoughts, #DevCommunity?

    ---

    Quick context: I've got a #ReactJS #messagingApp (repo here: github.com/positive-intentions) and a separate #UIFramework (repo here: github.com/positive-intentions) built with #Lit (which uses Web Components). I'm genuinely wondering if there's a compelling #cybersecurity reason to refactor the chat app to use my #WebComponent UI framework. Might be a whole new level of #SecurityByDesign for #FrontEndDev.

    FYI, same question's on Reddit here: reddit.com/r/ExperiencedDevs/c, got some good #insights, but want to make sure nothing's getting overlooked! Let's discuss #InfoSec #WebDev #JavaScript #OpenSource #TechQuestion.

  19. Just released: #teskooano new #webComponent based engine toolbar - a plugin toolbar that allows panels to register themselves with a button - so it;s much easier to add new features.

    teskooano.space

    #gameDev #indieDev #threeJS

  20. We are happy to announce our new open-source web template for creating a simple and minimal radio directory - Radiohub! It's powered by the amazing web-component library Shoelace.

    Feel free to check it out and let us know your feedback.

    github.com/digitalmalayali/rad

    #digitalmalayali #opensource #webtemplate #shoelace #lit #lithtml #webcomponent #radio #radiodirectory