Tim van der Lippe
60bc8888bf
These files were used in the pre-ES module module era, to instruct editors like VS Code to resolve symbols. However, since we are in ES modules land we explicitly *don't* want this resolution. By removing suport for jsconfig, the editor will now warn before hand on un-imported symbols. This should reduce the risk of accidentally using the global symbol rather than the import. After this change, there will be numerous `jsconfig.json` in the repository. You are recommended to `git add . && git reset --hard` to remove these from your local checkout. Most files will now see a lot of red squiggles with errors, which is to be expected, as TypeScript does not understand many of the globals. I have declared `ls` in the globals to at least suppress these, as well as fix the definition of UIString. These seem to be the most prominent. All other usages will still need fixing before the files in question can be typescriptified. However, we do hope that with this change, it is more difficult to check in new code that is not compliant with TypeScript already. Bug: 1006759 Change-Id: I6591e73d66c845a2160b843b627c1adcb1389c24 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2098602 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Paul Lewis <aerotwist@chromium.org> Reviewed-by: Robert Paveza <Rob.Paveza@microsoft.com>
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.