• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

styles/H11-Apr-2017-1310

svgs/H03-May-2022-

.gitignoreH A D11-Apr-20175 11

README.mdH A D11-Apr-20171.3 KiB4231

SUMMARY.mdH A D11-Apr-2017521 2017

backend.mdH A D11-Apr-201768 21

debugger-api.mdH A D11-Apr-2017320 106

debugger-panel.mdH A D11-Apr-201750 21

frontend.mdH A D11-Apr-201769 21

http-inspector.mdH A D11-Apr-20176.3 KiB168125

inspector-panel.mdH A D11-Apr-20175.8 KiB9981

memory-panel.mdH A D11-Apr-201710.6 KiB227170

protocol.mdH A D11-Apr-2017252 65

react-guidelines.mdH A D11-Apr-20172.5 KiB7352

react-tips.mdH A D11-Apr-2017645 1913

react.mdH A D11-Apr-20175.7 KiB157122

redux-guidelines.mdH A D11-Apr-20172 KiB5333

redux-tips.mdH A D11-Apr-201788 53

redux.mdH A D11-Apr-20176.3 KiB160128

responsive-design-mode.mdH A D11-Apr-20173.2 KiB7156

svgs.mdH A D11-Apr-20173 KiB4228

tools.mdH A D11-Apr-201774 21

README.md

1# Firefox Developer Tools
2
3Hello! This documentation is for developers who want to work on the
4developer tools. If you are looking for general docs about how to use
5the tools, checkout [this MDN
6page](https://developer.mozilla.org/en-US/docs/Tools).
7
8These docs explain how the developer tools work at high-level, as well
9as providing links to reference documentation. This is a good starting
10point if you are a new contributor, or want to learn how our protocol,
11a specific tool, or something else works.
12
13If you are looking to **start hacking** on the developer tools, all of
14this information is documented on the
15[Hacking](https://wiki.mozilla.org/DevTools/Hacking) wiki page.
16
17A very quick version:
18
19```
20$ hg clone http://hg.mozilla.org/integration/fx-team
21$ ./mach build
22$ ./mach run -P development
23```
24
25You can also clone via git from
26`https://github.com/mozilla/gecko-dev.git`. Note that the workflow for
27submitting patches may be a little different if using git.
28
29Please see the [Hacking](https://wiki.mozilla.org/DevTools/Hacking)
30page for a lot more information!
31
32All of our **coding standards** are documented on the [Coding
33Standards](https://wiki.mozilla.org/DevTools/CodingStandards) wiki
34page.
35
36We use ESLint to enforce coding standards, and if you can run it
37straight from the command like this:
38
39```
40./mach eslint path/to/directory
41```
42