Is styling web components still the biggest issue with adoption?

https://www.smashingmagazine.com/2016/12/styling-web-components-using-a-shared-style-sheet/

by taf2 • 3 years ago

8 7 3 years ago

troupo3• 3 years ago

The biggest issue with adoption is that they need 20 more nee web standards to fix issues literally no other lib, framework or approach has.

pjmlp3• 3 years ago

The issue is that cool kids use React, and they are the only main SPA framework that doesn't care about Web Components.

troupo3• 3 years ago

hey are the only main SPA framework that doesn't care about Web Components.

Depends on what you mean by "main SPA frameworks", but most of them couldn't care less about Web Components, and are at best neutral towards them. Even frameworks that looked to them as inspiration at the start are now openly quite against them (Vue, Svlete).

Among the multitude of UI frameworks in general you'd be hard pressed to find those that target web components beside the usual suspects of lit and stencil: https://krausest.github.io/js-framework-benchmark/current.ht...

moritzwarhier• 3 years ago

I have successfully used a web component library with react, no significant issues apart from stringly typed Events and Shadow DOM (if you want custom Styling with it, you depend on css variables if the component provides them)

pjmlp3• 3 years ago

Only three matter for most folks, React, Vue and Angular.

From those three, only React doesn't provide Web Components interop, or the option to produce their components as Web Components.

As for your Vue remark.

https://vuejs.org/guide/extras/web-components.html

"We consider Vue and Web Components to be primarily complementary technologies. Vue has excellent support for both consuming and creating custom elements."

Is styling web components still the biggest issue with adoption?

Related Stories