The Polymer CLI is the recommended starting point for tools related to developing Polymer elements. If for some reason it does not meet your needs, here is a list of the underlying tools that it is composed of. You can use a build tool like Gulp or Grunt in combination with these tools to create your own workflow.
polyserve—web server for developing elements
polyserve powers the Polymer CLI command
polyserve is simple web server for serving
bower_components, locally. It's useful when developing your own elements.
polyserve serves the component from the current directory as
element-name is defined as the name in
bower.json. All other dependencies are served from
npm install -g polyserve@next
cd my-element/ polyserve -p 8080
polylint—lint projects for errors and common mistakes
polylint powers the Polymer CLI command
polylint is a linting tool to detect common mistakes and errors in your projects.
npm install -g polylint
polylint --root my-project/ \ --input elements.html my-element.html
web-component-tester—unit-testing tool for elements
web-component-tester powers the Polymer CLI command
Web component tester is a tool providing a browser-based testing environment for web components. Out of the box it includes support for Mocha, Chai, Async and Sinon. See Test your elements for detailed usage.
npm install -g web-component-tester@next
wct wct -l chrome (runs tests in chrome only)
By default, any tests under
test/ will be run. You can override this by specifying particular files (or globs of files) via
If you prefer not to use WCT's command line tool, you can also run WCT tests directly in a browser via a web server of your choosing.
For details on using WCT, see Test your elements.
Build and optimization
polymer-build—automates Polymer build tasks
polymer-build powers the Polymer CLI command
polymer-build is a Node library for automating Polymer build tasks. You can use it to create a custom Polymer build process using Gulp or another Node-based build system.
npm install --save-dev polymer-build@next