8 replies

1. Jason Miller 🦊⚛️ 1 day later

   @zachleat lol is it bad if I don't?

   1. Jason Miller 🦊⚛️ 1 day later

      @zachleat it's not perfect, mind, but I've never had something come up that was difficult or unwieldy enough that it would have justified a change to Preact or WCs. Using WCs built with Preact and WC's built in Lit rendered by Preact in a bunch of places at work right now actually.

      1. JoviDeCroock 1 day later

         @developit @zachleat The code is minimal, the main things that cause friction are props vs attributes, weirdly named i.e. onX or an overlap with data- due to dash in the fifth spot

         1. Jason Miller 🦊⚛️ 1 day later

            @jovi @zachleat tbh both of those ended up not being an issue for foundation components because the custom elements define accessor pairs for event handler properties and reflected attributes so the events are registered in the correct casing and attributes never used by Preact. Works pretty well!

            1. JoviDeCroock 1 day later

               @developit @zachleat Oh yea, it works well but these patterns seem pretty widespread afaict

               1. JoviDeCroock 1 day later

                  @developit @zachleat The guides on how to do web-components the right way are probably as scarce as Preact, so the combination of them... 😅

                  1. Jason Miller 🦊⚛️ 1 day later

                     @jovi @zachleat lol yeah very true.

   2. Zach Leatherman 2 days later

      @developit no! Would certainly disagree with some points coming from Svelte, Vue, and Solid.js camps though 🫠