Anna Monus
Jan 20, 2021 ⋅ 7 min read

What happened to web components?

Anna Monus Anna is a technical writer who covers frontend frameworks, web standards, accessibility, WordPress development, UX design, and more. Head to her personal blog Annalytic for more content.

Recent posts:

Vite Adoption Guide Overview Examples And Alternatives

Vite adoption guide: Overview, examples, and alternatives

Vite is a versatile, fast, lightweight build tool with an exceptional DX. Let’s explore when and why you should adopt Vite in your projects.

David Omotayo
Nov 29, 2023 ⋅ 16 min read
Implementing Advanced Features With The Navigator.Share API

Implementing advanced features with the navigator.share API

Explore advanced capabilities for content sharing with the navigator.share API, including dynamic content sharing, custom share targets, and batch sharing.

David Omotayo
Nov 29, 2023 ⋅ 10 min read
Chas Peacock Leader Spotlight

Leader Spotlight: Scaling for the next phase of growth with Chas Peacock

We spoke with Chas to get his insights on building technology and internal processes for companies that are scaling quickly.

Jessica Srinivas
Nov 29, 2023 ⋅ 7 min read
Cypress Adoption Guide: Overview, Examples, Alternatives

Cypress adoption guide: Overview, examples, and alternatives

Cypress is one of today’s foremost tools for testing web applications. Let’s explore when and why you should adopt Cypress in your projects.

Paul Akinyemi
Nov 28, 2023 ⋅ 10 min read
View all posts

5 Replies to "What happened to web components?"

  1. I have been using native web components for a few years now and I will never go back to frameworks. They are a completely unassay layer. ..of course I have always preferred component development over frameworks regardless of the platform.

  2. We have been using and supporting Web Components in ING Bank for years, we published our own open source library called Lion (https://github.com/ing-bank/lion). All our apps and websites are based on Web Components.

    Companies which use Web Components include Microsoft (https://www.fast.design/), SalesForce (https://developer.salesforce.com/docs/component-library/documentation/en/lwc), Adobe (https://opensource.adobe.com/spectrum-web-components/) and IBM (https://www.carbondesignsystem.com/), amongst many others.

    Sites such as Open Web Components (https://open-wc.org/) and Modern Web (https://modern-web.dev/) offers a wide array of developer support, guides, helpers, etc to get started and keep learning.

    I firmly believe Web Components are the future of web front-end development. However you can use Web Components TODAY to create accessible, safe and fast websites and web apps.

  3. All of the issues mentioned here about web components apply as well to the various frameworks!
    I have been using web components for years, and it is far more stable than frameworks.

  4. How do you tackle SEO issues that come with the introduction of the shadow-dom?
    The problem of pre-rendering: https://www.youtube.com/watch?v=rKgF0rf009c
    Besides Google no other search engine executes JS and even with Google there is only a “potential” 2nd crawl that might pick up your JS dependant content.
    How can we as devs. encounter this problem, using web-components?

Leave a Reply