calcite-design-system
declarative-shadow-dom
calcite-design-system | declarative-shadow-dom | |
---|---|---|
2 | 2 | |
261 | 189 | |
3.4% | - | |
9.9 | 4.1 | |
about 4 hours ago | about 1 month ago | |
TypeScript | HTML | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
calcite-design-system
-
HTML with Superpowers: An Introduction to Web Components
Esri’s Calcite Component library is another.
https://github.com/Esri/calcite-components
-
Web Components
Example of a larger company using it: https://github.com/Esri/calcite-components
declarative-shadow-dom
-
HTML with Superpowers: An Introduction to Web Components
Take a look at Declarative Shadow DOM: https://github.com/mfreed7/declarative-shadow-dom
-
Shoelace: A Web Component Kit
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.)
What are some alternatives?
arcgis-rest-js - compact, modular JavaScript wrappers for the ArcGIS REST API
design-reviews - W3C specs and API reviews
ui-image-site-challenge - A sample website from an interview challenge which displays a number of images with the speed limit signs marked. Built using Web Components.
ui5-webcomponents - UI5 Web Components - the enterprise-flavored sugar on top of native APIs! Build SAP Fiori user interfaces with the technology of your choice.
lite-youtube - The fastest little YouTube web component on this side of the internet. The shadow dom web component version of Paul's lite-youtube-embed.
webcomponents - Web Components specifications
custom-elements-everywhere - Custom Element + Framework Interoperability Tests.
prerender - Node server that uses Headless Chrome to render a javascript-rendered page as HTML. To be used in conjunction with prerender middleware.
WHATWG HTML Standard - HTML Standard
lit - Lit is a simple library for building fast, lightweight web components.
hypernova - A service for server-side rendering your JavaScript views