At the Google I/O conference in 2013, Google released the Web UI framework Polymer. As my own son, I can basically see Polymer at the annual Google I/O conference. Polymer will also appear at I/O 2018 next week and officially release version 3.0.
Compared to 2.0, Polymer 3.0 is the biggest change in the project's history. Polymer has used Bower and HTML Imports to manage dependencies since its early days: Bower installs dependencies, and HTML Imports loads them. And version 3.0 will use ES Modules instead of HTML imports and migrate Bower to npm.
In the recently updated Roadmap , the Polymer development team stated that in version 3.0, Polymer Elements will also be converted into ES modules and distributed via npm, just like the core library. The Polymer CLI and related tools will also be updated to support developing, testing, and deploying projects composed of ES modules.
Of course, although the changes this time around are huge, the development team said they will make the transition as seamless as possible. The API of Polymer3.0 will be basically the same as the API of 2.X. There will also be an upgrade tool ( polymer-modulizer ) that will automatically handle most of the conversion work for 2.x based Elements and applications.