Tim van der Lippe
67c4ae8e03
For all `_module.js` files, we currently copy all `modules` into the `module.json` metadata. However, since then the Runtime got updated to always load the entrypoint. This is possible, because in release modes only the entrypoint exists and all other files are removed. Therefore, we can use an empty array to denote that solely the entrypoint should be loaded by the Runtime. If however the module has a legacy file, the Runtime needs to load that instead. (See `Runtime._loadModules` for more information) Therefore, include solely the legacy file to the metadata information in the `_module.js` to load it. Eventually, this will allow us to remove the files from the modules array in the `module.json`, as only Closure would require that information. R=aerotwist@chromium.org Bug: 1131500 Change-Id: Ie14bd55b29b356a39aad7e8ca2041c979bd1b2cb Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2461783 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Auto-Submit: Tim van der Lippe <tvanderlippe@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.