Tim van der Lippe
62d5232756
The original behavior of build_debug_applications.py was to traverse all files recursively in the front_end folder and symlink each individual file to the version in third_party/blink/renderer/devtools/front_end. However, this requires rebuilding of Chrome when new files are added to the application. After this CL, the developer experience is more What-You-See-Is-What-You-Get. This CL is also in preparation to remove the logic in C++-land to remove the need for a separate debug folder. A follow-up CL will change the behavior of `debug_devtools` to symlink directly into out/[NAME]/resources/inspector, rather than an explicit sub-directory. As a nice side-effect of this change, we are no longer symlinking the debug folder for every version of the application. Previously, it would iterate through all `application_names` and symlink the full debug folder. This is time-consuming and did not provide any actual benefit. Since we now symlink directly to the local version, we no longer need to build the HTML files directly. Bug: 986365 Change-Id: I7e54ac3af57e0a3941b88a46b71b3ddacd5664f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713344 Reviewed-by: Erik Luo <luoe@chromium.org> Commit-Queue: Tim van der Lippe <tvanderlippe@google.com> Cr-Original-Commit-Position: refs/heads/master@{#680518} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: a66c49ab42280aaaa4cf2b293b8e0c42c545b154
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
- local_node - installs a local runtime of node.js
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.