| .. | ||
| img | ||
| styles | ||
| svgs | ||
| .gitignore | ||
| backend.md | ||
| backward-compatibility.md | ||
| debugger-api.md | ||
| debugger-panel.md | ||
| frontend.md | ||
| highlighters.md | ||
| http-inspector.md | ||
| inspector-panel.md | ||
| inspector.md | ||
| memory-panel.md | ||
| protocol.md | ||
| react-guidelines.md | ||
| react-tips.md | ||
| react.md | ||
| README.md | ||
| redux-guidelines.md | ||
| redux-tips.md | ||
| redux.md | ||
| responsive-design-mode.md | ||
| SUMMARY.md | ||
| svgs.md | ||
| tools.md | ||
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.
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 wiki page.
A very quick version:
$ hg clone https://hg.mozilla.org/integration/mozilla-inbound
$ ./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 page for a lot more information!
All of our coding standards are documented on the Coding Standards 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