node package manager
Easy sharing. Manage teams and permissions with one click. Create a free org »



Polymer element for the plotly.js library.

Build Status

<plotly-plot> provides a thin, fully-functional interface to the core of the library. The key properties of the plot, data, layout, and config, are all exposed as Polymer properties; updates to these properties via .set will automatically trigger redrawing.

All of the update methods provided with plotly.js have been exposed: redraw, restyle, and relayout. The other methods are also available for dynamic updates: addTraces, deleteTraces, and moveTraces.

Finally, the custom plotly-specific events are also replicated as Polymer events.

For thorough documentation, visit the project homepage.

Using plotly-plot

Install the element with Bower by adding it to your project's dependencies in bower.json, or install via NPM/Yarn by adding it to your package.json. If you install over NPM, make sure your dependencies are flat, as Polymer HTML imports require it.

Import the element into your project by using an HTML import:

<link rel="import" href="../plotly-plot/plotly-plot.html">

NOTE: The plotly.js library is incompatible with shadow DOM

Polymer elements, and web components in general, depend on being able to "hide" their inner DOM from the rest of the page. This is accomplished through a set of functionality known as the "shadow DOM."

Polymer has two kinds of shadow DOM implementations: native shadow DOM, and a shim called "shady DOM." Native shadow DOM is newer and yields improved performance, but it has incomplete support in browsers outside the newest Chrome and can often cause problems with existing code. For this reason, shady DOM is still the default implementation in Polymer 1.x.

Unfortunately, native shadow DOM is currently incompatible with plotly.js. The icon toolbar layout code in the plotly.js library fails for all plotly plots rendered inside a shadow DOM, whether by Polymer or any other means. The element cannot tell that the library code has misrendered. It acts as if it rendered correctly and responds to JavaScript normally.

This is a library-level issue between plotly.js and the DOM. It does not have to do with this element itself, and <plotly-plot> can't do anything about it until either plotly.js or the shadow DOM code change to accommodate one another.

In the mean time, if you're using <plotly-plot>, make sure you do not have Polymer.dom = 'shadow' in the global Polymer settings of your project.

Developing/contributing to plotly-plot

Installing Dependencies

Element dependencies are managed via Bower for the front-end/polymer components, and NPM for everything else.

Installing NPM dependencies

    $ npm install

Installing / updating Bower dependencies:

    $ npm run bower:install
    $ npm run bower:update



Polylint can be used to take into account Polymer linting specificities.

    $ npm run polylint

Polylint documentation.


ESLint is used to lint the JavaScript.

    $ npm run eslint

Both can be run together:

    $ npm run lint

Dev server

Polyserve makes it easy to use the element while keeping Bower dependencies in line. It works well as a development server.

Installing Polyserve:

    $ npm install -g polyserve

Running Polyserve:

    $ npm start

Once running, http://localhost:8080/components/plotly-plot/, shows the index page of the element.


Navigate to http://localhost:8080/components/plotly-plot/test/ (as served by Polyserve) to run the tests.


The tests are implemented with web-component-tester. They can be run in a terminal:

    $ npm test

WCT Tips

  • npm test -- -l chrome will only run tests in chrome.
  • npm test -- -p will keep the browsers alive after test runs (refresh to re-run).
  • npm test -- test/some-file.html will test only the files you specify.

Continuous Integration: TravisCI

On every merge request in this repo, linting and tests will automatically be performed by travis-ci. Tagged versions are automatically released to NPM and Bower.