gecko-dev/devtools/client/netmonitor
Jan Odvarko 4133d764ee Bug 1566019 - Fix URL column sorting + test r=nchevobbe
Differential Revision: https://phabricator.services.mozilla.com/D38065

--HG--
extra : moz-landing-system : lando
2019-07-15 15:22:56 +00:00
..
bin
configs
src Bug 1566019 - Fix URL column sorting + test r=nchevobbe 2019-07-15 15:22:56 +00:00
test Bug 1566019 - Fix URL column sorting + test r=nchevobbe 2019-07-15 15:22:56 +00:00
.babelrc
.eslintrc.js Bug 1558517 - Pre 3.0: Remove conflicting eslint rules, and turn on "curly: all" everywhere, r=standard8 2019-06-28 17:14:01 +02:00
index.html
initializer.js Bug 1561435 - Format devtools/client/, a=automatic-formatting 2019-07-05 11:24:38 +02:00
launchpad.js Sumary: Bug 862851 - Swap the Domain and File columns in the network panel r=Honza 2018-10-30 16:44:15 +00:00
moz.build
package.json Bug 1556434 - Use JSON reporter for DevTools jest tests on Try r=nchevobbe,Ola 2019-06-04 12:29:43 +00:00
panel.js
README.md Bug 1527826 - Reflect our github org name change in the m-c code; r=nchevobbe 2019-02-15 09:38:53 +00:00
webpack.config.js Bug 1561435 - Format devtools/client/, a=automatic-formatting 2019-07-05 11:24:38 +02:00
yarn.lock Bug 1539530 - Setting up Jest tests with Task Cluster r=Honza 2019-04-17 11:13:42 +00:00

Network Monitor

The Network Monitor (netmonitor) shows you all the network requests Firefox makes (for example, when a page is loaded or when an XMLHttpRequest is performed) , how long each request takes, and details of each request. You can edit the method, query, header and resend the request as well. Read MDN to learn all the features and how to use the tool.

Prerequisite

If you want to build the Network Monitor inside of the DevTools toolbox (Firefox Devtools Panels), follow the simple Firefox build document in MDN. Start your compiled firefox and open the Firefox developer tool, you can see the Network Monitor inside.

Run inside of the DevTools toolbox

Files used to run the Network Monitor inside of the DevTools toolbox.

  • panel.js called by devtools toolbox to launch the Network Monitor panel.
  • index.html panel UI and launch scripts.
  • src/connector/ wrap function call for Browser specific API. Current support Firefox and Chrome(experimental).

Run in the browser tab (experimental)

Files used to run the Network Monitor in the browser tab

  • bin/ files to launch test server.
  • configs/ dev configs.
  • launchpad.js the entry point, equivalent to index.html.
  • webpack.config.js the webpack config file, including plenty of module alias map to shims and polyfills.
  • package.json declare every required packages and available commands.

To run in the browser tab, the Network Monitor needs to get some dependencies from npm module. Check package.json to see all dependencies. Check webpack.config.js to find the module alias, and check devtools-core packages to dive into actual modules used by the Network Monitor and other Devtools.

UI

The Network Monitor UI is built using React components (in src/components/).

  • MonitorPanel in MonitorPanel.js is the root element.
  • Three major container components are
    • Toolbar Panel related functions.
    • RequestList Show each request information.
    • NetworkDetailsPanel Show detailed information per request.
    • StatusBar Show statistics while loading.
  • src/assets Styles that affect the Network Monitor panel.

We prefer stateless component (define by function) instead of stateful component (define by class) unless the component has to maintain its internal state.

State

Besides the UI, the Network Monitor manages the app state via Redux. The following locations define the app state:

  • src/constants.js constants used across the tool including action and event names.
  • src/actions/ for all actions that change the state.
  • src/reducers/ for all reducers that change the state.
  • src/selectors/ functions that return a formatted version of parts of the app state.

We use reselect library to perform state calculations efficiently.