author Julian Descottes <>
Wed, 07 Dec 2016 18:24:51 +0100
changeset 325354 b9b90a3362eaed6b77720905182ad4153d8b1dab
parent 259966 ae64d16898395607093db2e2dd667b6544cb1f55
permissions -rw-r--r--
Bug 1321509 - use devtools-local-toolbox to load the inspector in content;r=bgrins,tromey Add package.json to devtools/client/inspector Integration with devtools-local-toolbox: - provides development server - default webpack config - landing page to select a tab In this patch: - bin/dev-server-js contains the inspector specific routes - webpack/*-sham.js : inspector dependencies that had to be mocked ideally, decoupling work should continue and the inspector client should only ever require files that require no chrome priviledged APIs. - toolbox.js contains the interface with devtools-local-toolbox bootstrap and the inspector panel initialization - configs/development.json is the inspector config for the devtools-local-toolbox MozReview-Commit-ID: 7YQLUlgSyDX

An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:

For information on how to build Mozilla from the source code, see:

To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla ( Instructions are at:

If you have a question about developing Mozilla, and can't find the solution
on, you can try asking your question in a
mozilla.* Usenet group, or on IRC at [The Mozilla news groups
are accessible on Google Groups, or with a NNTP reader.]

You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
            - or -