devtools/docs/README.md
author Sylvestre Ledru <sledru@mozilla.com>
Tue, 07 Feb 2017 14:11:58 +0100
changeset 479859 f54cdd43eb0d8ce39f07462d78ee062917acff7a
parent 342907 9e9f949b36c80f6794a22cbd137c1bce5d9e7098
child 478977 7339582b02bbed5eac7aa7265f880f3c79aefe55
permissions -rw-r--r--
Bug 1337358 - Converts for(...; ...; ...) loops to use the new range-based loops in C++11 in browser/ r?fkiefer MozReview-Commit-ID: KOTTyFtYKE8

# Firefox Developer Tools

Hello! This documentation is for developers who want to work on the
developer tools. If you are looking for general docs about how to use
the tools, checkout [this MDN
page](https://developer.mozilla.org/en-US/docs/Tools).

These docs explain how the developer tools work at high-level, as well
as providing links to reference documentation. This is a good starting
point if you are a new contributor, or want to learn how our protocol,
a specific tool, or something else works.

If you are looking to **start hacking** on the developer tools, all of
this information is documented on the
[Hacking](https://wiki.mozilla.org/DevTools/Hacking) wiki page.

A very quick version:

```
$ hg clone http://hg.mozilla.org/integration/fx-team
$ ./mach build
$ ./mach run -P development
```

You can also clone via git from
`https://github.com/mozilla/gecko-dev.git`. Note that the workflow for
submitting patches may be a little different if using git.

Please see the [Hacking](https://wiki.mozilla.org/DevTools/Hacking)
page for a lot more information!

All of our **coding standards** are documented on the [Coding
Standards](https://wiki.mozilla.org/DevTools/CodingStandards) wiki
page.

We use ESLint to enforce coding standards, and if you can run it
straight from the command like this:

```
./mach eslint path/to/directory
```