Airhorner Custom Element
Possibly the world's best airhorn now as a custom element
I love the web. The web should allow anyone to access any experience that they need without the need for native install or content walled garden.
Possibly the world's best airhorn now as a custom element
I'm exploring the best way to load web components, focusing on how to include styles and templates without creating uncontrolled blocking requests. I've experimented with using a single JavaScript file that encapsulates everything, including styles and a dynamically created template element. This approach avoids external requests but raises questions about extensibility and best practices. Should we revive HTML imports, embrace ES modules, or find a common model for handling templates and styles? Is inlining templates a reasonable solution? I'm looking for community input on how to balance performance and developer experience when deploying web components.