Building Web Components - What I Learned

Web components, in essence, represent the modern web's promise of encapsulation and reusability. They're an umbrella term for a suite of technologies, allowing developers to create reusable custom elements with their functionality hidden from the global scope. But it's crucial to understand that web components are more than just a technology or a feature: they're a set of specifications and conventions.

There isn't a monolithic, singular way to build web components. Unlike certain frameworks or libraries that come with strict guidelines, web components, being more of a standard, leave much to interpretation. This freedom can be both exhilarating and overwhelming. Having built a few web components, I've learned a lot about the best practices and pitfalls of web components and here are some of my takeaways:

• Do not extend built-in HTML elements as Safari doesn't support it. Only extend HTML elements.

  Extending built-in HTML elements (like <button>, <input>, etc.) is referred to as customized built-in elements. As of August 2023, Safari does not fully support it. The safer approach is to use autonomous custom elements, which means creating entirely new elements like <my-button> or <my-slider>.

• The state of the component is cached in an object.

  This is a common pattern, especially in larger or more complex components. Managing the state in a centralized object can simplify update logic and make the component more readable.

• The state object will be defined in the ___PRESERVE_8___.

  Generally, it's a good place to define initial values. It ensures the state exists before any other methods attempt to use it.

• The state object will be initialized in ___PRESERVE_9___.

  This makes sense if you want to ensure the state object is populated with initial values when the element is added to the DOM.

• Element updates will be done with a dedicated ___PRESERVE_10___ method.

  It's a good practice to abstract the update logic to its own method. This makes the code modular and easier to maintain.

• Attributes define the initial component state.

  My components use attributes to allow users to configure the initial state of the component.

• Attributes will not be updated via the JS API.

  This follows how HTML elements work. For example, you can't update the value attribute of an <input> element with JavaScript. Instead, you update the value property.

• Boolean attribute changes will be monitored with a ___PRESERVE_14___.

  This will allow the deletion and addition of attributes to be monitored.

• All non-boolean attributes will be monitored in ___PRESERVE_15___.

  This is the built-in way of detecting attribute changes for web components.

• Attribute changes will call the element update method.

  This ensures the component remains reactive to changes.

• All attributes will be reflected with element properties in ___PRESERVE_16___.

  This ensures synchronicity between attributes and properties.

• Getters and setters will update the ___PRESERVE_17___ object and then call the component update method if necessary.

  It's common to use getters and setters for this. BUT, be aware that this can cause infinite loops, as updating a property in a setter could lead to the setter being called again!

• Encapsulation is powerful but can introduce styling challenges.

  Web components may include a shadow DOM, which ensures style and structure encapsulation. But it can also make it challenging when users want to style your component. A good approach is to provide CSS custom properties or "CSS variables" to allow for some style customization without breaching encapsulation. A README file is your best way to communicate how to style your component.

• Events are the bridge for inter-component communication.

  While encapsulation ensures separation, sometimes your web component needs to talk to the outer world. Custom events can broadcast updates and communicate with its surroundings.

• Accessibility is non-negotiable.

  Like all web development, accessibility is essential. Ensure that your components are accessible by using the right aria attributes, semantic HTML, and keyboard navigability. It's easy to overlook this with custom elements, but it's crucial.