That is a very good example of it doing what it should do actually. The browser native data input or an existing webcomponent is way more maintainable long term

ReactやVueを使った、JSによるHTML生成は、人間がコーディングする上での手間を考慮して、採用が増えたと思う。 一方、AIでコード生成するなら、人間のコーディングの手間はない。 また、ブラウザも進化してて、標準WebComponentの仕組みもあり、ビルドが必須でもない。

«Quiero hacer un webcomponent con un canvas de 800x300. En el canvas se ve la visión desde un vehículo o coche, donde vemos una carretera. El canvas emula un juego donde con los cursores podemos mover el coche hacia la derecha o izquierda, para conducir por la carretera, la cuál va teniendo curvas en esas direcciones. El canvas debe verse una autopista o carretera, POV, al estilo a juegos antiguos de MSDOS como Lotus o Test Drive.» Aquí usamos @forgecodehq como agente.

«Crea un WebComponent que utilice un canvas de 800x308 y se vea una animación de copos de nieve cayendo. El fondo será azul marino. Quiero que generes un muñeco de nieve en SVG en una parte de la escena. Crealo en un WebComponent diferente y lo añades de forma dinámica en el WebComponent de snowfall-canvas.» Usamos @opencode como agente.

so you are able to respond to any native event or custom event and have the current state of signals in a cache and optimized way. new CustomEvent('foo', {some: "bar"}) and access it via data-on:foo="@post('/commands/blah') works with all events (especially WebComponent driven)

I found kind of funny there are some WebComponent folks who attribute better performance for re-writes of some websites was because of moving away from React, and not because the re-write itself

Are there any plans to bring the web components used in checkout and accounts to the storefront? I know there are storefront web components but that is kinda scoped to buy button 2.0. Would be nice to have a single webcomponent library we can use across the whole buyer journey

Just for the hell of it, I opened up Cursor to see if it could do something simple: literally copy / paste 5 lines of HTML, change the ID tag/attribute, add 2 lines of javascript to the webcomponent associated with those. It could not follow those basic instructions. It renamed text *inside* the tags (not even html, just regular text) and it added 10 - 12 lines of javascript code it thought it needed to make the 2 lines I asked for work. Something so basic and it couldn't get even that right. It added 5 minutes of work to what should have taken 30 seconds. "It's a good autocomplete" my ass

mimium.org/en/ に使ってるエディタをWebComponent化したので簡単に埋め込めるようになった

Today i released a big update to spark. Lots of improvements in the framework. see yourself : pub.dev/packages/spark_frame… and even more in the cli : pub.dev/packages/spark_cli/c… #dart #dartweb #dartlang #ssr #webcomponent

I updated my article on reducing #WebComponent FOUC to include details on how to choose an appropriate timeout. #html #css #javascript dev.to/stuffbreaker/reducing…

I'm really proud of this setup for the upcoming NEAR merch store. It's the culmination of a lot of work... inspired by near.social and its decentralized frontends/modules. It combines runtime module federation for both the UI and the API -- the "host" is just a lightweight rsbuild shell that reads a JSON config, and then hydrates the entire application from remote modules. This means I can swap out the entire backend or frontend just by updating a single line in config: the remote entry. Modules are strongly-typed and can be deployed standalone as well, UI communicates with API over oRPC and API comes with OpenAPI spec automatically. It's pretty wild, I get deja-vu all the time... "gateways", bos-workspace, near-bos-webcomponent... and now this! Micro-frontends & micro-services built with @rspack_dev, oRPC (@unnoqcom), @EffectTS_, @ZephyrCloudIO, and @tan_stack router. It's not perfect, but it's working! The vision? @NEARProtocol accounts that can dictate, secure, and orchestrate highly-configurable, interconnected applications... stick this host in a TEE with a codehash attestation (via something like @out_layer) and I think you've got something pretty amazing, especially in this new world of AI generated applications. The more type-safe and scoped for the AI, the better!

DAY 74 After squat day, it’s time to build the widget with a webcomponent to add a feedback view in gat! v2 is gonna be big!

Sooo stoked, Publicly Shared Report URLs coming this week to Dreambase! Long time feature request fulfilled. Complete with dynamically generated Next.js OpenGraph images & details. Next up, Embeddable Webcomponent Reports.

How it looks? Full component tweet is on the way. #buildinpublic #web #webcomponent

Inventez vos propres balises HTML ! Découvrez comment créer des composants web réutilisables avec les Custom Elements en HTML5 Tutoriel complet : blog.crea-troyes.fr/7431/cus… #HTML5 #frontend #js #javascript #webcomponent #code #WebDevelopment #developpeur #webDesign

Trabajando en un webcomponent para añadir fácilmente circuitos a mí web. Todo integrado con Astro, vanilla, full brilli brili, y animaciones cucas ¡Hasta puedes hacer click en los interruptores y se recalcula todo!

Acaba de nacer OpenVidu Meet, una plataforma de videoconferencia lista para usar, que también se puede integrar en cualquier aplicación de forma muy sencilla (API REST y webcomponent) Gracias al equipo de devs que se implican mucho en lo que hacen openvidu.medium.com/introduc…

WIP: @crisp_im as a WebComponent. You can mount it anywhere in your app (Vue, React), size it as you'd like (sidebar) (We need this for an internal Crisp project, but it's a secret 🤫)

If you're ready to build a beautiful, well-crafted web project from the ground up, let's connect. Expect this quality of work. 🤝 🔗 zafar-saleem.github.io #ReactJS #NextJS #WebDevelopment #Startups #TechFounders #Frontend #WebComponent #saas #websites #landingpages