Home Start Get started Quick tour of Polymer Install the Release Candidate Polymer Feature overview What's new About Polymer 2.0 Upgrade guide Hybrid elements Release notes Custom elements Custom element concepts Define an element Declare properties Shadow DOM & styling Shadow DOM concepts DOM templating Style shadow DOM Custom CSS properties Events Handle and fire events Gesture events Data system Data system concepts Work with object and array data Observers and computed properties Data binding Helper elements Tools Tools overview Polymer CLI Document your elements Test your elements Optimize for production Advanced tools Services polymer.json specification Node support Resources Browser compatibility Glossary API Reference API Reference App Toolbox What's in the box? Using the Toolbox App templates Responsive app layout Routing Localization App storage Service worker Serve your app Case study Shop News Blog Community Feature overview
What's new
About Polymer 2.0 Upgrade guide Hybrid elements Release notes
Custom elements
Custom element concepts Define an element Declare properties
Shadow DOM & styling
Shadow DOM concepts DOM templating Style shadow DOM Custom CSS properties
Events
Handle and fire events Gesture events
Data system
Data system concepts Work with object and array data Observers and computed properties Data binding Helper elements
Tools
Tools overview Polymer CLI Document your elements Test your elements Optimize for production Advanced tools Services polymer.json specification Node support
Resources
Browser compatibility Glossary
API Reference
API Reference

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 powers the Polymer CLI command polymer serve.

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 /components/{element-name}/, where element-name is defined as the name in bower.json. All other dependencies are served from ./bower_components/.

Install:

npm install -g polyserve@next

Usage:

cd my-element/
polyserve -p 8080

Source: github.com/PolymerLabs/polyserve

polylint powers the Polymer CLI command polymer lint.

polylint is a linting tool to detect common mistakes and errors in your projects.

Install:

npm install -g polylint

Usage:

polylint --root my-project/ \
    --input elements.html my-element.html

Source: github.com/PolymerLabs/polylint

web-component-tester powers the Polymer CLI command polymer test.

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.

Install:

npm install -g web-component-tester@next

Usage:

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 wct path/to/files.

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.

Source: github.com/Polymer/web-component-tester

polymer-build powers the Polymer CLI command polymer build.

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.

Install:

npm install --save-dev polymer-build@next

Usage:

See the polymer-build README for detailed usage instructions.

Source: github.com/Polymer/polymer-build