Mathias Bynens
4a0d19365c
Reland of: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2316062 Screenshot: https://i.imgur.com/LJHFIp9.png Note that the screenshot shows this as a response header instead of a request header, since that was easier to test. In real-world scenarios it would be a request header instead, but the UI looks the same. CL preparing the ClientVariationsParser for use in the DevTools UI: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2316065 TBR=isherman@chromium.org,mathias@chromium.org,changhaohan@chromium.org,alexrudenko@chromium.org Bug: chromium:1103854 Change-Id: I6b959a1d57bcbc84f8571257a88fcbec805bf330 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2318257 Reviewed-by: Mathias Bynens <mathias@chromium.org> Reviewed-by: Ilya Sherman <isherman@chromium.org> Reviewed-by: Paul Lewis <aerotwist@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org>
DevTools Scripts
Development workflow scripts
These are scripts that can be useful to run independently as you're working on Chrome DevTools front-end.
The newer scripts such as for testing and hosted mode are written in Node.js, which has become the standard toolchain for web apps. The older scripts such as building (e.g. bundling and minifying) are written in Python, which has first-class support in Chromium's infrastructure.
Overview
Folders
- build - Python package for generating DevTools debug and release mode
- chrome_debug_launcher - automagically finds Chrome Canary and launches it with debugging flags (e.g. remote debugging port)
- closure - see section on Closure Compiler below
- gulp - experimental build process written in node.js & gulp to remove the dependency on Chromium-specific build tools (i.e. gn and ninja)
- hosted_mode - run DevTools on a localhost development server
- jsdoc_validator - enforces the use of Closure type annotations
Python Scripts
- compile_frontend.py - runs closure compiler to do static type analysis
- Note: the compiled outputs are not actually used to run DevTools
- lint_javascript.py - run eslint
- optimize_svg_images.py - manually run when changing svg images
Node.js scripts
The easiest way to run the node.js scripts is to use npm run which displays all the commands. For more information on the specific npm run commands, take a look at the primary devtools front-end readme (../readme.md).
Closure
DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the closure_runner (in ./closure) and jsdoc_validator custom jars using the python scripts in their respective directory.