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.

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

> 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...

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)

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."

You can consume Web Components in React just fine.

It's not seamless for a variety of very well documented reasons (stemming, in no small part, from the design of Web Components themselves).

And yes, consuming and perhaps sometimes compiling to web components is the extent the absolute vast majority of frameworks do. You'd do well to read and listen to what the authors of those frameworks have to say about web components.

We do read and listen, hence why we know that their attitude is definitely not the same of React folks, regardless of the wording.