ui5-webcomponents VS declarative-shadow-dom

With the node adapter, I'm able to build successfully but when I do npm run preview It breaks, because I'm using a web components library UI5 web components and for some reason, I get this error:

Have you seen OpenUI5 by SAP? -> https://github.com/SAP/ui5-webcomponents

Look neat. They even have Typescript type definitions to it.

I did a simpile test with ScalablyTyped in order to import those into ScalaJS to no avail but there might be a fix.

Take a look at Declarative Shadow DOM: https://github.com/mfreed7/declarative-shadow-dom

Hmm, I see that Chromium shipped their implementation a year ago now; I had missed that. Other than that, there’s been no real change in the situation in the last almost two years (since Shoelace 2.0 was released, the last time I examined the situation). And there still doesn’t look to be any real interest in actually implementing it outside of Google: Mozilla are unenthusiastic though not against it <https://mozilla.github.io/standards-positions/#declarative-s...>, and WebKit still find fault with some aspects of the design (https://lists.webkit.org/pipermail/webkit-dev/2021-February/..., https://github.com/mfreed7/declarative-shadow-dom/issues/9), though they’re content most of the earlier issues are ironed out.

So you certainly can’t rely on scriptless server-side rendering of Shadow DOM being possible—it’ll work in Chromium only, and it’ll probably be at least another year or two before other browsers even contemplate doing anything with it.

(And of course, even once Shadow DOM is serialisable, that’s a far shot from a particular frameworky thing being SSR-compatible, but I was quibbling over the Shadow DOM and impossibility aspects, so I shan’t step back on that.)