Search for existing and closed issues. If your problem or idea is not addressed

yet, [please open a new issue](https://github.com/plotly/plotly.js/issues/new).

[`plotly`](https://stackoverflow.com/questions/tagged/plotly)) or on

community.plot.ly (tagged [`plotly-js`](http://community.plot.ly/c/plotly-js)).

We use the following [labels](https://github.com/plotly/plotly.js/labels) to track issues:

| `status: reviewable` | PRs that are completed from the author's perspective |

| `status: on hold` | PRs that are put on hold |

- git

- [node.js](https://nodejs.org/en/). We recommend using node.js 4.2.x (LTS).

Upgrading and managing node versions can be easily done using

[`nvm`](https://github.com/creationix/nvm) or its Windows alternatives.

There is also a search bar in the top right of the dashboard. This fuzzy-searches

image mocks based on their file name and trace type.

- `npm run preprocess`: pre-processes the css and svg source file in js. This

script must be run manually when updating the css and svg source files.

- `npm run watch`: starts a watchify file watcher just like the test dashboard but

without booting up a server.

Both jasmine and image tests are run on

[CircleCI](https://circleci.com/gh/plotly/plotly.js) on every push to this

To view the results of a run on CircleCI, download the `build/test_images/` and `build/test_images_diff/` artifacts into your local repo and then run `npm run start-image_viewer`.

- Distributed files are in `dist/`

- CommonJS require-able modules are in `lib/`

- Non-distributed, built files are in `build/` (most files in here are git-ignored, the css and font built files are exceptions)

Check if ok, with `npm run lint`