Are Web Components A Good Choice?

[@CalifornianViking]

Thanks for this honest and practical view of Web Components. I personally believe that we have navigated down a dead-end path with the current approach to building web applications using Single-Page Applications (SPA). It looks like we are building monolithic applications running in the web browser with complex and highly dependent data (JSON REST data) interfaces to the back end. This approach makes it very hard to create mashups that can create a common user experience across multiple back ends. Imagine that you are a company that has chosen three applications: finance application A, customer relationship management application B, and supply chain management application C. Each of these applications provides its own user experience. How can I build a front end that allows Alice in accounting to work across all three? One option is for each application to use Web Components. All I would need to do is build a front end that consumes these components. What is the best way to do that?

[@js2brain]

Since Web Components are standard, you are quite free in your choice. If you don't want to build an SPA, you can use one of the meta frameworks like Next (React) or Nuxt (Vue). You could also use HTMX, if you prefer. If you are fine with an SPA, you could also build an app completely in Lit. The property and event binding to Web Components is very nice.

[@orderandchaos_at_work]

Stencil -> React components works great. SSR with web components is a nightmare.