If you're already using the Polymer CLI or polymer-build, and you're happy with your project, then by all means stick with them! They're great tools that do awesome stuff 😁 Who is this for? īefore jumping into the nitty gritty, I wanted to first identify which users would benefit the most from this tool. Although the project is still in a beta phase, I thought it would be cool to do a short write up so members of the Polymer community can kick the tires and give it some feedback. Not only does this make it much easier to use Polymer with other frameworks, but it also adds interesting new features to Polymer like the ability to use ES Module import syntax to pull in code installed via npm.īefore I get too ahead of myself I want to point out that this is not an official Polymer project-Polymer isn’t “going all in on Webpack” or anything like that-this is just an awesome tool created by two community members, Bryan Coulter and Chad Killingsworth, that solves a pain point a number of developers have encountered. So could it be extended to understand HTML imports? Sure, why not! Today I'm really excited to show off polymer-webpack-loader, a new tool which consumes HTML Imports and outputs modules ready for Webpack. This means developers who want to use the two together will need to reconcile how things get bundled and the order in which they’re loaded.īut Webpack can already understand multiple file formats (.css. Polymer, on the other hand, uses HTML Imports. Most frameworks tend to rely on ES Modules or CommonJS and tools like Webpack to bundle their code. Often these teams are on different stacks (React, Vue, Angular, etc.) so using something like Web Components and Polymer makes sense, as all of these frameworks can consume and communicate with Web Components. Over the last year I've had a number of discussions with mid to large sized companies who are interested in creating common UI libraries that all of their teams can share.

How to run webpack cli