mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-08 04:44:04 +08:00
Tim van der Lippe
74e4acb702
In https://crrev.com/c/2684274 the layout tests will use the gen build output of DevTools. The layout tests are still failing ( https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8855048827859077360/+/steps/blink_web_tests__with_patch_/0/logs/outdir_json/0 ) with the following error: ``` PROMISE FAILURE: Error: While loading from url http://localhost:8000/inspector-sources/i18n/locales/en-US.json server responded with a status of 404 at XMLHttpRequest.n.onreadystatechange (http://localhost:8000/inspector-sources/root/root.js:1:8457) ``` As it turns out, we need to explicitly list the locales as `data` as well. Rather than updating the `filter_include` to include `*.json` (which would cause it to include `tsconfig.json` files, which we don't want), we should instead only include the mapped sources in the gen-directory. We also can't use the `invoker.sources` array directly, as that would include `*.ts` files, which don't have a corresponding `gen` build output file. That would crash the CQ bots as well, as they ensure that all `runtime_deps` files exist. R=jacktfranklin@chromium.org Bug: 1174013 Change-Id: I35623e86c40f5616836c1387c150fc492db527e6 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2700391 Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@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
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).