A look at WICG/webcomponents: 4.5k stars on GitHub, written primarily in HTML. Web Components specifications
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Web Components are a new browser feature that provides a standard component model for the Web, consisting of several pieces maintained in different places:
Shadow DOM
Most of the parts are now maintained in DOM Standard, called shadow trees.
Some of the parts are still remained in this repository. See Issue #661 for the progress of upstreaming those parts from the partially out-of-date Shadow DOM document.
Issues against the DOM and HTML Standard.
Issues raised in this repository.
The old issue tracker on W3C bugzilla, which is no longer used.
Custom Elements
Custom elements were upstreamed into the HTML Standard (and bits in the DOM Standard) and are maintained there.
Issues against the DOM and HTML Standard.
Issues raised in this repository.
The old issue tracker on W3C bugzilla, which is no longer used.
HTML Templates
HTML Templates were upstreamed into the HTML Standard and are fully maintained there.
CSS changes
The CSS WG works on CSS Scoping and CSS Shadow Parts, which help dealing with shadow trees with various selectors. Various other parts of CSS and its object model are also impacted by shadow trees and directly worked on in the various CSS specificaions.
Issues against the CSS WG repository.
JSON, CSS, HTML Modules
Successor to the abandoned HTML Imports, allows JSON, CSS, and HTML markup to be requested by a component. HTML Modules Spec work is being incubated upstream in whatwg/html (see PR). For new issues, please file against whatwg/html or here in w3c/webcomponents. See also the HTML Modules explainer, initial proposal, and earlier design ideas.
Issues raised in HTML Standard
Issues raised in this repository. Includes related issues for other potential module-types, such as CSS and JSON.
Old issue tracker includes a few issues filed when the feature was first proposed. Please avoid filing new issues there.
Issues
Please file issues in the most specific repository possible, per the above issue pointers. (It's often not this repository.)
Abandoned features:
HTML Imports
The current issue tracker.
The old issue tracker on W3C bugzilla, which is no longer used.
Note: HTML Modules are intended to replace HTML Imports (see above).
TopGit's last sync did not record any GitHub topics for WICG/webcomponents. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on WICG/webcomponents?
The most recent commit recorded on WICG/webcomponents was 8 months ago, based on the GitHub push timestamp. The repository has 393 forks — one of the better signals of community interest.
How many stars does WICG/webcomponents have?
WICG/webcomponents has 4.5k GitHub stars — refresh the page for the live number, or check github.com/WICG/webcomponents. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is WICG/webcomponents written in?
WICG/webcomponents is written primarily in HTML. GitHub's language field is based on the largest share of bytes in the default branch.
Where do I read more about WICG/webcomponents?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/WICG/webcomponents is the definitive source.
Read full README in the tab above.
Curious whether webcomponents is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about webcomponents.
/webcomponents