Here's a new library to solve a problem you don't have yet.
Fixed that for you :)
Despite being 6 years in development:
- they basically delivered none of the original promises
- they are extremely cumbersome to use without a library/framework on top (Polymer is the jQuery of WebComponents)
- they are plagued by multiple problems and shifts in the ecosystem (browsers don't want to support `is=`, HTML imports are being dropped in favour of ES6 imports)
- they have multiple problems integrating with existing frameworks: https://custom-elements-everywhere.com (basically any framework that bastardises HTML syntax is ok, anything relying on Javascript only is in trouble)
Don't hold your breath for the next couple of years as everyone tries to figure out how to work with them.
To me, it doesn't seem like too big of a stretch to think that the popular frameworks of today will move to the custom element spec instead of their own proprietary component model.
Maybe they don't solve your problem, but they certainly seem to solve Ionic's or Netflix's problems (or mine for that matter).
"Vue.js seems to solve Gitlab's problems (or mine for that matter)"
etc.
Throwing big names around amounts to pretty much nothing.