Brandon Goddard
f8f37d164e
This CL introduces an alternate approach to the integrated workflow that allows users to use a single gclient project to manage both chromium/src and devtools-frontend. It also adds a scripts and instructions for how to install as a hook to ensure that running `gclient sync -D` no longer removes the symlink to the devtools-frontend when using the integrated workflow *Note that the hook can be used regardless of using the single gclient project if the path to the non-symlinked devtools frontend is inserted in the .gclient project file for chromium/src Change-Id: I235ff713964fd02d9cec40e07e88e9d7b68dcf16 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2209366 Commit-Queue: Brandon Goddard <brgoddar@microsoft.com> Reviewed-by: Robert Paveza <Rob.Paveza@microsoft.com> Reviewed-by: Yang Guo <yangguo@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.