Awesome

polymer-cdn <sup><sub>v2.6.0.2</sub></sup>

A mirror of Polymer's components so that they can be used directly from CDN

Polymer CDN is powered by MaxCDN

❗  Polymer CDN now supports Polymer 2! Please report any issues you may find.

How to use

In general, given an element named my-cool-element, the CDN url for it will be:

https://cdn.rawgit.com/download/polymer-cdn/2.6.0.2/lib/my-cool-element/my-cool-element.html

To be sure, browse this repo and copy-paste the url to the raw version into RawGit.

Try a pen

Try hacking on this Codepen.

Versioning

As this repo groups a whole set of components, versioning is tricky. For now I've decided to follow the Polymer version number and add an extra number behind it for updates that did not involve a change of the Polymer version. It's important to remember that this repo does not (can not) follow semantic versioning guidelines and that it's version numbers indicate not much more than which versions came before which and after which other versions.

Make sure you always link to a specific version and not to master, as that would mean your code could change right under your nose. Something you don't want in production! Also, for this same reason, I recommend forking this repo and including from your own fork, so you'll have full control over it.

To see available versions and select one, use the Branch dropdown menu and select one of the tags. You can then browse that version of the Repo. Browse to the file you want to include and copy the url to it's raw version. Throw that into RawGit and you'll have a url to a file on CDN that never expires from cache and is not throttled or limited in bandwidth in any way.

Branch selection in GitHub

Missing something?

This repository aims to be a complete set of the standard Polymer components, grouped in such a way that (transitive) dependencies can be correctly resolved for all components. If you are missing some (version of) a component, please create an issue explaining what should be changed and I'll do my best to implement it.

In the meanwhile, you can fork this project and apply the needed updates to your own fork. It's a pretty simple process. Have a look at the Contribution Guide which explains it in more detail.

All the libraries available in polymer-cdn can be found side-by-side in the lib subfolder. Contained therein are all elements listed as compatible with Polymer 2.

It looks like gold-zip-input wasn't actually ported to Polymer 2 yet at the time of writing this, despite being listed as compatible, as witnessed by incompatibility warnings concerning this element in the Bower output at the bottom of this page. Your mileage with this element may vary.

Some of the libraries depend on other libraries. We call those other libraries the dependencies of the library. These dependencies will also be pulled into your page when you include such a library. If the dependencies themselves depend on yet other libraries, these dependencies of dependencies will also be pulled into your page, et cetera until the full dependency tree has been loaded. We call this transitive dependency resolution and it's built in to the way Web Components work.

The bower output below lists, for each library included in this CDN, the dependencies of that library. These dependencies are themselves also listed at the top-level, so you can work out the entire dependency tree for a library by carefully examining this diagram.