Polymer 3.0 preview: npm and ES6 Modules
Today at the 2017 Polymer Summit in Copenhagen, we announced one of the biggest changes to our developer workflow in the project's history.
Today at the 2017 Polymer Summit in Copenhagen, we announced one of the biggest changes to our developer workflow in the project's history. Actually, it's two changes:
- Polymer is moving from Bower to npm.
- We're switching to using ES6 modules instead of HTML Imports.
We're currently previewing these changes—which will be included in the next major version of Polymer—so we can get feedback, and continue working on them in public. By all means, experiment with the preview. For production work, continue using the existing Polymer 1.x or 2.x library you're using today. If you're starting a new project today, we recommend using Polymer 2.x.
While these changes will be significant, we’re committed to making the transition as seamless as possible. The Polymer 3.0 API will be essentially identical to the 2.x API. To the extent that any API changes are necessary, we expect them to be minor and easy to apply mechanically. All of the classes, mixins, elements, template system, and other APIs that are a part of Polymer 2.x are being ported to modules, including the Polymer 1.x legacy syntax. All of the knowledge that Polymer developers have will translate directly to Polymer 3.0.
We’ll also be providing a tool called Polymer Modulizer to automate the conversion of your current elements and apps to Polymer 3.0. This tool will be available immediately as part of the preview and has already been tested against the Polymer library and the full set of Polymer elements.
Today's post describes our reasoning behind the changes in Polymer 3.0, and the next steps that need to happen before a stable release. Tomorrow, we'll get you started working hands-on with the preview code.
Why are we switching to NPM and ES6 modules?
Since the early days of Polymer, we've used Bower and HTML Imports to manage dependencies: Bower to install dependencies, and HTML Imports to load them.
These technologies have worked great if you committed to an HTML Imports-based workflow, like Polymer and third-party web components that have followed Polymer’s lead. But they've put us outside the mainstream of web development, and made it hard for people working with other frameworks or build tools.
On the other hand, moving to ES6 modules and npm has several advantages:
- Polymer elements and applications will run without any polyfills on recent versions of Chrome, Opera, and Safari. When Edge and Firefox ship custom elements and shadow DOM, Polymer will run polyfill-free on those browsers, too.
The following sections describe these changes in more depth.
HTML Imports ➙ ES6 Modules
Since the beginning, Polymer has used HTML Imports to load dependencies. HTML Imports have a lot of benefits:
- Web-native loading mechanism. No build tools are required to load code using HTML Imports.
- Transitive loading of dependencies with ordered evaluation. That is, if A imports B, and B imports C, C and B are loaded and evaluated before A.
- Deduplication of dependencies by URL. Each import is downloaded and evaluated only once, even if imported multiple times.
- Native HTML parsing.
But HTML Imports have not gotten traction among the standards committees or other browsers. There are active discussions on a successor, but any new standard would be years away.
- Web-native loading mechanism.
- Transitive loading of dependencies with ordered evaluation.
- Deduplication of dependencies by URL.
The one HTML Imports feature obviously missing from ES6 modules is native loading and parsing of imported HTML. We’d like to see the platform get this feature back, but while standards discussions unfold we believe that embracing the widely adopted ES6 modules standard is what’s best for our developers and their users.
Bower ➙ npm
Like HTML Imports, Bower has been with us for a long time. Bower's flat dependency tree is ideal for front-end projects. But Bower has never been as widely adopted as npm, and while it's still maintained, it's no longer being actively developed.
Moving to npm will make Polymer packages seamlessly available to the millions of npm users, and allow Polymer packages to easily use other packages from the massive npm ecosystem.
This has been a long requested feature, but we've been waiting until we had good solutions for supporting flat installs of modules and keeping Bower and npm packages in sync.
The Yarn npm client provides support for flat installs, which solves our #1 issue with npm.
After considering a number of approaches to keeping Bower and npm packages in sync, we concluded that maintaining parallel versions was impractical. So we're making a clean break at 3.x and moving to npm exclusively.
When will this happen?
You can preview the new version of the library and elements now, but there are still a number of pieces that need to come together to make a full, production release.
Right now, we have:
- Working versions of the Polymer core library and elements published to npm.
- Support for npm packages in
We need a few more things to come together before we release Polymer 3.0:
- We'd like to see at least one browser shipping full support for modules, including dynamic imports. (Safari 10.1 and Chrome 61 already support modules, but not dynamic imports).
- We need to do more comprehensive performance testing—native support for ES6 modules is still in the process of landing and relatively untried..
- We need to finish updating the Polymer CLI and related tools for modules and npm.
- We need to write documentation, samples, templates, and all that good stuff.
- Most importantly, we need your feedback, input and participation to help us get Polymer Modulizer, Polymer 3.0, and the 3.0-compatible Polymer elements ready for production use. We’ll also need your help to get the booming ecosystem of third-party web components transitioned.
We hope you’re as excited as we are about the Polymer 3.0 preview and we'd love to have your feedback.
Tune in tomorrow to get hands-on with the new code!